Andreas Dilger wrote: > Running e2fsck on a quiescent (but mounted) filesystem fails in the > common case where the superblock inode and block count summaries are > wrong. The kernel doesn't update these values except at unmount time. > If there are other errors in the filesystem then they will already > cause e2fsck to consider the filesystem invalid, so these minor errors > should not. If by quiescent, if you mean ->write_super_lockfs, shouldn't that path be indistinguishable from an unmount? Why wouldn't write_super_lockfs also update these counts, rather than working around it in fsck? -Eric > Don't consider only an error in the superblock summary as incorrect. > The kernel does not update this field except at unmount time. Any > other unfixed errors will themselves mark the filesystem invalid. > > Signed-off-by: Andreas Dilger <adilger@xxxxxxx> -- 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
