From: Jens Axboe <axboe@suse.de>
To: Ewan Mac Mahon <ecm103@york.ac.uk>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Christopher Li <chrisl@vmware.com>,
"'Linux Kernel '" <linux-kernel@vger.kernel.org>,
"'ext2-devel@lists.sourceforge.net '"
<ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] Re: 2.5.46 ext3 errors
Date: Wed, 6 Nov 2002 18:08:44 +0100 [thread overview]
Message-ID: <20021106170844.GA897@suse.de> (raw)
In-Reply-To: <20021106161234.GB17138@york.ac.uk>
On Wed, Nov 06 2002, Ewan Mac Mahon wrote:
> On Wed, Nov 06, 2002 at 02:05:21PM +0100, Jens Axboe wrote:
> > On Wed, Nov 06 2002, Stephen C. Tweedie wrote:
> > >
> > > error is just ext3's normal reaction to a fatal error detected in the
> > > filesystem, so that in itself isn't a worry. The cause of the problem
> > > it spotted is the worry; is this reproducible?
> >
> > I can try. The kernel run had my rbtree deadline patches, however
> > they've been well tested and are likely not the cause of the problem. It
> > cannot be 100% ruled out though, I'm testing for this very thing right
> > now. I will let you know what happens.
>
> I think I can rule that out, I've got much the same[1] from a vanilla
> 2.5.46, and the filesystem's recent history has been plain 2.5.XXs as
> well.
Interesting, so it smells like a generic problem. I cannot reproduce it
on my test box (been running kernel compiles and dbenches all afternoon)
with the same kernel. I've got 2.5.46-BK on the desktop again now, we'll
see what happens....
For the record, test box is P3-800MHz SMP, 512MiB RAM. Desktop is a
MP1800+ SMP, 1GiB of RAM.
--
Jens Axboe
prev parent reply other threads:[~2002-11-06 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C77B405ABE6D611A93A00065B3FFBBA36A493@PA-EXCH2>
2002-11-06 10:18 ` [Ext2-devel] Re: 2.5.46 ext3 errors Stephen C. Tweedie
2002-11-06 13:05 ` Jens Axboe
2002-11-06 16:12 ` Ewan Mac Mahon
2002-11-06 17:08 ` Jens Axboe [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=20021106170844.GA897@suse.de \
--to=axboe@suse.de \
--cc=chrisl@vmware.com \
--cc=ecm103@york.ac.uk \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox