Skip to contentSkip to conversation

ext2fs corruption again

DISCUSSION Kristian Peters 5 participants 6 messages Sep 15, 2001

lore
Share & tools
lore
#0 lore raw

Hello.

For about 3 weeks I sent a report that I've got very strange kernel error messages.

I changed my harddrive to IBM 75 GB because someone said that IBM's 40 GB harddisks are not very stable.

Today I've got these from the kernel (with the new hd):

Sep 15 10:01:58 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4215
Sep 15 10:01:58 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4217
Sep 15 10:01:59 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4234
Sep 15 10:01:59 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4236
Sep 15 10:01:59 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4239
Sep 15 10:02:03 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4847
Sep 15 10:02:03 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4848
Sep 15 10:02:03 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4852
Sep 15 10:02:03 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4855
Sep 15 10:02:06 adlib kernel: EXT2-fs error (device ide0(3,5)): ext2_new_block:
Allocating block in system zone - block = 174
Sep 15 10:02:06 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: Freeing blocks in system zones - Block = 179, count = 3
Sep 15 10:02:09 adlib kernel: EXT2-fs error (device ide0(3,5)):

ext2_free_blocks: bit already cleared for block 4839

Then I did an e2fsck on that device (hda5) and the errors occured after the check (and a complete reboot) again:

Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4163
Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4166
Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4131
Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4132
Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4155
Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4156
Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4157
Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4161
Sep 15 10:10:38 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 4162
Sep 15 10:10:43 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 716
Sep 15 10:10:43 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 717
Sep 15 10:10:43 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 720
Sep 15 10:10:43 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 723
Sep 15 10:10:43 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 724
Sep 15 10:10:43 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 725
Sep 15 10:10:43 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block 726
Sep 15 10:10:43 adlib kernel: EXT2-fs error (device ide0(3,5)):

ext2_free_blocks: bit already cleared for block 727

I've written down all e2fsck messages by hand. ;-) And I compared them.

The following messages from e2fsck are always the same even on the old and on the new hd. Here they are:

Duplicate/bad bock(s) in inode: 97: 643 Duplicate/bad bock(s) in inode: 100: 649 Duplicate/bad bock(s) in inode: 101: 650 651 Duplicate/bad bock(s) in inode: 102: 652 Duplicate/bad bock(s) in inode: 103: 653 656 Duplicate/bad bock(s) in inode: 104: 659 660 Duplicate/bad bock(s) in inode: 105: 661 662 663 664 665 666 Duplicate/bad bock(s) in inode: 106: 667 668 Duplicate/bad bock(s) in inode: 107: 669 671 Duplicate/bad bock(s) in inode: 108: 672 673 674 Duplicate/bad bock(s) in inode: 110: 678

Inodes 643-678 are always connected to faults.

The following files are always in connection with these errors:
/var/log/wtmp
/var/log/messages

The old hd was hda: IBM-DTLA-305040, ATA DISK drive. The new is: hda:
IBM-DTLA-307075, ATA DISK drive.

hdparm says:
Model=IBM-DTLA-307075, FwRev=TXAOA50C, SerialNo=YSDYSFN9998 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40 BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=8 CurCHS=17475/15/63, CurSects=-78446341, LBA=yes, LBAsects=150136560 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 AdvancedPM=yes: disabled (255)
Drive Supports : ATA/ATAPI-5 T13 1321D revision 1 : ATA-2 ATA-3 ATA-4 ATA-5

I currently use linux 2.4.9 and e2fsprogs 1.23 and fileutils-4.1 and a modified RedHat 6.2. These errors only occured with linux>=2.4.5-ac11.

I might say this is definitely an error with ext2 !

Kristian

·· · · reach me :: · ·· ·· · · ·· · ·· · ··· · ·

                           :: http://www.korseby.net
                           :: http://www.tomlab.de

[email protected] ....::

#1 lore raw
Quoted 2 lines · Kristian Peters

I changed my harddrive to IBM 75 GB because someone said that IBM's 40 GB harddisks are not very stable.

[....]

Quoted 1 line

I might say this is definitely an error with ext2 !

