From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: ext2 issues with xfstests 113
Date: Tue, 1 Jun 2010 15:08:37 +0200 [thread overview]
Message-ID: <20100601130837.GF4275@quack.suse.cz> (raw)
In-Reply-To: <20100601090337.GA28085@lst.de>
On Tue 01-06-10 11:03:37, Christoph Hellwig wrote:
> On Mon, May 31, 2010 at 11:31:01PM +0200, Jan Kara wrote:
> > Hmm, interesting because I've run test 113 again with a kernel somewhere
> > between 2.6.34 and 2.6.35-rc1 and the filesystem is clean. So probably you
> > are able to hit some kind of race I'm not able to. Could you check whether
> > the corruption is caused by the O_DIRECT run or some other one?
>
> 113 is an AIO test, so it must be using O_DIRECT.
Now I see that the third run of aio-stress failed so yes, it's using
O_DIRECT.
> > Also could you get "e2image -r" of the filesystem, bzip2 it and put it
> > somewhere for download?
>
> I've jyst attached it as the compressed version is small enough (88k).
I've looked at the image and for both corrupted inodes it looks as if
we didn't write double-indirect block. The blocks which should be
presumably referenced from it are properly allocated so it couldn't be just
truncated or so. I've tried to reproduce the problem on another machine but
failed... Is there anything special in your setup? Also are there any
messages in the kernel log?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2010-06-01 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 9:46 ext2 issues with xfstests 113 Christoph Hellwig
2010-05-31 17:57 ` Jan Kara
2010-05-31 18:01 ` Christoph Hellwig
2010-05-31 21:31 ` Jan Kara
[not found] ` <20100601090337.GA28085@lst.de>
2010-06-01 10:26 ` Jan Kara
2010-06-01 13:08 ` Jan Kara [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=20100601130837.GF4275@quack.suse.cz \
--to=jack@suse.cz \
--cc=hch@lst.de \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).