Document URL: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Storage/2.1/html-single/Administration_Guide/index.html Section Number and Name: 10.4. Migrating Volumes Describe the issue: Our admin guide contains references to 'replace-brick'. Currently we use the workaround of doing an add-brick and then doing a remove-brick instead of using replace-brick. Also, the note in the chapter refers to the known issues in "Red Hat Storage 2.0 Update 4 Release Notes" Suggestions for improvement: Additional information:
Marking this urgent as we have few bugs for replace-brick i.e. BZ 1006899 ,BZ 1006901 in samba. The work-around works for samba but replace-brick does not. So it we are removing replace brick section from Admin guide , we can reduce the priority of the samba bugs or even close them.
Hi Anush, The issue is fixed in bug 947158. Made the changes as suggested. https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/2.1/html-single/Administration_Guide/index.html#sect-User_Guide-Managing_Volumes-Migrating
According to sayan's comment from the bug 947158 replace-brick supports for commit option, hence reducing the severity.
(In reply to Bhavana from comment #2) > Hi Anush, > > The issue is fixed in bug 947158. > > Made the changes as suggested. > > https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/2.1/html- > single/Administration_Guide/index.html#sect-User_Guide-Managing_Volumes- > Migrating Bhavana, The issue stated by Anush is not yet resolved with the change. Anush was suggesting a way to replace a brick, without using "replace-brick" command. This needs to be documented. I have raised the similar bug https://bugzilla.redhat.com/show_bug.cgi?id=1074415 and provided the steps in https://bugzilla.redhat.com/show_bug.cgi?id=1074415#c1 Probably https://bugzilla.redhat.com/show_bug.cgi?id=1074415 should be closed as DUP of this bug.
Based on Comment 4, closing this bug as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1074415. *** This bug has been marked as a duplicate of bug 1074415 ***