On Sun, May 18, 2008 at 12:37:37PM +0200, Bas van Schaik wrote: > However, there is a slight > problem with scripting e2fsck: it seems that e2fsck /always/ exits with > exit code 1 just because of the fact that the snapshot journal has been > replayed. Because of this, the script cannot tell whether there is a > real problem or not and keeps e-mailing me. This is a typical output of > such an e2fsck run: Simply replying the journal should not cause e2fsck to have an exit code of 1. It must have done something else. The common one was clearing the LARGE_FILES feature flag if the filesystem didn't have one, but that was removed as of 1.40.7. Can you take a snapshot, run dumpe2fs, run e2fsck -fy /dev/loop1, and then run dumpe2fs again, and send me a before and after? - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