I might say that you could have tried a complete different make drive. who says that the 75 MB IBM is ok ?

maybe the same design mistake was made or so. just a thought.

options to see if something weird isn't due to hardware could be to not use dma, change pio modes, e.g. relax the drive settings.

not that I say IBM's drive is bad, it's just a thought.

Signature · 3 lines
Grobbebol's Home                   |  Don't give in to spammers.   -o)
http://www.xs4all.nl/~bengel       | Use your real e-mail address   /\
Linux 2.2.16 SMP 2x466MHz / 256 MB |        on Usenet.             _\_v  
#2 lore raw
In reply to Kristian Peters
Quoted 1 line · Roeland Th. Jansen

not that I say IBM's drive is bad, it's just a thought.

They are bad if it's hardware-related. The big one is manufactured in Hungary, the other one in Thaiwan.

The error occured again.

I post the new errors. Maybe you can see any structure in it.

Sep 15 16:16:23 adlib kernel: EXT2-fs error (device ide0(3,5)): ext2_free_blocks: bit already cleared for block (5412-5427)

e2fsck reported the following on that device (hda5):

++ entries are new with this check
-- entries only appeared earlier

Duplicate/bad bock(s) in inode:  97: 643 +644+
Duplicate/bad bock(s) in inode:  98: +647+
Duplicate/bad bock(s) in inode:  99: +648+
Duplicate/bad bock(s) in inode: 100: 649
Duplicate/bad bock(s) in inode: 101: 650 651
Duplicate/bad bock(s) in inode: 102: 652
Duplicate/bad bock(s) in inode: 103: 653 656 +657+
Duplicate/bad bock(s) in inode: 104: +658+ 659 660
Duplicate/bad bock(s) in inode: 105: 661 662 663 664 665 666
Duplicate/bad bock(s) in inode: 106: 667 -668-
Duplicate/bad bock(s) in inode: 107: 669 -671-

-Duplicate/bad bock(s) in inode: 108: 672 673 674- -Duplicate/bad bock(s) in inode: 110: 678-

767011: 647 648 649 650 651 652 653 654 671 832166: 655 656 657 658 659 660 661 662 832170: 643 644
832178: 663 664 665 666 667

832178 is /var/log/boot.log
832170 is /var/log/wtmp
832166 is /var/log/messages
767011 is /home/tisi/syslog

Only syslog related files are concerned.

syslog is configured that it will accept logs from other machines. Maybe there's a possibility that these strange errors were caused by the network-card or -driver ? I own an eepro100. Just a thought...

These errors occured since 2.4.5 that's why I think it's software-related.

I'll try to use 'hdparm -d1 -X33 /dev/hda' and other modes to see if it occurs again. But testing could take some time. It appears ~~ every second day.

Kristian

·· · · reach me :: · ·· ·· · · ·· · ·· · ··· · ·

                         :: http://www.korseby.net
                         :: http://www.tomlab.de

[email protected] ....::

#3 lore raw
In reply to Kristian Peters
Quoted 5 lines · Kristian Peters

For about 3 weeks I sent a report that I've got very strange kernel error messages.

I changed my harddrive to IBM 75 GB because someone said that IBM's 40 GB harddisks are not very stable.

...

Quoted 8 lines

The following files are always in connection with these errors:
/var/log/wtmp
/var/log/messages

The old hd was hda: IBM-DTLA-305040, ATA DISK drive. The new is: hda:
IBM-DTLA-307075, ATA DISK drive.

...

Quoted 5 lines

I currently use linux 2.4.9 and e2fsprogs 1.23 and fileutils-4.1 and a modified RedHat 6.2. These errors only occured with linux>=2.4.5-ac11.

I might say this is definitely an error with ext2 !

You need to provide more information such as what kind of motherboard or ide chipset you are using.

Signature · 8 lines
=====================================================================
Mohammad A. Haque                              http://www.haque.net/ 
                                               [email protected]

  "Alcohol and calculus don't mix.             Project Lead
   Don't drink and derive." --Unknown          http://wm.themes.org/
                                               [email protected]
