OK, well I've seen your name around a lot, but you never know...
> This is purely a case of the *first* mount message being EXT2 instead
> of EXT3, as if the journal wasn't detected in the first place. However,
> the r/w mount is always ext3 per fstab.
Well, 'mount' output is useless w.r.t. the root filesystem, because it is
simply copied from /etc/fstab. You need to check /proc/mounts to see if
it is _ever_ being mounted as ext3 (lots of people have this problem,
especially if they use initrds and ext3 as a module).
If it _is_ being mounted as ext2 sometimes and ext3 other times, it
would be informative to get the dmesg output, because it will tell
you why it couldn't load the journal. Note that if there _is_ a
journal in use, it would normally prevent the filesystem from being
mounted as ext2 entirely after a crash.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/