[Gluster-users] Clarification on common tasks

Gandalf Corvotempesta gandalf.corvotempesta at gmail.com
Thu Aug 11 14:28:40 UTC 2016

2016-08-11 16:25 GMT+02:00 Anuradha Talur <atalur at redhat.com>:
> 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.

Anyway, the suggested docs page is wrong. It has many bad commands, in example:

"gluster volume heal info failed"

this doesn't exist. The right command should be
"gluster volume <volume> heal info heal-failed

Also, the replace-brick in a replicated volumes, makes use of
"setfattr" and also ask for a directory creation/removal (step 4):

mkdir /mnt/r2/<name-of-nonexistent-dir>
rmdir /mnt/r2/<name-of-nonexistent-dir>
setfattr -n trusted.non-existent-key -v abc /mnt/r2
setfattr -x trusted.non-existent-key  /mnt/r2

i didn't this and seems to work fine.

I think that this doc page should be rewrote, there is much confusion
and unneeded steps.

More information about the Gluster-users mailing list