From: Oleg Drokin <green@namesys.com>
To: Lorenzo Allegrucci <l.allegrucci@tiscali.it>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.6.0-test4 reiserfs oops
Date: Wed, 27 Aug 2003 10:46:13 +0400 [thread overview]
Message-ID: <20030827064613.GB29131@namesys.com> (raw)
In-Reply-To: <200308261559.20668.l.allegrucci@tiscali.it>
Hello!
On Tue, Aug 26, 2003 at 03:59:20PM +0000, Lorenzo Allegrucci wrote:
> > > > > I have got this oops running fsstress and fsx-linux
> > > > > on a 20Gb reiserfs partition. Fully reproducible.
> > > > What are the options to fsx and fsstress?
> > > fsx-linux linux-2.5.0.tar.bz2 :)
> > > mkdir d
> > > fsstress -d d -n 1000000 -p 10
> > > The oops follows immediately.
> > works for me without any patches.
>
> This is easier to reproduce:
> touch file
> mkdir d
> fsstress -d d -n 1000000 -p 10
> As soon as I run "fsx-linux file" on another console I get the oops.
> (However fsx-linux without fsstress is not sufficient)
Well, actually I was able to reproduce it yesterday later after replying to you.
And we got some other similar reports under different workloads.
My initial suspiction about the cause was right. and that fix I sent to you
on the second try is the correct thing to do.
The actual problem came from AIO people merging incorrect patch
into reiserfs code.
Bye,
Oleg
prev parent reply other threads:[~2003-08-27 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 20:47 2.6.0-test4 reiserfs oops Lorenzo Allegrucci
2003-08-26 8:32 ` Oleg Drokin
2003-08-26 11:46 ` Lorenzo Allegrucci
2003-08-26 10:38 ` Oleg Drokin
2003-08-26 15:59 ` Lorenzo Allegrucci
2003-08-27 6:46 ` Oleg Drokin [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=20030827064613.GB29131@namesys.com \
--to=green@namesys.com \
--cc=l.allegrucci@tiscali.it \
--cc=reiserfs-list@namesys.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 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.