https://bugzilla.kernel.org/show_bug.cgi?id=26642 Summary: Automatically clean dirty bit on ext2/ext4-without-journal file systems Product: File System Version: 2.5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: enhancement Priority: P1 Component: ext4 AssignedTo: fs_ext4@xxxxxxxxxxxxxxxxxxxx ReportedBy: t.artem@xxxxxxxxxxxx Regression: No In ext2/journalless ext4 if you forget to umount the FS before rebooting/powering down PC you'll have to run fsck on a next boot. That's obvious. However we can easily avoid fsck'ing if we clean the dirty bit about a certain timeout (I suggest a configurable 300 seconds value) and only after dirty buffers have been flushed to the disk. If we write to the disk again, then this bit should be set again, of course. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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