On Wed, Jun 30, 2010 at 12:17:09PM +0200, John Hughes wrote:
> 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?
Here's a workaround for now:
debugfs -w /dev/group-a/ums
debugfs: ssv journal_uuid null
debugfs: ssv journal_inum 0
debugfs: feature ^needs_recovery
debugfs: feature ^has_journal
debugfs: quit
... and then run e2fsck -f on the file system.
In the long run e2fsck will need an extended feature that explicitly
requests it to abandon an external journal. I don't want to make this
too easy to do, since if a disk goes temporarily off-line, we don't
want "e2fsck -y" to just blindly nuke the external journal.
- Ted
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