=====================================================================
#4 lore raw
In reply to Kristian Peters

*Soooorrrry for sending the first message of this thread 3 times... But the mailing list still returns my mails...*

Quoted 2 lines · Mohammad A. Haque

You need to provide more information such as what kind of motherboard or ide chipset you are using.

Ok. I already did that before and will do it again. ;-)

As you'll see I have no VIA chipset.

[root@adlib /root]# cat /proc/interrupts
CPU0

  0:     424127          XT-PIC  timer
  1:      20206          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
 11:     186306          XT-PIC  es1371, bttv, eth0
 12:      94563          XT-PIC  PS/2 Mouse
 14:     117603          XT-PIC  ide0
 15:         17          XT-PIC  ide1
NMI:          0
ERR:          0

[root@adlib /root]# cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 3).
Master Capable. Latency=64.
Prefetchable 32 bit memory at 0x44000000 [0x47ffffff].
Bus 0, device 1, function 0:
PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 3).
Master Capable. Latency=64. Min Gnt=140.
Bus 0, device 14, function 0:

    Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 5).
      IRQ 11.
      Master Capable.  Latency=66.  Min Gnt=8.Max Lat=56.
      Prefetchable 32 bit memory at 0x48100000 [0x48100fff].
      I/O at 0x1000 [0x101f].
      Non-prefetchable 32 bit memory at 0x48000000 [0x480fffff].
  Bus  0, device  15, function  0:
    Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 6).
      IRQ 11.
      Master Capable.  Latency=64.  Min Gnt=12.Max Lat=128.
      I/O at 0x1080 [0x10bf].
  Bus  0, device  16, function  0:
    Multimedia video controller: Brooktree Corporation Bt878 (rev 17).
      IRQ 11.
      Master Capable.  Latency=66.  Min Gnt=16.Max Lat=40.
      Prefetchable 32 bit memory at 0x48200000 [0x48200fff].
  Bus  0, device  16, function  1:
    Multimedia controller: Brooktree Corporation Bt878 (rev 17).
      IRQ 11.
      Master Capable.  Latency=66.  Min Gnt=4.Max Lat=255.
      Prefetchable 32 bit memory at 0x48300000 [0x48300fff].
  Bus  0, device  20, function  0:
    ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2).
  Bus  0, device  20, function  1:
    IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1).
      Master Capable.  Latency=64.
      I/O at 0x1040 [0x104f].
  Bus  0, device  20, function  2:
    USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1).
      IRQ 11.
      Master Capable.  Latency=64.
      I/O at 0x1020 [0x103f].
  Bus  0, device  20, function  3:
    Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2).
      IRQ 9.
  Bus  1, device   0, function  0:
    VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 130).
      IRQ 11.
      Master Capable.  Latency=64.  Min Gnt=16.Max Lat=32.
      Prefetchable 32 bit memory at 0x42000000 [0x43ffffff].
      Non-prefetchable 32 bit memory at 0x40800000 [0x40803fff].
      Non-prefetchable 32 bit memory at 0x40000000 [0x407fffff].

[root@adlib /root]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 3
cpu MHz : 597.416
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat p
se36 mmx fxsr sse
bogomips : 1192.75
[root@adlib /root]# cat /proc/filesystems

nodev   proc
nodev   sockfs
nodev   tmpfs
nodev   shm
nodev   pipefs
        ext2
        msdos
        vfat
        iso9660

nodev devfs
umsdos
nodev devpts
nodev nfs
[root@adlib /root]# cat /proc/dma
4: cascade

Kristian

·· · · reach me :: · ·· ·· · · ·· · ·· · ··· · ·

                         :: http://www.korseby.net
                         :: http://www.tomlab.de

[email protected] ....::

#5 lore raw
In reply to Kristian Peters
Quoted 5 lines · Kristian

I'll try to use 'hdparm -d1 -X33 /dev/hda' and other modes to see if it occurs again. But testing could take some time. It appears ~~ every second day.

Kristian

If it takes that long, then make sure you start with ''hdparm -d0 /dev/hda'.

Mike