I was testing a had a failover which caused the fsck to
stop and prompt:
<4>Node 3 has gone down!!!
INIT: Sending processes the TERM signal
fsck 1.32 (09-Nov-2002)
e2fsck 1.32 (09-Nov-2002)
ext3 recovery flag clear, but journal has data.
Run journal anyway<y>?
1. Clearly, in simple cases we should not prompt the user.
2. If there is a severe problem, we should abort the
fsck and NOT remount the filesystem until
administrative intervention occurs.
3. Is this particular problem related to the orphan
inodes and an improper umount?
Log in to post a comment.