From: tytso@mit.edu
To: Jari Sundell <sundell.software@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: Extents in spare files on ext4 not being merged
Date: Sun, 14 Feb 2010 13:03:39 -0500 [thread overview]
Message-ID: <20100214180339.GH5337@thunk.org> (raw)
In-Reply-To: <b3f268591002140550x746b96aeo3c7a017ac4ecf993@mail.gmail.com>
On Sun, Feb 14, 2010 at 10:50:45PM +0900, Jari Sundell wrote:
> http://libtorrent.rakshasa.no/ticket/460#comment:49
>
> Some users of rtorrent reported very high number of extents for files
> despite the use of posix_fallocate/fallocate on ext4. (3000+ for 250MB
> file, ) A test program showed that the file was contiguous on disk
> despite the high number of extents reported by filefrag. (Not sure
> what kernel versions they used)
Yeah, it's a known problem. The main problem is that we are only
checking to see merge both to the left and the right of the extent
tree when converting an extent from uninitialzied to initialized.
I've cc'ed the linux-ext4 list in the hopes someone is motivated to
fix this long-standing shortcoming. Unless someone starts working
quickly, it's not likely it will make this upcoming merge window, but
we can hope....
- Ted
parent reply other threads:[~2010-02-14 18:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <b3f268591002140550x746b96aeo3c7a017ac4ecf993@mail.gmail.com>]
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=20100214180339.GH5337@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sundell.software@gmail.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 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).