From: Stephan Kulow <coolo@suse.de>
To: Andreas Dilger <adilger@sun.com>, linux-ext4@vger.kernel.org
Subject: Re: file allocation problem
Date: Sat, 18 Jul 2009 23:16:39 +0200 [thread overview]
Message-ID: <200907182316.39516.coolo@suse.de> (raw)
In-Reply-To: <20090717211444.GF4231@webber.adilger.int>
On Friday 17 July 2009 23:14:44 Andreas Dilger wrote:
> > Yeah, but even the file in /tmp/nd got 3 extents. my file is 1142 blocks
> > and my mb_groups says 2**9 is the highest possible value. So I guess I
> > will indeed try to create the file system from scratch to test the
> > allocator for real.
>
> The defrag code needs to become smarter, so that it finds small files
> in the middle of freespace and migrates those to fit into a small gap.
> That will allow larger files to be defragged once there is large chunks
> of free space.
Is there a way that user space can hint the allocator to fill these gaps? I
don't see any obvious way. Relying on the allocator not to make matters worse
might be enough, but it doesn't sound ideal. Unless something urgent comes up
I might actually continue experiment next week :)
My resize2fs defrag worked pretty well actually, but then again I did it on an
offline copy and it won't work for online that way.
Greetings, Stephan
next prev parent reply other threads:[~2009-07-18 21:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 11:31 file allocation problem Stephan Kulow
2009-07-16 15:58 ` Theodore Tso
2009-07-16 17:43 ` Stephan Kulow
2009-07-17 1:12 ` Theodore Tso
2009-07-17 4:32 ` Andreas Dilger
2009-07-17 5:31 ` Stephan Kulow
2009-07-17 5:17 ` Stephan Kulow
2009-07-17 14:26 ` Theodore Tso
2009-07-17 18:02 ` Stephan Kulow
2009-07-17 21:14 ` Andreas Dilger
2009-07-18 21:16 ` Stephan Kulow [this message]
2009-07-19 22:45 ` Ron Johnson
2009-07-20 21:18 ` Andreas Dilger
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=200907182316.39516.coolo@suse.de \
--to=coolo@suse.de \
--cc=adilger@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 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.