[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#425534: ext3 filesystem corruption also with linux-image-2.6.18-4-486



reassign 425534 linux-2.6 2.6.18.dfsg.1-12
found    425534 2.6.18.dfsg.1-12etch2
retitle  425534 linux-2.6: ext3 filesystem corruption
thanks


Hello,

today I got an error in my ext3 root-fs very similar to the ones
described earlier.

1) During boot hda1 reached maximal mount count and was checked.
2) e2fsck reports:
   /dev/hda1: Inode 53916 has illegal blocks
   /dev/hda1: UNEXPECTED INCONSISTENCY, RUN fsck MANUALLY
3) I then reboot into Knoppix, and start e2fsck. It shows now error on
   this filesystem. The superblock time error was only because the clock 
   was wrong under knoppix.
   
   root@tty1[hdd1]# e2fsck -yf /dev/hda1
   e2fsck 1.39-WIP (09-Apr-2006)
   Superblock last write time is in the future.  Fix? yes
   Pass 1: Checking inodes, blocks, and sizes
   Pass 2: Checking directory structure
   Pass 3: Checking directory connectivity
   Pass 4: Checking reference counts
   Pass 5: Checking group summary information
   /dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****
   /dev/hda1: 26298/124672 files (0.7% non-contiguous), 133789/248999 blocks
   
4) During the e2fsck run the output from dumpe2fs -h /dev/hda1 changed from:
   Filesystem state:         clean with errors
   to
   Filesystem state:         clean

5) After that the System booted without problems!!


Because the Error occurs in different kernel packages I reassign it to
the source package linux-2.6 and adjust the version numbers.




In the meantime I write a small bash script that extracts a statistic
how often this problem occurs with different kernel images from my log
files. The script is attached, the logfiles are all from the same
machine.
Maybe the bug is fixed in Package 2.6.21-1-k7 Version 2.6.21-4.
I will report after a few more tests.

----------------------------------------------
Kernel : 2.6.21-1-k7.*2.6.21-4
----------------------------------------------
Days with this kernel booted      (counted): 11 (Jun 22  until Jul  9 )
Reboots with this kernel in total (counted): 12
Reboots with EXT3 corruption      (counted): 0
% Errorfree days (roughly) / reboots       : 100% / 100%

----------------------------------------------
Kernel : 2.6.18-5-486.*2.6.18.dfsg.1-13
----------------------------------------------
Days with this kernel booted      (counted): 2 (Jul  9  until Jul 10 )
Reboots with this kernel in total (counted): 2
Reboots with EXT3 corruption      (counted): 0
% Errorfree days (roughly) / reboots       : 100% / 100%

----------------------------------------------
Kernel : 2.6.18-4-486.*2.6.18.dfsg.1-12
----------------------------------------------
Days with this kernel booted      (counted): 3 (Jul 10  until Jul 12 )
Reboots with this kernel in total (counted): 3
Reboots with EXT3 corruption      (counted): 1
% Errorfree days (roughly) / reboots       : 66% / 66%

----------------------------------------------
Kernel : 2.6.18-4-k7.*2.6.18.dfsg.1-12etch2
----------------------------------------------
Days with this kernel booted      (counted): 19 (May 18  until Jun 15 )
Reboots with this kernel in total (counted): 48
Reboots with EXT3 corruption      (counted): 12
% Errorfree days (roughly) / reboots       : 36% / 75%

----------------------------------------------
Kernel : 2.6.16.52
----------------------------------------------
Days with this kernel booted      (counted): 10 (Jun 13  until Jun 22 )
Reboots with this kernel in total (counted): 18
Reboots with EXT3 corruption      (counted): 1
% Errorfree days (roughly) / reboots       : 90% / 94%

----------------------------------------------
Kernel : 2.6.8-3-k7
----------------------------------------------
Days with this kernel booted      (counted): 37 (Apr  2  until May 18 )
Reboots with this kernel in total (counted): 51
Reboots with EXT3 corruption      (counted): 0
% Errorfree days (roughly) / reboots       : 100% / 100%


Regards,
Martin

Attachment: Kernel-EXT3-Corruption-Statistic.sh
Description: Bourne shell script


Reply to: