FSCK Errors
A clean reload after around 50 days of uptime and forced FSCK on an ext4 FS produced the following:
***** File system check forced at Tue Jul 23 21:02:13 WEST 2013 ***** fsck 1.42.8 (20-Jun-2013) e2fsck 1.42.8 (20-Jun-2013) Pass 1: Checking inodes, blocks, and sizes Inode 4195619, end of extent exceeds allowed value (logical block 64907, physical block 11435403, len 16) Clear? yes Inode 4195619, i_blocks is 1337216, should be 1337176. Fix? yes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: -(11435403--11435407) Fix? yes Free blocks count wrong for group #348 (2130, counted=2135). Fix? yes Free blocks count wrong (417470107, counted=417470112). Fix? yes /dev/c/c: ***** FILE SYSTEM WAS MODIFIED ***** /dev/c/c: 625785/30212096 files (13.6% non-contiguous), 65923424/483393536 blocks Any ideas??? I previously had this issue which got resolved: http://www.linuxquestions.org/questi...cks-4175459714 But don't have any bad blocks reported etc. |
If it helps guys, the same file as before is causing the issue with inode 4195610, a very large MS access DB.
|
All times are GMT -5. The time now is 12:27 PM. |