Package: e2fsprogs Version: 1.41.12-2 If an ext4 filesystem is configured with an external journal, and the block device containing that journal is destroyed (for example, drive failure), it seems impossible to remedy the situation with the current version of e2fsprogs.
The steps should be something along the lines of: tune2fs -f -O ^has_hournal /dev/bustedfs # (will corrupt filesystem) e2fsck /dev/bustedfs # (hope the damage is not too bad) mke2fs -O journal_dev -L new_journal /dev/newjournal tune2fs -o journal_data -j -J device=LABEL=new_journal /dev/bustedfs The first step will always fail, claiming "The needs_recovery flag is set. Please run e2fsck before clearing the has_journal flag." A similar bug was reported on ext3-us...@redhat.com mailing list, including a patch: https://www.redhat.com/archives/ext3-users/2009-April/msg00001.html -- Brian Ristuccia br...@ristuccia.com bri...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
