From: Alex Tomas <bzzz.tomas@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andreas Dilger <adilger@Sun.COM>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: delalloc fragmenting files?
Date: Fri, 02 Nov 2007 11:56:36 +0300 [thread overview]
Message-ID: <472AE644.1040102@gmail.com> (raw)
In-Reply-To: <472A2384.2010001@redhat.com>
Eric,
would you mind to repeat the run and then grab /proc/fs/ext4/<dev>/mb_history?
thanks in advance, Alex
Eric Sandeen wrote:
> Eric Sandeen wrote:
>> Alex Tomas wrote:
>>> please, try the patch attached.
>> Looks quite a bit better:
>>
>> http://people.redhat.com/esandeen/seekwatcher/ext4-alex.png
>> http://people.redhat.com/esandeen/seekwatcher/ext4-alex-ext4-dd-write.png
>> http://people.redhat.com/esandeen/seekwatcher/ext4-alex-ext4-xfs-dd-write.png
>>
>> It is much less fragmented, although still not exactly the nice linear
>> allocation I'd expect from a single threaded large write on a fresh fs...
>
> Note, we're still getting out-of-order extents, too:
>
> First block: 122880
> Last block: 2694143
> Discontinuity: Block 7424 is at 101376 (was 130303)
> Discontinuity: Block 28160 is at 133120 (was 122111)
> Discontinuity: Block 58368 is at 188416 (was 163327)
> Discontinuity: Block 66304 is at 180224 (was 196351)
> Discontinuity: Block 73984 is at 172032 (was 187903)
> Discontinuity: Block 81664 is at 167936 (was 179711)
> Discontinuity: Block 84736 is at 221184 (was 171007)
> Discontinuity: Block 92416 is at 212992 (was 228863)
> Discontinuity: Block 100096 is at 204800 (was 220671)
> Discontinuity: Block 107776 is at 198656 (was 212479)
> ...
>
> I'm trying to find time to look into this but other things are knocking
> at my door so no promises...
>
> -Eric
>
next prev parent reply other threads:[~2007-11-02 8:57 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
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 [this message]
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=472AE644.1040102@gmail.com \
--to=bzzz.tomas@gmail.com \
--cc=adilger@Sun.COM \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.