Bug#397675: checkfs fails during init with OCFS2 partitions

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#397675: checkfs fails during init with OCFS2 partitions

Frederik Schueler-2

Retitle 397675 please do not check automatically ocfs2 filesystems
Reassign 397675 initscripts
thanks

Hi!

Automatic filesystem check of a _cluster_ filesystem during bootup of a node
is a pretty dumb idea, if the filesystem is already active on other nodes,
guess what happens.

ocfs2 filesystems (and gfs, gfs2 ones too) _must_ be fscked when _not mounted_
on _any_ node. This cannot be ensured by a node booting up.

Manual fscking of  these filesystems is mandatory.

Reassigned back.

Best regards
Frederik Schüler

--
ENOSIG

signature.asc (204 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#397675: checkfs fails during init with OCFS2 partitions

Petter Reinholdtsen
[ Frederik Schüler]
> Manual fscking of these filesystems is mandatory.

This sound to me like a good argument to make -a a no-op, and not do
any checking when it is specified.  fsck.fstype -a is the interface
used by fsck, and this make me believe it should work also for
fsck.ocfs2.  Would such change solve the problem with boot?

I believe it is best to avoid special case handling in the generic
initscripts, and thus am reluctant to try to solve it here.  Of
course, it could be solved in fsck, teaching it to not call
'fsck.ocfs2 -a'.  I doubt the fsck developers want to handle specially
the ocfs2 file system, thought.

Happy hacking,
--
Petter Reinholdtsen



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]