>From: Theodore Ts'o <[EMAIL PROTECTED]>
> Um, e2fsck does search for the external journal device by UUID. It
> only falls back to the superblock field specifying the device if the
> journal can't be found.
I was in a hurry so I might of misread the symptoms I was seeing, but it
sure looked like e2fsck 1.37-2sarge1 wasn't finding the journal. I didn't
dare try reseting the field with tune2fs for fear of losing journal
entries and data damage.
> I think the problem you may be seeing is that it currently doesn't
> correct the superblock field specifying the device. E2fsck can find
> the journal, and it will replay the external journal if necessary.
> But at the moment it doesn't set the superblock hint.
You'll note that my first message said "...and correct the superblock
field...", this is the main issue. Given that a filesystem with the
journal device hint set wrong isn't mountable and tune2fs is dangerous on
unclean filesystems, e2fsck MUST set the hint!
> Still, it would probably be a good idea for e2fsck to set the
> superblock hint, even if the mount program should also be doing this
> as well.
Isn't `mount` supposed to be a filesystem independant utility? At which
point it has no business modifying flags in the superblock of an ext2
filesystem.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | [EMAIL PROTECTED] PGP 8881EF59 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
\___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
