2001-02-01 23:00:31

by Wolfgang Wegner

[permalink] [raw]
Subject: e2fs corruption with 2.4.0-ac12

Hi,

just for the records, as I saw some reports about fs corruption:
I had a case of e2fs corruption under 2.4.0-ac12 on an IDE drive
(Intel BX chipset) yesterday.
I was not able to reproduce it, all I can say it seemed to be related
to a single file on a 1GB partition, filled about 70%. I noticed
mkisofs reading from this filesystem aborting with an I/O error,
resulting in "attempt to access beyond end of device". The
filesystem was generated some days ago under 2.2.14 using
mke2fs 1.18.

The machine itself is running fine under 2.2.14 for several
months, the only flaw is this partition being unused up to
now.

If this of any interest and there is any more information
I should provide, let me know.

Regards,
Wolfgang


2001-02-02 04:07:47

by Patrice Belleville

[permalink] [raw]
Subject: Re: e2fs corruption with 2.4.0-ac12

On February 1, Wolfgang Wegner <[email protected]> writes:

> just for the records, as I saw some reports about fs corruption: I had
> a case of e2fs corruption under 2.4.0-ac12 on an IDE drive (Intel BX
> chipset) yesterday.

I also had such problems twice on my Sony VAIO PCGF-430, using
2.4.1-test10 + the ACPI patch "acpi-20010125.diff". In both cases, the
system locked up tight (X wasn't responding, and I was unable to switch to
a different virtual console), a cold boot was required, and there was
filesystem corruption that forced me to run fsck manually. Luckily, no
essential file was destroyed.

As the files involved were certainly not in the process of being updated
when the system locked up [in one case it involved man pages], I don't
believe the corruption was caused directly by the lockup. I include the
relevant part of the output from /sbin/lspci below.

I went back to 2.4.0, which works perfectly apart from the fact that
kacpid oopses on startup, and has not seen any corruption since. Please
let me know if there's any additional information that I can provide to
help track the problem down.

Patrice

---
**------------------------------------------------------------------------
** Patrice Belleville ([email protected]) (604) 822-9870
** Instructor and Departmental advisor, Department of Computer Science
**------------------------------------------------------------------------

---
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
(rev 03)
Subsystem: Sony Corporation: Unknown device 806f
Flags: bus master, medium devsel, latency 64
Memory at 40000000 (32-bit, prefetchable) [size=16M]
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])
Flags: bus master, 66Mhz, medium devsel, latency 128
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
Memory behind bridge: fe800000-fecfffff
Prefetchable memory behind bridge: fd000000-fdffffff

00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
Flags: bus master, medium devsel, latency 0

00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
(prog-if 80 [Master])
Flags: bus master, medium devsel, latency 64
I/O ports at fc90 [size=16]

00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
(prog-if 00 [UHCI])
Flags: medium devsel, IRQ 9
I/O ports at fca0 [size=32]

00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 03)
Flags: medium devsel