All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taras Glek <tglek@mozilla.com>
To: linux-ext4@vger.kernel.org
Subject: Minimizing fragmentation in ext4, fallocate not enough?
Date: Fri, 24 Sep 2010 17:05:42 -0700	[thread overview]
Message-ID: <4C9D3CD6.9080000@mozilla.com> (raw)

Hi,
I noticed that several random IO-heavy Firefox files got fragmented 
easily. Our cache suffers most.
The cache works by creating a flat file and storing fixed-size entries 
in it. I though if I fallocate() the file first, then all of the writes 
within the allocated area would not cause additional fragmentation.

This doesn't seem to completely cure fragmentation with ext4 in 2.6.33. 
If I allocate a 4mb file, it gets more and more fragmented over time. 
fallocate() does reduce fragmentation, but not as much as I expected.

I assumed that writing to an fallocate()ed area will not cause 
additional fragmentation. Is my assumption incorrect?

Thanks,
Taras

ps. I'm using filefrag for measuring fragmentation.

ps2. Does running filefrag on a directory mean anything in ext4?

             reply	other threads:[~2010-09-25  0:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  0:05 Taras Glek [this message]
2010-09-25  1:07 ` Minimizing fragmentation in ext4, fallocate not enough? Andreas Dilger
2010-09-25 17:26   ` Eric Sandeen
2010-09-27 21:10     ` Taras Glek
2010-09-27 21:16       ` 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=4C9D3CD6.9080000@mozilla.com \
    --to=tglek@mozilla.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 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.