Thanks for a quick reply!
> Hmm... meaning the corrupted area was not touched by the running fs.
> Because if it had, the fs would have been remounted ro with a message
> asking the user to run fsck.
If so, the corrupted fs was probably not the cause of an initial problem
which made me run fsck.
Hmm... meaning the corrupted area was not touched by the running fs.
Because if it had, the fs would have been remounted ro with a message
asking the user to run fsck.
Remember, ocfs2 is a journaled fs. So there is no need to run fsck
on a regular basis. If a node dies, the surviving node recovers
Thanks for a great file system!
I have a two-node cluster working as a HA NFS server. This system has
worked fine for almost a year, but recently I found that an ocfs2 file
system had been corrupted and needed to be repaired with fsck.ocfs2.
Even though I don't think that any data was lost I foun
