[Gluster-users] broken after IPs changed

Костырев Александр Алексеевич a.kostyrev at serverc.ru
Sat Jun 2 08:04:31 UTC 2012

Yep, that’s exactly what happened


Guys from IRC #gluster helped me to solve the problem – thanks to them.


To solve:

1.       getfattr -m .  -d -e hex /mnt/ld0  <-- get the xattrs

2.       setfattr -x “list of xattr (step1) “ /mnt/ld0


for all bricks

and then gluster volume create … again


From: David Coulson [mailto:david at davidcoulson.net] 
Sent: Saturday, June 02, 2012 11:27 AM
To: Костырев Александр Алексеевич
Cc: gluster-users at gluster.org
Subject: Re: [Gluster-users] broken after IPs changed


You probably want to blow away your brick filesystem and start clean - There will be xattr information that is confusing Gluster.

Best practice is to use DNS to support peers, rather than IP addresses.  

On 6/1/12 12:27 AM, Костырев Александр Алексеевич wrote: 


I fired up gluster v.3.2.5 with this:


gluster peer probe

gluster volume create vms replica 2 transport tcp

gluster volume start vms

mkdir /mnt/gluster


added in /etc/fstab /mnt/gluster glusterfs defaults,_netdev 0 0

mount /mnt/gluster


everything was awesome


than for some reason I had to change IPs of my servers

from -> ->


I’ve decided to 

stop my volume,

delete it,

stop glusterd,

erase gluster software (and all configs) with yum (Centos 6.2 x86_64)

and then recreate that volume again with:

gluster peer probe

gluster volume create vms replica 2 transport tcp


but  it said:

Operation failed


I googled for awhile and found out that new 3.3.0 has arrived, so I updated to it and start whole thing over again

Now It says:

/mnt/ld0 or a prefix of it is already part of a volume


Any help ?

Thanks in advance


Gluster-users mailing list
Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120602/e392a21a/attachment.html>

More information about the Gluster-users mailing list