From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.rutgers.edu
Subject: The file system corruption bug (Summary)
Date: Wed, 23 Jun 1999 13:20:57 +0100 (BST) [thread overview]
Message-ID: <E10wm1T-0008P3-00@the-village.bc.nu> (raw)
Ok this is the distilled info so far
2.2.7 -> 2.2.9 broke a small number of systems. I can't tell if 2.2.8 was
a problem or not. 2.2.8 had enough other problems nobody ran it.
The reports of 2.2.7 worked 2.2.9/10 blow up all fall into the following
categories
o Block numbers off the end of the disk
o Reports of incorrect bitmaps
o Bizarre C compiler error reports
With the cases I followed up on, hitting the reset button after such odd
reports generally made them vanish. That is the corruption was in memory
not on media. Unlike the other noise reports there is a consistent "2.2.7 OK
2.2.9 fails" message.
It doesn't matter what platform - PMac (actually this is the worst hit)
Mips x86 all have reports. IDE and SCSI seem affected.
The most bizarre part of the whole matter is that a given machine will almost
always be affected by the same variant of the problem not a mix.
Lower memory machines seem most likely to trip it.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~1999-06-23 12:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E10wm1T-0008P3-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
/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.