On Wed, Aug 19, 2009 at 06:27:46AM +0100, Graham Murray wrote: > Shortly after rebooting following an untidy shutdown due to an unrelated > (to ext4 or the filesystem) Oops. Unmounting the partition and running > e2fsck (version 1.41.8) just replayed the journal and stated the > filesystem was clean but I did not believe it so ran 'e2fsck -f > /dev/sdb3' and that showed several errors which I allowed it to correct. What sort of errors did it find? > Aug 18 23:50:07 newton EXT4-fs error (device sdb3): ext4_mb_generate_buddy: EXT4-fs: group 35: 3499 blocks in bitmap, 3243 in gd > Aug 18 23:50:07 newton Aborting journal on device sdb3:8. Was this right after you mounted the filesystem, or did some time take place before these errors started showing up? - Ted -- 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
