[Gluster-users] Restoring glusterfs cluster.

2012-10-24 Thread Tao Lin
Hello, deer glustefs experts: I've found that my cluster of only two nodes had ran into a big trouble. Here are some information about my glusterfs. [root@yq35 ~]# gluster --version glusterfs 3.2.6 built on Mar 22 2012 10:44:28 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c)

Re: [Gluster-users] Help! Can't replace brick.

2012-10-24 Thread Tao Lin
I've already detached 10.67.15.27 when i found i could not get replace move on. 2012/10/25 Tao Lin > Hello, glusterfs experts: > I'v been using glusterfs-3.2.6 for moths, and it works fine.Now i'm > facing a problem of disk(brick) full.For some resons, I have to expa

[Gluster-users] Help! Can't replace brick.

2012-10-24 Thread Tao Lin
Hello, glusterfs experts: I'v been using glusterfs-3.2.6 for moths, and it works fine.Now i'm facing a problem of disk(brick) full.For some resons, I have to expand space using replace current bricks to new bricks instead of add new bricks. It seemed okay when i used this command : gluster vo

[Gluster-users] How to replace brick being used by nfs?

2012-10-24 Thread Tao Lin
Hello, glusterfs experts: Can I replace a brick to a new brick (the new brick is placed on another machine) without stopping nfs that is using current brick? Can I just use the following commands? 1.gluster volume replace VOLNAME brick new-brick start 2.gluster volume replace VOLNAME brick new-b

[Gluster-users] How to add new bricks to a volume?

2012-10-22 Thread Tao Lin
Hi, dear glfs experts: I've been using glusterfs (version 3.2.6) for months,so far it works very well.Now I'm facing a problem of adding two new bricks to an existed replicated (rep=2) volume,which is consisted of only two bricks and is mounted by multiple clients.Can I just use the following co

Re: [Gluster-users] lost data, help!

2012-10-10 Thread Tao Lin
I don't think glusterfs can help you out, and I guess that the "cp" command will do a trucate before copy data. While you were trying to copy files from bricks to mountpoint, it was obvious that you were trying to copy a file to itself, the cp command would truncate the file first, then "cp" found