https://bugzilla.kernel.org/show_bug.cgi?id=25352 --- Comment #8 from Kees Cook <kees@xxxxxxxxxxx> 2010-12-21 18:03:21 --- Ted, no, sorry; I didn't mean to confuse. Those are just left-over corruption from my initial fs hit. I just thought I'd report the fact that fsck didn't notice this when cleaning up from the original corruption. I.e. here's my timeline for this corruption: resize get errors in dmesg umount fsck -f (for half a day, cleans up tons) mount delete all of lost+found continue using fs more dmesg errors umount fsck -f (returns without error) mount continue using fs still dmesg errors rm offending directory completely no more errors So, it seemed like a flaw in fsck that it didn't find the bad directory, but since it was related to the corruption introduced by this kernel bug, I thought I'd bring it up in this thread. -- 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
