From: Oleg Drokin <green@namesys.com>
To: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 / reiserfs data corruption, 2.5-bk
Date: Tue, 10 Jun 2003 12:43:23 +0400 [thread overview]
Message-ID: <20030610084323.GA16435@namesys.com> (raw)
In-Reply-To: <20030609193541.GA21106@suse.de>
Hello!
On Mon, Jun 09, 2003 at 08:35:55PM +0100, Dave Jones wrote:
> 2.5 Bitkeeper tree as of last 24 hrs. Running a lot
> of disk IO stress (multiple fsstress, over 100 fsx instances,
> and random sync calling) produced failures on both reiserfs
> and ext3.
> Tests were done on seperate disks, but concurrently.
Do you have smp or preempt enabled?
Bye,
Oleg
next prev parent reply other threads:[~2003-06-10 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 19:35 ext3 / reiserfs data corruption, 2.5-bk Dave Jones
2003-06-10 8:43 ` Oleg Drokin [this message]
2003-06-10 9:20 ` Dave Jones
2003-06-10 21:44 ` Nathan Conrad
2003-06-10 18:11 ` Bartlomiej Zolnierkiewicz
2003-06-10 22:18 ` Nathan Conrad
2003-06-10 20:59 ` Andrew Morton
2003-06-12 5:20 ` ext3 / reiserfs data corruption, 2.5-bk; NULL pointer dereference bug Nathan Conrad
2003-06-10 22:49 ` ext3 / reiserfs data corruption, 2.5-bk Dave Jones
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=20030610084323.GA16435@namesys.com \
--to=green@namesys.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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