From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Alex Tomas <alex.tomas@sun.com>
Subject: Re: delalloc fragmenting files?
Date: Fri, 26 Oct 2007 21:54:55 -0500 [thread overview]
Message-ID: <4722A87F.3070709@redhat.com> (raw)
In-Reply-To: <20071026221938.GV3042@webber.adilger.int>
Andreas Dilger wrote:
> On Oct 26, 2007 16:24 -0500, Eric Sandeen wrote:
>> The resulting file had over 4k extents.
>> [root@bear-05 ~]# filefrag -v /mnt/test/foobar | grep -i extents
>> File is stored in extents format
>> /mnt/test/foobar: 4075 extents found
>
> On a related note - we're just putting the finishing touches on the
> FIEMAP patches for ext4 + e2fsprogs, so that we can get decent looking
> output from filefrag, and much more efficiently than FIBMAP.
sounds good.
> One of the issues is that w/o delalloc the mballoc code only gets
> single-block allocations, so there might be a problem with the interface
> to mballoc. That might be caused by the fact the patches were changed
> at one point from delalloc-atop-mballoc to mballoc-atop-delalloc, and
> something was missed in that conversion.
>
> Have you tried O_DIRECT? That is another way to access mballoc w/o
> using delalloc.
I've tried osync:
http://people.redhat.com/esandeen/seekwatcher/ext4-dd-osync-write.png
but not yet O_DIRECT, will do.
-Eric
next prev parent reply other threads:[~2007-10-27 2:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 21:24 delalloc fragmenting files? Eric Sandeen
2007-10-26 22:19 ` Andreas Dilger
2007-10-27 2:54 ` Eric Sandeen [this message]
2007-10-27 3:08 ` Eric Sandeen
2007-10-31 21:01 ` Eric Sandeen
2007-11-01 0:35 ` Alex Tomas
2007-11-01 15:20 ` Eric Sandeen
2007-11-01 19:05 ` Eric Sandeen
2007-11-02 8:56 ` Alex Tomas
2007-11-02 15:41 ` Eric Sandeen
2007-11-04 18:36 ` Alex Tomas
2007-11-05 17:37 ` Eric Sandeen
2007-11-05 17:39 ` Eric Sandeen
2007-11-05 17:45 ` Alex Tomas
2007-11-05 18:51 ` Andreas Dilger
2007-11-05 18:54 ` Eric Sandeen
2007-11-06 19:54 ` Eric Sandeen
2007-11-07 20:37 ` Andreas Dilger
2007-11-07 20:53 ` Eric Sandeen
2007-10-29 19:13 ` Eric Sandeen
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=4722A87F.3070709@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=alex.tomas@sun.com \
--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).