<div dir="ltr">Yes it was executed after a mount/umount because it is configured in fstab and I reboot the system then it was mounted and then I umount it to run xfs_repair.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2013/4/9 Eric Sandeen <span dir="ltr"><<a href="mailto:sandeen@sandeen.net" target="_blank">sandeen@sandeen.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 4/9/13 10:18 AM, ·ûÓÀÌÎ wrote:<br>
> The servers are back to service now and It's hard to run xfs_repair.<br>
> It always happen bellow is the xfs_repair log when it happens on<br>
> another server several days ago.<br>
<br>
> -sh-4.1$ sudo xfs_repair -n /dev/glustervg/glusterlv<br>
<br>
</div>Ok; just for what its worth, if you don't mount/umount first,<br>
you may be running repair -n with a dirty log, and it will<br>
find "more" corruption than it should, since the log is not<br>
replayed.<br>
<br>
I see that you included a non "-n" repair log as well, was<br>
that after a mount/umount? Just to be sure...<br>
<br>
Thanks,<br>
-Eric<br>
<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>·ûÓÀÌÎ
</div>