But initially the system had devices in /etf/fstab with _netdev option.
When system starts mounting a kernel panic appears, sometimes after few
minuts.<br>The only way that I could start the system was mounting all devices one by one, with a previups fsck.<br>
I don't know if it is the better way, but is the only that I've used succesfully.<br><br><div class="gmail_quote">2011/5/13 Sunil Mushran <span dir="ltr"><<a href="mailto:sunil.mushran@oracle.com">sunil.mushran@oracle.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On 05/13/2011 11:44 AM, Xavier Diumé wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello,<br>
Is it possible to fsck a mounted filesystem. When one of the cluster nodes reboots because a kernel panic, the device requires fsck.ocfs2 because in mounted.ocfs2 -f rebooted node is shown.<br>
</blockquote>
<br></div>
If mounted.ocfs2 -f shows the rebooted node, that means the slotmap<br>
has not been cleaned up as yet. That cleanup happens during node<br>
recovery. If the volume is still mounted on another node, it will get<br>
cleaned up momentarily.<br>
<br>
If however it does not get cleaned up, that means that the volume is<br>
not mounted on any node. In that case, the next mount will clean<br>
up slotmap.<br>
<br>
Either way one does not need to fsck just to cleanup the slotmap.<br>
</blockquote></div><br><br clear="all"><br>-- <br>Xavier Diumé<br><a href="http://socaqui.cat">http://socaqui.cat</a><br>