http://bugzilla.kernel.org/show_bug.cgi?id=12272 ------- Comment #2 from tytso@xxxxxxx 2008-12-26 06:16 ------- What does e2fsck report when you try running e2fsck on the filesystem? Most of the errors indicate filesystem corruption which e2fsck should have complained vociferously about, and which it should have been able to fix if run manually. I can't tell how big the filesystem is (I'd need the output of dumpe2fs /dev/hdXXX) to detect that, but this: [92499.263311] Buffer I/O error on device dm-2, logical block 522133279 Indicates either a hardware error, or a corrected journal inode. In the latter case, e2fsck would have detected the problem, and offered to fix it. In the former case, this isn't a kernel bug, but rather a hardware problem.... -- 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
