http://bugzilla.kernel.org/show_bug.cgi?id=12821 ------- Comment #6 from tytso@xxxxxxx 2009-03-05 11:06 ------- If it's what I think it is, it's not an anomaly; e2fsck 1.41.3 had a bug which would cause it to not fix certain types of corruption in the extent tree, and it would just bail out with an exit(1). And the error messages that the kernel printed are consistent with it. Did you try re-running a forced fsck on the filesystem after you got that failure? -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- 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
