<div dir="ltr">What I finally did was:<div><br></div><div>-commit force the replace-brick operation and the brick was changed.</div><div>-to force healing I ran find /mnt/gvol/ -print0 | xargs --null stat >/dev/null;</div><div><br></div><div>If the source disk dies I still have the old copy on the replaced brick, but going through a full directory listing is quite a time/resource consuming task.</div></div><div class="gmail_extra"><br><div class="gmail_quote">2014-11-07 9:50 GMT-03:00 Juan José Pavlik Salles <span dir="ltr"><<a href="mailto:jjpavlik@gmail.com" target="_blank">jjpavlik@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi guys, we added a new node to the cluster we have so I used replace-brick to move a brick from node 4 to the new node 5. Everything was going great but the operation was completed before moving all the files it was supposed to move. It barely moved 1TB from 2.3TB it should have moved.<div><br></div><div>What should I do? Abort the replacement? Commit force it and let self heal move the rest of the files?</div><div><br></div><div>Regards<span class="HOEnZb"><font color="#888888"><br clear="all"><div><br></div>-- <br><div><div dir="ltr">Pavlik Salles Juan José<div>Blog - <a href="http://viviendolared.blogspot.com" target="_blank">http://viviendolared.blogspot.com</a></div></div></div>
</font></span></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Pavlik Salles Juan José<div>Blog - <a href="http://viviendolared.blogspot.com" target="_blank">http://viviendolared.blogspot.com</a></div></div></div>
</div>