From: Oleg Drokin <green@namesys.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: ext2 FS corruption with 2.5.59.
Date: Thu, 23 Jan 2003 17:26:38 +0300 [thread overview]
Message-ID: <20030123172638.A821@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301231402290.1589-100000@localhost.localdomain>
Hello!
On Thu, Jan 23, 2003 at 02:09:12PM +0000, Hugh Dickins wrote:
> > My test consists of running "fsx -c 1234 testfile", "iozone -a",
> > "dbench 60", "fsstress -p10 -n1000000 -d ." at the same time on the
> > tested FS.
> > fsx usually breaks just when dbench is finished.
> It was "dbench 100" which led me to investigate and post patch below
> a couple of days ago: worth trying again with this patch applied.
I thought your patch only fixes stuff with insufficient space and/or IO
errors.
Anyway I applied the patch and still can reproduce the problem.
Also I decided to run same test with ext3 and it deadlocked.
This time it was not absolutely vanilla kernel, so I am going to try it on
vanilla kernel and report back if it will be reproducable there.
(with stacktraces)
Bye,
Oleg
next prev parent reply other threads:[~2003-01-23 14:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 12:38 ext2 FS corruption with 2.5.59 Oleg Drokin
2003-01-23 14:09 ` Hugh Dickins
2003-01-23 14:26 ` Oleg Drokin [this message]
2003-01-23 14:39 ` Oleg Drokin
2003-01-24 10:32 ` Andrew Morton
2003-01-24 12:39 ` Oleg Drokin
2003-01-25 6:53 ` Andrew Morton
2003-01-25 12:36 ` Oleg Drokin
2003-01-25 23:13 ` Andrew Morton
2003-01-26 9:25 ` Oleg Drokin
2003-01-26 3:04 ` Andrew Morton
2003-01-26 3:28 ` William Lee Irwin III
2003-01-26 3:46 ` Andrew Morton
2003-01-26 4:14 ` William Lee Irwin III
2003-01-26 5:10 ` Andrew Morton
2003-01-27 22:59 ` Stephen Hemminger
2003-01-27 23:59 ` William Lee Irwin III
2003-01-26 11:11 ` Anton Blanchard
2003-01-26 11:23 ` Andrew Morton
2003-01-28 13:50 ` Christoph Hellwig
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=20030123172638.A821@namesys.com \
--to=green@namesys.com \
--cc=akpm@digeo.com \
--cc=hugh@veritas.com \
--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