Partition check:
sda: sda1 sda2 sda3
sdb: sdb1
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 36k freed
Adding Swap: 104384k swap-space (priority -1)
EXT2-fs error (device 08:02): ext2_check_blocks_bitmap: Wrong free blocks count for group 5, stored = 2242, counted = 2241
EXT2-fs error (device 08:02): ext2_check_blocks_bitmap: Wrong free blocks count for group 6, stored = 6538, counted = 6537
EXT2-fs error (device 08:02): ext2_check_blocks_bitmap: Wrong free blocks count for group 14, stored = 2862, counted = 2860
EXT2-fs error (device 08:03): ext2_check_inodes_bitmap: Wrong free inodes count in group 50, stored = 1608, counted = 1607
EXT2-fs error (device 08:03): ext2_check_inodes_bitmap: Wrong free inodes count in super block, stored = 246903, counted = 246902
E2fsck, fsck(.ext2) (e2fsprogs-1.12) can't repair this damages. All
filesystem is now mounted with errors. Is this reparable dmage of the
ext2fs ?
(I think... without formating or low-level formating of a hard disk)
These are actually very minor filesystem errors; e2fsck should have
absolutely no trouble fixing this kind of damage.
What makes you think that e2fsck is having trouble repairing this
damage? What messages is it printing out?
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/