From: Oleg Drokin <green@namesys.com>
To: Bernhard Sadlowski <sadlowsk@mathematik.Uni-Bielefeld.DE>
Cc: reiserfs-list@namesys.com
Subject: Re: Stress test failure for reiserfs, but ext3 ok on Linux 2.4.20
Date: Wed, 15 Jan 2003 14:58:04 +0300 [thread overview]
Message-ID: <20030115145804.B31603@namesys.com> (raw)
In-Reply-To: <20030115115100.GB16645@mathematik.uni-bielefeld.de>
Hello!
On Wed, Jan 15, 2003 at 12:51:00PM +0100, Bernhard Sadlowski wrote:
> > Hm. This resembles me something.
> > Can you reproduce the same problem if you apply patches from
> > ftp://ftp.namesys.com/pub/reiserfs-for-2.4/testing/quota-2.4.20/
> > These patches add quota support to reiserfs, but also change some
> > new inode-related operation to prevent deadlocks like you are seeing.
> The unpatched kernel shows the hangs much earlier, so I assume that the
> above patches solve the problem. With the patches the load goes up very
> slowly but steady to "100" and I/O does not freeze anymore. vmstat and
> iostat still show activity. I assume you don't need any sysrq-t output
> now.
Ok. That's a good sign.
> Will the patches be included in 2.4.21?
No, they require quota support tha won't be included into 2.4 because of
new quota formats and stuff.
I will extract relevant bits from the patch though.
I will send you short version without quota once it will be ready.
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-15 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 2:35 Stress test failure for reiserfs, but ext3 ok on Linux 2.4.20 Bernhard Sadlowski
2003-01-15 10:43 ` Oleg Drokin
2003-01-15 11:51 ` Bernhard Sadlowski
2003-01-15 11:58 ` Oleg Drokin [this message]
2003-01-15 15:01 ` Oleg Drokin
2003-01-15 15:48 ` Bernhard Sadlowski
2003-01-15 15:51 ` Oleg Drokin
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=20030115145804.B31603@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sadlowsk@mathematik.Uni-Bielefeld.DE \
/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.