+++ This bug was initially created as a clone of Bug #765327 +++ I have a distribute replicate setup 2x2, mounted on a fuse. i started replacing a brick, then i paused and then aborted it. Later i again started the replace-brick on same bricks. When it got succeeded , i checked the status, it said migration completed. But if you look in the back end, all files are not completely self-healed. But after sometime all files got self healed. --- Additional comment from vijaykumar on 2011-10-17 05:42:34 EDT --- I followed the same thing with 3.2.4 on RHEL-6.1 , i am observing the same behavior. --- Additional comment from amarts on 2012-07-11 02:43:18 EDT --- need to check if its happening on 3.3.0
Need to know , in which version it is fixed.
Since we are not supporting data migration in replace-brick moving this out of Big Bend.
Verified sanity only on 3.4.0.57rhs-1.el6rhs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0208.html