From: Andreas Dilger <adilger@clusterfs.com>
To: Eric <erpo41@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Online defragmentation and ext4migrate
Date: Fri, 18 May 2007 15:05:06 -0600 [thread overview]
Message-ID: <20070518210506.GE5286@schatzie.adilger.int> (raw)
In-Reply-To: <1179519594.6109.40.camel@eric-laptop>
On May 18, 2007 13:19 -0700, Eric wrote:
> A defragmentation routine makes files contiguous on disk. A better
> defragmentation routine intelligently locates data structures on the
> disk so that files and directories are placed to minimize latency and
> maximize throughput now, AND so that this will continue to happen in the
> future. Typically this means not only making files contiguous, but also
> consolidating free space at the end of the volume so that the block
It is not necessarily best to put free space at the END of the volume
(that is very FAT-centric) but it does make sense to consolidate free
space within each block group.
> But on an extent file there is a logical, high-performance mapping
> between the on-disk structures that keep track of which blocks belong to
> which files and the data returned by the as-yet-to-be-implemented FIEMAP
> ioctl, which could make defragging faster and more fun.
>
> http://www.mail-archive.com/linux-ext4@vger.kernel.org/msg01434.html
Yeah, I wish I had time to finish working on this.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-05-18 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 13:06 Online defragmentation and ext4migrate Aneesh Kumar K.V
2007-05-18 20:19 ` Eric
2007-05-18 21:05 ` Andreas Dilger [this message]
2007-05-21 8:33 ` Aneesh Kumar
2007-05-21 10:42 ` Jan Kara
2007-05-21 10:25 ` Takashi Sato
2007-05-21 10:37 ` Aneesh Kumar K.V
2007-05-22 8:35 ` Takashi Sato
2007-05-21 10:38 ` Jan Kara
2007-05-21 13:36 ` Eric
2007-05-22 11:28 ` Jan Kara
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=20070518210506.GE5286@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=erpo41@gmail.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