Actualy this is even worse than I thought.
If an external journal gets destroyed there appears to be no way to fsck
the filesystem.
I have an ext3 filesystem on /dev/group-a/ums which has a journal on
/dev/flash/ums-journal. Some terrible accident causes the destruction
of the journal. Now how do I fsck the filesystem?
lvremove /dev/flash/ums-journal
Do you really want to remove active logical volume ums-journal? [y/n]: y
Logical volume "ums-journal" successfully removed
r...@acadia:~/ums-benchmark# fsck /dev/group-a/ums
fsck from util-linux-ng 2.16.2
e2fsck 1.41.12 (17-May-2010)
Can't find external journal
r...@acadia:~/ums-benchmark# tune2fs -f -O ^has_journal /dev/group-a/ums
tune2fs 1.41.12 (17-May-2010)
r...@acadia:~/ums-benchmark# fsck.ext3 /dev/group-a/ums
e2fsck 1.41.12 (17-May-2010)
Can't find external journal
What with this and bug 587531 external journals look pretty dodgy.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
