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 13:43:15 +0300 [thread overview]
Message-ID: <20030115134315.A31068@namesys.com> (raw)
In-Reply-To: <20030115023559.GA14694@mathematik.uni-bielefeld.de>
Hello!
On Wed, Jan 15, 2003 at 03:35:59AM +0100, Bernhard Sadlowski wrote:
> I am using the attached stess.sh script (probably from this mailinglist)
> for creating load on a reiserfs filesystem, which forks 100
> (read,write,delete) processes:
> # mkreiserfs /dev/sda4
> # mount /dev/sda4 /backup
> # stress.sh -c /usr -n 100 /backup
> Then wait until /backup fills up.
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.
> Any I/O freezes and even after killing the script, the remaining cp and
> mv commands don't terminate. They are in status "D". A simle "ls
> /backup" never comes back. Only a hard powerdown fixes this situation,
> because "init 6" etc. doesn't work. I have even activated the reiserfs
> debug, but I don't see any additional info.
Try executing sysrq-t after the lockup happens, then send us decoded output
plese.
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-15 10:43 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 [this message]
2003-01-15 11:51 ` Bernhard Sadlowski
2003-01-15 11:58 ` Oleg Drokin
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=20030115134315.A31068@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.