https://bugzilla.kernel.org/show_bug.cgi?id=16401 --- Comment #1 from Dave Chinner <david@xxxxxxxxxxxxx> 2010-07-19 23:41:54 --- The problem appears to have been specific to a single filesystem that was corrupted in some way that e2fsck did not detect. e2fsck would report the fs as clean (even with a forced check) but the problem would come back, always on inodes around the 211,000 number. The filesystem eventually trashed itself, but I made a fat-fingered mistake and backed up the wrong image whenthe problem first manifested. Hence I can't reproduce the problem now because I had to re-image the root drive. >From this, I'd say this is not a regression, so closing this bug is fine by me... -- 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
