I have come up with the attached patch to fix e2fsck to handle the old inodes left behind when you use lazy_itable_init. It simply checks if ctime < s_mkfs_time and offers to clear the inode. The check is skipped if the clock is detected to be broken. The first prompt informs you that "Inodes with ctime older than the mkfs time detected. Either you have a broken clock, or they are leftover from a previous fs." If you answer yes to clear the inode, the answer is latched and all subsequent inodes with the same problem are also cleared.
I feel that this addresses the issue and should allow us to turn on lazy_itable_init by default. What do you all think? ** Patch added: "clear-old-inodes.patch" http://launchpadlibrarian.net/49273354/clear-old-inodes.patch ** Patch removed: "clear-old-inodes.patch" http://launchpadlibrarian.net/49273354/clear-old-inodes.patch -- dmraid-activate ERROR https://bugs.launchpad.net/bugs/524825 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
