From: Jens Axboe <axboe@suse.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
"David S. Miller" <davem@redhat.com>,
viro@math.psu.edu, linux-kernel@vger.kernel.org,
tytso@valinux.com
Subject: Re: 2.4.0-test11 ext2 fs corruption
Date: Wed, 29 Nov 2000 02:11:50 +0100 [thread overview]
Message-ID: <20001129021150.A24264@suse.de> (raw)
In-Reply-To: <E2C40AB5D29@vcnet.vc.cvut.cz> <20001129014329.C23771@suse.de> <20001129020852.C20971@athlon.random>
In-Reply-To: <20001129020852.C20971@athlon.random>; from andrea@suse.de on Wed, Nov 29, 2000 at 02:08:52AM +0100
On Wed, Nov 29 2000, Andrea Arcangeli wrote:
> Side note: that could generate mem/io corruption only on headactive devices
> (like IDE).
Yep, that's why I told Linus it was a long shot and couldn't possibly
account for all the corruption cases reported. And one would expect
fs corruption to go with that as well. So it's of course a long shot,
but still worth trying for Petr.
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
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-29 1:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 21:46 2.4.0-test11 ext2 fs corruption Petr Vandrovec
2000-11-29 0:43 ` Jens Axboe
2000-11-29 1:08 ` Andrea Arcangeli
2000-11-29 1:11 ` Jens Axboe [this message]
2000-11-29 1:32 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2000-11-29 12:41 Petr Vandrovec
2000-11-29 12:21 schwidefsky
2000-11-29 12:43 ` Alexander Viro
2000-11-28 21:10 Petr Vandrovec
2000-11-28 20:04 ` David S. Miller
2000-11-28 20:41 ` Alexander Viro
2000-11-29 16:26 ` Daniel Phillips
2000-11-28 20:32 Petr Vandrovec
2000-11-28 20:02 ` Alexander Viro
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=20001129021150.A24264@suse.de \
--to=axboe@suse.de \
--cc=VANDROVE@vc.cvut.cz \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@valinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox