[Gluster-users] 'replace-brick' - why we plan to deprecate

任英杰 renyj at neusoft.com
Wed Oct 17 08:32:46 UTC 2012

hi Amar,
I met across a problem when I replace a brick in a stripe-replicate volume.
I used both methods you mentioned in your post.
#gluster volume replace-brick <VOL> brick1 brick2 start [1]
# gluster volume replace-brick <VOL> brick1 brick2 commit force
(self-heal daemon heals the data)

the message shows that brick1 doesn't in the volume.
I checked the volume info ,and it real exists there.
Any idea or advise?


Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosure or copying 
is strictly prohibited, and may be unlawful.If you have received this communication in error,please 
immediately notify the sender by return e-mail, and delete the original message and all copies from 
your system. Thank you. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20121017/8967948a/attachment.html>

More information about the Gluster-users mailing list