linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: delalloc fragmenting files?
Date: Fri, 26 Oct 2007 16:24:46 -0500	[thread overview]
Message-ID: <47225B1E.2060708@redhat.com> (raw)

I was doing a little seekwatchering today, and found something...
interesting.

I was doing an 8G buffered write via dd, on a machine that reports 3G of
memory, in 1M chunks like so:

dd if=/dev/zero of=/mnt/test/foobar bs=1024k count=8192

on a fairly decent hardware raid, ~90G filesystem.

Kernel is 2.6.24-rc1, with all the git patches from a day or so ago applied.

I made the ext4 fs with lustre's e2fsprogs, with -I 256, and mounted with:

mount -t ext4dev -o data=writeback,delalloc,extents,mballoc /dev/sdb7
/mnt/test

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

http://people.redhat.com/esandeen/seekwatcher/ext4-dd-write.png

if I don't mount with delalloc:

mount -t ext4dev -o data=writeback,extents,mballoc /dev/sdb7 /mnt/test

and run the same dd, I get 229 extents:

[root@bear-05 ~]# filefrag -v /mnt/test/foobar  | grep -i extents
File is stored in extents format
/mnt/test/foobar: 229 extents found

http://people.redhat.com/esandeen/seekwatcher/ext4-dd-write-nodelalloc.png

It looks like delalloc is dribbling all over the disk....

(note: times & rates look wrong to me, something is up with blktrace I
think, but FIBMAP shouldn't lie about allocation)

-Eric

             reply	other threads:[~2007-10-26 21:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 21:24 Eric Sandeen [this message]
2007-10-26 22:19 ` delalloc fragmenting files? 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
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=47225B1E.2060708@redhat.com \
    --to=sandeen@redhat.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).