http://bugzilla.kernel.org/show_bug.cgi?id=12272 ------- Comment #10 from folkert@xxxxxxxxxxxxxx 2009-01-16 11:37 ------- Theodore, > 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 Device Boot Start End Blocks Id System /dev/hda1 * 1 31 248976 83 Linux /dev/hda2 32 4865 38829105 5 Extended /dev/hda5 32 4865 38829073+ 8e Linux LVM 38829073 < 522133279 so it tries to reach beyond the physical boundaries of the disk > Indicates either a hardware error, or a corrected journal inode. Possible as one of the errors that pop up is aborted journals, and journals take off-line and what not. > In the latter case, e2fsck would have detected the problem, and offered to > fix it. e2fsck finds millions of issues, I always give fixing a try but after minutes of pressing enter to fsck questions I give up and re-install debian (takes 15 minutes) -- 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
