From: "Mohammad A. Haque" <mhaque@haque.net>
To: Alexander Viro <viro@math.psu.edu>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Tigran Aivazian <tigran@veritas.com>
Subject: Re: ext2 filesystem corruptions back from dead? 2.4.0-test11
Date: Fri, 24 Nov 2000 00:42:40 -0500 [thread overview]
Message-ID: <3A1DFFD0.22C8CEC3@haque.net> (raw)
In-Reply-To: <Pine.GSO.4.21.0011240006040.12702-100000@weyl.math.psu.edu>
I got the error while I was compiling XFree86 4 CVS and kernel. So
that's what I've been doing in multiples along witha couple otehr things
thrown inthe mix to generate lots of disk i/o.
Nothing yet, but I'm pretty sure my machine hates me for putting it
through this.
Alexander Viro wrote:
> Bloody interesting. I don't see anything recent that could affect the
> areas in question. Intersting versions to check: 11-pre5 and 11-pre6.
> It smells like buffer cache corruption, but I don't see anything
> relevant. __generic_unplug_device() change loock pretty innocent,
> ditto for bh_kmap() ones in raid5 and on ext2 side we had two obviously
> equivalent replacements (pre5->pre6). No buffer.c changes, no VM ones.
> Urgh.
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
mhaque@haque.net
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
batmanppc@themes.org
=====================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-24 6:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 5:51 ext2 filesystem corruptions back from dead? 2.4.0-test11 Mohammad A. Haque
2000-11-23 6:03 ` Neil Brown
2000-11-23 9:37 ` Alexander Viro
2000-11-23 11:05 ` Neil Brown
2000-11-23 12:12 ` Neil Brown
2000-11-23 16:36 ` Alexander Viro
2000-11-23 17:12 ` Alexander Viro
2000-11-23 20:51 ` Tigran Aivazian
2000-11-23 20:56 ` Mohammad A. Haque
2000-11-24 2:29 ` Neil Brown
2000-11-24 5:32 ` Alexander Viro
2000-11-24 5:42 ` Mohammad A. Haque [this message]
2000-11-24 5:57 ` Alexander Viro
2000-11-27 5:49 ` Neil Brown
2000-11-28 22:55 ` Mohammad A. Haque
2000-11-29 4:37 ` Mohammad A. Haque
2000-11-29 6:44 ` Ion Badulescu
2000-11-29 7:08 ` Mohammad A. Haque
2000-11-29 7:20 ` Ion Badulescu
2000-11-29 7:23 ` Mohammad A. Haque
2000-11-29 8:54 ` Tigran Aivazian
2000-11-29 10:01 ` Mohammad A. Haque
2000-11-23 12:52 ` Guest section DW
2000-11-24 4:58 ` Ion Badulescu
2000-11-24 5:29 ` Guest section DW
2000-11-24 5:34 ` Mohammad A. Haque
2000-11-24 8:51 ` Ion Badulescu
2000-11-24 13:35 ` Guest section DW
2000-11-24 17:41 ` Linus Torvalds
2000-11-24 15:06 ` Mohammad A. Haque
2000-11-24 5:59 ` Andre Hedrick
2000-11-24 6:11 ` Alexander Viro
2000-11-24 6:30 ` Andre Hedrick
2000-11-24 7:03 ` Alexander Viro
2000-11-24 7:58 ` Andre Hedrick
2000-11-24 8:43 ` Ion Badulescu
2000-11-24 11:06 ` Mike Ricketts
2000-11-24 11:11 ` Tigran Aivazian
2000-11-25 2:21 ` Andre Hedrick
2000-11-23 6:40 ` Andreas Dilger
2000-11-23 7:22 ` Pär-Ola Nilsson
-- strict thread matches above, loose matches on Subject: below --
2000-11-25 22:42 Rick Bunke
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=3A1DFFD0.22C8CEC3@haque.net \
--to=mhaque@haque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=tigran@veritas.com \
--cc=viro@math.psu.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.