From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Bug in delayed allocation: really bad block layouts!
Date: Sun, 10 Aug 2008 13:54:50 -0500 [thread overview]
Message-ID: <489F397A.1040709@redhat.com> (raw)
In-Reply-To: <20080810182231.GB15353@mit.edu>
Theodore Tso wrote:
> On Sun, Aug 10, 2008 at 12:54:00PM -0500, Eric Sandeen wrote:
>> Hm, and I tried writing out 10 files in order as a simple test but
>> umount/remount brought me back many 0-byte files, I need to update my
>> patchset I guess. :)
>>
>
> One of the questions in my mind is whether this is a regression
> triggered by the some of our most recent patches.... since I only
> have 2.2% files reported a fragmented by e2fsck, and if this problem
> had always been there, I would have expected a much higher
> fragmentation number. So if you have some older kernels, you might
> want to see if you can replicate the problem. I've since found that
> just doing a copy via "(tar -cf - -C / usr/include ) | tar -C /mnt -xf -)"
> is sufficient to see the problem. Just add a "sync; sleep 5" before
> the umount. :-)
It may be; I tried this and then a quick filefrag run:
# filefrag usr/include/*.h | grep -v extents | awk -F : '{print $2}' |
sort | uniq -c
146 1 extent found
so everything came out contiguous.
This was with 2.6.27-0.186.rc0.git15.fc10.x86_64
-Eric
next prev parent reply other threads:[~2008-08-10 18:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 17:30 Bug in delayed allocation: really bad block layouts! Theodore Ts'o
2008-08-10 17:54 ` Eric Sandeen
2008-08-10 18:22 ` Theodore Tso
2008-08-10 18:54 ` Eric Sandeen [this message]
2008-08-10 20:04 ` Eric Sandeen
2008-08-11 1:46 ` Theodore Tso
2008-08-11 5:36 ` Eric Sandeen
2008-08-18 10:50 ` Andreas Dilger
2008-08-10 18:28 ` Theodore Tso
2008-08-11 7:55 ` Aneesh Kumar K.V
2008-08-11 14:39 ` Aneesh Kumar K.V
2008-08-11 18:15 ` Aneesh Kumar K.V
2008-08-13 2:32 ` Theodore Tso
2008-08-13 10:52 ` Aneesh Kumar K.V
2008-08-14 21:49 ` Mingming Cao
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=489F397A.1040709@redhat.com \
--to=sandeen@redhat.com \
--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).