continued ext2fs corruption

continued ext2fs corruption

[Ian Wehrman]

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

hello all,
all kernels since 2.4.2 (including the latest 2.4.4) have resulted in major
ext2 filesystem corruption for me. pre-2.4.2 kernels work fine, as does
2.2.19. generally the errors i see while using the filesystem look like this:

EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in directory
 #508411: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0,
 name_len=0

i first saw this in february, along with a few other people, read the thread
here: 
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0102.2/1350.html

basically after booting one of these new kernels, i quickly start to see a lot
of filesystem errors, and i/o errors. on reboot, fsck finds piles of errors,
and eventually clears a lot of inodes. this is a real pain. 

i don't think i'm using any exotic hardware. i've attached the output of
lspci -vv (under 2.4.0-test9, the kernel i'm running now that's stable for
me). i do have one hard disk connected to a promise 20267 ultra ata 100 board,
but that drive has never had any corruption, just the disk connected to the
onboard ide controller. 

i'd really like to help track down the problem, please let me know if i can
provide any further information.

thanks,
ian wehrman

[-- Attachment #2: lspci_vv --]
[-- Type: text/plain, Size: 5530 bytes --]

00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 64
	Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
	Capabilities: <available only to root>

00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 128
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	I/O behind bridge: 00009000-00009fff
	Memory behind bridge: f6000000-f7ffffff
	Prefetchable memory behind bridge: fc000000-fdffffff
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B+

00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Region 4: I/O ports at 1400 [size=16]

00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Interrupt: pin D routed to IRQ 9
	Region 4: I/O ports at 10c0 [size=32]

00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] (rev 74)
	Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 80 (2500ns min, 2500ns max), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at 1000 [size=128]
	Region 1: Memory at f4020000 (32-bit, non-prefetchable) [size=128]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: <available only to root>

00:0e.0 Multimedia audio controller: Creative Labs SB Live! EMU10000 (rev 07)
	Subsystem: Creative Labs CT4780 SBLive! Value
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64 (500ns min, 5000ns max)
	Interrupt: pin A routed to IRQ 10
	Region 0: I/O ports at 10e0 [size=32]
	Capabilities: <available only to root>

00:0e.1 Input device controller: Creative Labs SB Live! (rev 07)
	Subsystem: Creative Labs Gameport Joystick
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Region 0: I/O ports at 1410 [size=8]
	Capabilities: <available only to root>

00:10.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550])
	Subsystem: US Robotics/3Com: Unknown device baba
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 9
	Region 0: I/O ports at 1418 [size=8]
	Capabilities: <available only to root>

00:11.0 Unknown mass storage controller: Promise Technology, Inc. 20267 (rev 02)
	Subsystem: Promise Technology, Inc.: Unknown device 4d33
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Interrupt: pin A routed to IRQ 3
	Region 0: I/O ports at 1430 [size=8]
	Region 1: I/O ports at 1424 [size=4]
	Region 2: I/O ports at 1428 [size=8]
	Region 3: I/O ports at 1420 [size=4]
	Region 4: I/O ports at 1080 [size=64]
	Region 5: Memory at f4000000 (32-bit, non-prefetchable) [size=128K]
	Expansion ROM at <unassigned> [disabled] [size=64K]
	Capabilities: <available only to root>

01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) (prog-if 00 [VGA])
	Subsystem: 3Dfx Interactive, Inc.: Unknown device 1137
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=32M]
	Region 1: Memory at fc000000 (32-bit, prefetchable) [size=32M]
	Region 2: I/O ports at 9000 [size=256]
	Expansion ROM at <unassigned> [disabled] [size=64K]
	Capabilities: <available only to root>

Re: continued ext2fs corruption

[Ian Wehrman]

Rob Todd <todd@hcs.ufl.edu> wrote:
> I am using RH 7.1 with the stock 2.4.2-2 kernel (although the same behavior
> shows up in 2.4.4 also compiled using gcc 2.96).  Not quite sure about
> hardware we share... it is a 1GHz P3 ServerWorks LE board (with the OSB4
> chipset) connecting to a Seagate ST320414A 20GB HD (UDMA 33).  We have
> several hundred other machines (including older ServerWorks boards) running
> 2.4.4 with no problem so I was extremely surprised to receive these 32
> machines and have every single one of them experience some sort of file
> system corruption.  I am running 2.2.19 right now on these 32 machines with
> no problems whatsoever.
> 
> Rob Todd <todd@hcs.ufl.edu> wrote:
> > If you receive an answer please let me know... I've been seeing the same
> > problems on a 1GHz P3 with a ServerWorks OSB4 chipset.

on the surface, it looks like your systems don't have anything in common with
mine. i'm running rh71 too, but that's only because running kernel 2.4.2 on my
previous rh62 system corrupted the filesystem so badly that i had to format
and reinstall. i admit i'm somewhat glad to hear i'm not the only one having
these problems, but it obviously isn't particularly widespread. are you also
getting errors like this:

EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in directory
#508411: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0,
name_len=0 

the disk that becomes corrupted for me is an IBM Deskstar (UDMA 33), and it's on
an intel 440BX chipset. does anyone here have any thoughts?

thanks,
ian