* 2.4.2 ext2fs corruption status
@ 2001-08-01 22:10 Mohamed DOLLIAZAL
2001-08-01 22:15 ` Andreas Dilger
0 siblings, 1 reply; 5+ messages in thread
From: Mohamed DOLLIAZAL @ 2001-08-01 22:10 UTC (permalink / raw)
To: linux-kernel
Hi all,
I am using RH 7.1 with the stock 2.4.2-2 kernel, I got several times my
disk corrupted and even lost the superblock. I have seen a lot messages
about the ext2fs corruption in kernel 2.4.2 but I didn't find what was
causing this problem (hardware or sofware). And if was bug, What kernel
should I use to avoid this problem.
I got these error messages :
EXT2-fs error (device sd(8,8)): ext2_new_block: Allocating block in
system zone - block = 786920
EXT2-fs error (device sd(8,8)): ext2_new_block: Free blocks count
corrupted for block group 3
EXT2-fs error (device sd(8,8)): ext2_readdir: bad entry in directory
#768546: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0,
name_len=0
Here is the the output of lspci -vv :
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
(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: 8
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=4M]
Capabilities: [a0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
(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: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00007000-00007fff
Memory behind bridge: de500000-de5fffff
Prefetchable memory behind bridge: de200000-de2fffff
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 22)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
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: VIA Technologies, Inc. Bus Master IDE (rev 10)
(prog-if 8a [Master SecP PriP])
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: 32
Region 4: I/O ports at ffa0 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 10)
(prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
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, cache line size 08
Interrupt: pin D routed to IRQ 11
Region 4: I/O ports at bc00 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 10)
(prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
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, cache line size 08
Interrupt: pin D routed to IRQ 11
Region 4: I/O ports at c000 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
30)
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-
Capabilities: [68] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
Controller (rev 20)
Subsystem: Giga-byte Technology: Unknown device 7600
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 C routed to IRQ 10
Region 0: I/O ports at cc00 [size=256]
Region 1: I/O ports at c800 [size=4]
Region 2: I/O ports at c400 [size=4]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:09.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (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: 64, cache line size 08
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 00008000-00009fff
Memory behind bridge: de600000-deefffff
Prefetchable memory behind bridge:
00000000de300000-00000000de300000
BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=220mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
00:0c.0 SCSI storage controller: Adaptec 7892A (rev 02)
Subsystem: Adaptec: Unknown device e2a0
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 (10000ns min, 6250ns max), cache line size 08
Interrupt: pin A routed to IRQ 9
BIST result: 00
Region 0: I/O ports at d000 [disabled] [size=256]
Region 1: Memory at dfbcf000 (64-bit, non-prefetchable)
[size=4K]
Expansion ROM at dfba0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0f.0 VGA compatible controller: Trident Microsystems 3DIm`age 975
(rev f3) (prog-if 00 [VGA])
Subsystem: Trident Microsystems 3DImage 9750
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 11
Region 0: Memory at dfc00000 (32-bit, non-prefetchable)
[size=4M]
Region 1: Memory at dfbe0000 (32-bit, non-prefetchable)
[size=128K]
Region 2: Memory at df400000 (32-bit, non-prefetchable)
[size=4M]
Expansion ROM at dfbd0000 [disabled] [size=64K]
02:04.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100]
(rev 05)
Subsystem: Intel Corporation EtherExpress PRO/100+ Dual Port
Adapter
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 (2000ns min, 14000ns max), cache line size 08
Interrupt: pin A routed to IRQ 5
Region 0: Memory at de3ff000 (32-bit, prefetchable) [size=4K]
Region 1: I/O ports at 9c00 [size=32]
Region 2: Memory at dee00000 (32-bit, non-prefetchable)
[size=1M]
Expansion ROM at ded00000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
02:05.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100]
(rev 05)
Subsystem: Intel Corporation EtherExpress PRO/100+ Dual Port
Adapter
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 (2000ns min, 14000ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at de3fe000 (32-bit, prefetchable) [size=4K]
Region 1: I/O ports at 9800 [size=32]
Region 2: Memory at dec00000 (32-bit, non-prefetchable)
[size=1M]
Expansion ROM at deb00000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Thanks for you help,
Mohamed.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: 2.4.2 ext2fs corruption status
2001-08-01 22:10 2.4.2 ext2fs corruption status Mohamed DOLLIAZAL
@ 2001-08-01 22:15 ` Andreas Dilger
0 siblings, 0 replies; 5+ messages in thread
From: Andreas Dilger @ 2001-08-01 22:15 UTC (permalink / raw)
To: Mohamed DOLLIAZAL; +Cc: linux-kernel
Mohammed DOLLIAZAL writes:
> I am using RH 7.1 with the stock 2.4.2-2 kernel, I got several times my
> disk corrupted and even lost the superblock. I have seen a lot messages
> about the ext2fs corruption in kernel 2.4.2 but I didn't find what was
> causing this problem (hardware or sofware). And if was bug, What kernel
> should I use to avoid this problem.
It could be the VIA chipset, but I'm not sure. One rule with the Linux
kernel is you should (almost) always be running the most recent kernel
before reporting a bug. This saves a lot of effort in tracking down
bugs that have alreay been fixed.
It may be that Red Hat has already released a new kernel RPM since that
time, or maybe you need to compile a new kernel.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <no.id>]
* Re: 2.4.2 ext2fs corruption status
[not found] <no.id>
@ 2001-08-02 0:20 ` Alan Cox
2001-08-01 19:40 ` Mohamed DOLLIAZAL
2001-08-02 12:27 ` Alan Cox
1 sibling, 1 reply; 5+ messages in thread
From: Alan Cox @ 2001-08-02 0:20 UTC (permalink / raw)
To: Andreas Dilger; +Cc: Mohamed DOLLIAZAL, linux-kernel
> It may be that Red Hat has already released a new kernel RPM since that
> time, or maybe you need to compile a new kernel.
The official VIA workaround fix is now in 2.4.6ac5 and 2.4.7ac*. The fixes
in the older kernels were mostly going to do the job but I dont know if they
were perfect for all cases
The -ac kernel tree also contains important fixes that avoid DMA timeouts
potentially causing disk corruption by forgetting to write sectors
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: 2.4.2 ext2fs corruption status
2001-08-02 0:20 ` Alan Cox
@ 2001-08-01 19:40 ` Mohamed DOLLIAZAL
0 siblings, 0 replies; 5+ messages in thread
From: Mohamed DOLLIAZAL @ 2001-08-01 19:40 UTC (permalink / raw)
To: Alan Cox; +Cc: Andreas Dilger, linux-kernel
Alan Cox wrote:
> > It may be that Red Hat has already released a new kernel RPM since that
> > time, or maybe you need to compile a new kernel.
>
> The official VIA workaround fix is now in 2.4.6ac5 and 2.4.7ac*. The fixes
> in the older kernels were mostly going to do the job but I dont know if they
> were perfect for all cases
>
> The -ac kernel tree also contains important fixes that avoid DMA timeouts
> potentially causing disk corruption by forgetting to write sectors
Hi Alan,
I'am sorry I forgot to mention that the filesystem corruption happened on
SCSI disks. I guess there is no DMA on the SCSI disks.
Do you think that the VIA fixes that are included in the 2.4.6ac5 kernel or
above may solve my problem.
Thanks for your help,
Mohamed.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.4.2 ext2fs corruption status
[not found] <no.id>
2001-08-02 0:20 ` Alan Cox
@ 2001-08-02 12:27 ` Alan Cox
1 sibling, 0 replies; 5+ messages in thread
From: Alan Cox @ 2001-08-02 12:27 UTC (permalink / raw)
To: Mohamed DOLLIAZAL; +Cc: Alan Cox, Andreas Dilger, linux-kernel
> I'am sorry I forgot to mention that the filesystem corruption happened on
> SCSI disks. I guess there is no DMA on the SCSI disks.
Well there is but its off the scsi controller so should be ok
> Do you think that the VIA fixes that are included in the 2.4.6ac5 kernel or
> above may solve my problem.
They might do, they might not. But they are worth checking
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-08-02 12:26 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-08-01 22:10 2.4.2 ext2fs corruption status Mohamed DOLLIAZAL
2001-08-01 22:15 ` Andreas Dilger
[not found] <no.id>
2001-08-02 0:20 ` Alan Cox
2001-08-01 19:40 ` Mohamed DOLLIAZAL
2001-08-02 12:27 ` Alan Cox
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.