Hello all ,

Today I noticed that the iowait rate is high and I started to investigate in that and I found the following errs in the dmesg log and in the messages log:

dmesg:

EXT2-fs error (device sd(8,17)): ext2_new_block: Free blocks count corrupted for block group 347
EXT2-fs error (device sd(8,17)): ext2_new_block: Free blocks count corrupted for block group 347
EXT2-fs error (device sd(8,17)): ext2_new_block: Free blocks count corrupted for block group 347
EXT2-fs error (device sd(8,17)): ext2_new_block: Free blocks count corrupted for block group 347
EXT2-fs error (device sd(8,17)): ext2_free_blocks: bit already cleared for block 11369009

messages:

Apr 18 06:10:47 orbit kernel: EXT2-fs error (device sd(8,17)): ext2_new_block: Free blocks count corrupted for block group 347
Apr 18 06:10:47 orbit kernel: EXT2-fs error (device sd(8,17)): ext2_new_block: Free blocks count corrupted for block group 347
Apr 18 06:13:41 orbit kernel: EXT2-fs error (device sd(8,17)): ext2_new_block: Free blocks count corrupted for block group 347
Apr 18 06:15:07 orbit kernel: EXT2-fs error (device sd(8,17)): ext2_new_block: Free blocks count corrupted for block group 347


I tried to google it but I had nothing useful.

Anybody have any idea about this err and how to fix it.

Regards,

Yahia Salah

Uhhh, boot from a live CD or something and run e2fsck on the filesystem. The root problem could be anything from a corrupt portion of the filesystem to the early warning of a failing disk.

You need to run a filesystem check to correct the errors. Your best best is to:

shutdown -F -r now

This will shutdown and reboot the system, which will then automatically check the filesystems at boot.