[Ocfs2-users] fsck.ocfs2

[Sunil Mushran]

Please do not remove the cc-s.

Hard for me to comment without knowing anything about the panic.

However, assuming that the panic message indicated that the volume
needs to be fsck-ed. In that case, the best course is to umount the
volume on all nodes and running fsck on one node.

On 05/13/2011 12:33 PM, Xavier Diumé wrote:
> But initially the system had devices in /etf/fstab with _netdev option. When system starts mounting a kernel panic appears, sometimes after few minuts.
> The only way that I could start the system was mounting all devices one by one, with a previups fsck.
> I don't know if it is the better way, but is the only that I've used succesfully.
>
> 2011/5/13 Sunil Mushran <sunil.mushran at oracle.com <mailto:sunil.mushran at oracle.com>>
>
>     On 05/13/2011 11:44 AM, Xavier Diumé wrote:
>
>         Hello,
>         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.
>
>
>     If mounted.ocfs2 -f shows the rebooted node, that means the slotmap
>     has not been cleaned up as yet. That cleanup happens during node
>     recovery. If the volume is still mounted on another node, it will get
>     cleaned up momentarily.
>
>     If however it does not get cleaned up, that means that the volume is
>     not mounted on any node. In that case, the next mount will clean
>     up slotmap.
>
>     Either way one does not need to fsck just to cleanup the slotmap.
>
>
>
>
> -- 
> Xavier Diumé
> http://socaqui.cat

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110513/794d1441/attachment.html