From: Andrew Morton <akpm@zip.com.au>
To: Silvan <silvan@windows-sucks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.18 + ext3 = filesystem corruption
Date: Thu, 09 May 2002 20:14:02 -0700 [thread overview]
Message-ID: <3CDB3AFA.31A377F@zip.com.au> (raw)
In-Reply-To: <200205092156.12911.silvan@windows-sucks.com>
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.
-
prev parent reply other threads:[~2002-05-10 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 1:56 Kernel 2.4.18 + ext3 = filesystem corruption Silvan
2002-05-10 3:14 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CDB3AFA.31A377F@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=silvan@windows-sucks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.