[Gluster-users] brick does not exist in volume

2013-07-01 Thread empty chai
hi,all I have a gluster cluster consisting of three machines,Now I want to move a brick onto a new machine.But it reported a mistake. # ./sbin/gluster volume status datastores Status of volume: datastores Gluster process PortOnline Pid

[Gluster-users] Ext4 compatibility

2013-07-01 Thread Kushnir, Michael (NIH/NLM/LHC) [C]
I've run across several users on IRC and the mailing list using GlusterFS with Ext4. Is Ext4 compatibility fixed in 3.3.1-15 kkeithley RPMS, or are these users using a different version of GlusterFS? Thanks, Michael ___ Gluster-users mailing list

Re: [Gluster-users] Ext4 compatibility

2013-07-01 Thread Kaleb S. KEITHLEY
On 07/01/2013 09:48 AM, Kushnir, Michael (NIH/NLM/LHC) [C] wrote: I've run across several users on IRC and the mailing list using GlusterFS with Ext4. Is Ext4 compatibility fixed in 3.3.1-15 kkeithley RPMS, or are these users using a different version of GlusterFS? No, the fix isn't in the

Re: [Gluster-users] Ext4 compatibility

2013-07-01 Thread Michael Brown
Or they've turned off dir_index on the ext4filesystems.

[Gluster-users] problem expanding a volume

2013-07-01 Thread Matthew Sacks
Hello, I am having trouble expanding a volume. Every time I try to add bricks to the volume, I get this error: [root@gluster1 sdb1]# gluster volume add-brick vg0 gluster5:/export/brick2/sdb1 gluster6:/export/brick2/sdb1 /export/brick2/sdb1 or a prefix of it is already part of a volume Here is

Re: [Gluster-users] problem expanding a volume

2013-07-01 Thread Joshua Hawn
I've had this issue recently. The error occurred because I tried adding a brick that was previously part of another volume. If this is the case for you, then this article may be helpful: http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/ You'll need to

Re: [Gluster-users] problem expanding a volume

2013-07-01 Thread Rejy M Cyriac
On 07/02/2013 07:16 AM, Joshua Hawn wrote: I've had this issue recently. The error occurred because I tried adding a brick that was previously part of another volume. If this is the case for you, then this article may be helpful: