public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric <erpo41@gmail.com>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Online defragmentation and ext4migrate
Date: Mon, 21 May 2007 06:36:51 -0700	[thread overview]
Message-ID: <1179754611.389.10.camel@eric-laptop> (raw)
In-Reply-To: <20070521103828.GB29416@atrey.karlin.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]

On Mon, 2007-05-21 at 12:38 +0200, Jan Kara wrote:
>   Yes. On the other hand I believe that some people would like to use
> defragmentation but stay with ext3. For them conversion to extents is
> no-go.
> [...]
>  I've written a patch that defragments non-extent files but after
> discussion with XFS guys I've decided that the interfaces should be made
> more generic, so that XFS and other filesystems can use them too...

I see no reason why the ioctl to convert a file to extents and then
defragment it should be different from the ioctl to defragment a
non-extent file.

After all, whether a file's blocks are tracked as lists of blocks or a
set of extents is just bookkeeping, right? The set of data blocks that
make up the file and their order is the same regardless of whether the
extent flag is set in the inode.

If the user is running the ext2/3 driver or the ext4 driver with the
noextents option, just defragment the file. If the user is running ext4
without the noextents option, convert to extents and then defragment.

The only problem that I can think of is that defragmenting metadata
(including indirect block and/or whatever the equivalent is in
extent-land) presumably has performance benefits too, so maybe a
defragmenter in userspace would want to have some knowledge/control over
this process.

Cheers,

Eric


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-21 13:36 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
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 [this message]
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=1179754611.389.10.camel@eric-laptop \
    --to=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