Messages in this thread | | | Date | Thu, 09 May 2002 20:14:02 -0700 | From | Andrew Morton <> | Subject | Re: Kernel 2.4.18 + ext3 = filesystem corruption |
| |
Interesting domain name.
Silvan wrote: > > ... > I had a filesystem explosion (across the board corruption on all ext3 > partitions, brought to my attention by a rather nasty series of EXT3_fs > errors and an immediate crash) about a month back. > ...
I've just re-reviewed the 2.4.16 -> 2.4.18 diffs. There's really nothing there which could explain this. We have:
- lots of s/bread/sb_bread/etc. Which is rather unfortunate because it complicates any attempt to back out to 2.4.16's ext3.
- A bug fix for locking journal buffers (the infamous "request_list destroyed" bug)
- Some error-path-only code which remounts the fs readonly rather than taking down the machine when the unexpected happens.
> > My hardware: > > AMD K7-1000 on ASUS A7V (VIA Apollo KT133a chipset, integrated Promise > ATA-100 controller), 256 MB RAM, Linksys 10/100E NIC, USR PCI Performance > Pro modem, SB PCI 128, Riva TNT2 AGP video (running at 4X in BIOS and in X), > CREATIVE CD-RW RW8439E, CD-950E/TKU, Maxtor 94610H6, generic PS/2 mouse, > generic FD, and a 104-key keyboard.
I'd be suspecting this, frankly. Might be an IDE failure.
- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |