From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Kevin Shanahan <kmshanah@ucwb.org.au>,
Andreas Dilger <adilger@sun.com>, Alex Tomas <bzzz@sun.com>,
linux-ext4@vger.kernel.org
Subject: Re: More ext4 acl/xattr corruption - 4th occurence now
Date: Thu, 14 May 2009 20:21:05 -0500 [thread overview]
Message-ID: <4A0CC381.3080804@redhat.com> (raw)
In-Reply-To: <20090514212325.GG21316@mit.edu>
Theodore Tso wrote:
> On Fri, May 15, 2009 at 06:32:45AM +0930, Kevin Shanahan wrote:
>> Okay, so now I've booted into 2.6.29.3 + check_block_validity patch +
>> short circuit i_cached_extent patch, mounted the fs without
>> nodelalloc. I was able to run the full exchange backup without
>> triggering the check_block_validity error.
>
> Great!
>
> So here's the final fix (it replaces the short circuit i_cached_extent
> patch) which I plan to push to Linus. It should be much less of a
> performance hit than simply short-circuiting i_cached_extent...
>
> Thanks so much for helping to find track this down!!! If ever someone
> deserved an "Ext4 Baker Street Irregulars" T-shirt, it would be
> you....
>
> - Ted
So here's a fio job I thought would try to hit this ...
[global]
ioengine=libaio
iodepth=1
filesize=4g
bs=1m
norandommap
direct=1
loops=500
size=16g
[setup]
filename=file
rw=randwrite
loops=1
[thread1]
stonewall
filename=file
rw=randwrite
[thread2]
filename=file
rw=randread
it should lay out a 4g file in random 1m direct IOs to fragment it and
get a lot of extents, then launch 2 threads, one each doing random reads
and random writes of that same file.
I can't make this trip it, though ...
-Eric
next prev parent reply other threads:[~2009-05-15 1:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 6:26 More ext4 acl/xattr corruption - 4th occurence now Kevin Shanahan
2009-05-13 23:56 ` Kevin Shanahan
2009-05-14 4:40 ` Theodore Tso
2009-05-14 11:07 ` Kevin Shanahan
2009-05-14 11:17 ` Manish Katiyar
2009-05-14 12:30 ` Theodore Tso
2009-05-14 13:25 ` Kevin Shanahan
2009-05-14 14:07 ` Theodore Tso
2009-05-14 14:30 ` Kevin Shanahan
2009-05-14 15:44 ` Eric Sandeen
2009-05-14 21:07 ` Kevin Shanahan
2009-05-14 21:08 ` Eric Sandeen
2009-05-14 16:12 ` Theodore Tso
2009-05-14 21:02 ` Kevin Shanahan
2009-05-14 21:23 ` Theodore Tso
2009-05-14 21:33 ` Kevin Shanahan
2009-05-15 23:18 ` Kevin Shanahan
2009-05-15 1:21 ` Eric Sandeen [this message]
2009-05-15 12:50 ` Theodore Tso
2009-05-15 12:58 ` Eric Sandeen
2009-05-15 15:24 ` Eric Sandeen
2009-05-15 16:27 ` Eric Sandeen
2009-05-15 4:55 ` Aneesh Kumar K.V
2009-05-15 10:11 ` Theodore Tso
2009-05-15 13:07 ` Theodore Tso
2009-05-19 10:00 ` Thierry Vignaud
2009-05-19 11:36 ` Theodore Tso
2009-05-19 12:01 ` Alex Tomas
2009-05-19 15:04 ` Theodore Tso
2009-05-19 15:16 ` Alex Tomas
2009-05-19 15:18 ` Thierry Vignaud
2009-05-15 3:57 ` Alex Tomas
2009-05-15 4:58 ` Aneesh Kumar K.V
2009-05-15 10:27 ` Theodore Tso
2009-05-18 2:14 ` [PATCH] ext4: Add a comprehensive block validity check to ext4_get_blocks() (Was: More ext4 acl/xattr corruption - 4th occurence now) Theodore Tso
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=4A0CC381.3080804@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=bzzz@sun.com \
--cc=kmshanah@ucwb.org.au \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).