[Gluster-users] Clarification on common tasks

Anuradha Talur atalur at redhat.com
Thu Aug 11 14:25:06 UTC 2016

----- Original Message -----
> From: "Gandalf Corvotempesta" <gandalf.corvotempesta at gmail.com>
> To: "Anuradha Talur" <atalur at redhat.com>
> Cc: "gluster-users" <Gluster-users at gluster.org>
> Sent: Thursday, August 11, 2016 7:46:37 PM
> Subject: Re: [Gluster-users] Clarification on common tasks
> 2016-08-11 16:13 GMT+02:00 Anuradha Talur <atalur at redhat.com>:
> > There was a document that I'm not able to locate right now.
> > The first step after mounting the brick was to set volume ID using
> > setfattr -n trusted.glusterfs.volume-id -v <volume-id> <brickpath>.
> > I think there were more steps, I will update once I find the doc.
> > Once all the required xattrs are set, gluster v start force was supposed to
> > be done.
> This is a test environment so I can break everything everytime.
> I did (only once) "replace-brick" by using a new mount point, without
> setting any fattr and
> brick process was brought up immediatly and healing is going on.
> Is setfattr mandatory ?

The replace-brick you did, mentioned in the previous mails was correct and fine.
You said you have different names for old and new brick, so it works.
setfattr is *not* required in this case.

In the above case that you have quoted, I'm talking when brick names have to be the same (if you have that
requirement). There were 2 setfattrs that were needed. Anyway, sorry about the confusion.
As brick names are different, it doesn't affect your testcase.


More information about the Gluster-users mailing list