public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Alex Buell <alex.buell@munted.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Online ext4 defragmention
Date: Sun, 11 Jan 2009 15:28:38 -0500	[thread overview]
Message-ID: <20090111202838.GA29383@mit.edu> (raw)
In-Reply-To: <20090111134443.581cfc83@lithium.local.net>

On Sun, Jan 11, 2009 at 01:44:43PM +0000, Alex Buell wrote:
> Can someone confirm if the online ext4 defragmentation ioctls will
> be going into 2.6.29? Thanks, I'm planning a migration from a
> disparate collection of filesystems to ext4 over the next few months. 

Unfortunately, the defragmentation patches need to a lot of work (to
be honest, largely refactored and almost rewritten) before they are
ready to for mainline yes.  I am also concerned that the current
defrag patches also try too hard to keep blocks in the same block
group, even as a higher priority keeping them non-fragmented.

Also, note that some of the benefits of ext4 only show up if you do a
backup, mkfs, and restore; that's because there are layout changes
that can only take place if you reformat the filesystem.  Finally,
there are some allocation algorithm changes which didn't make the
2.6.29 merge window which I think will make a long-term difference.
So you'll probably want to use 2.6.29 with the ext4 patch set.

So if you want the best performance and fastest fsck times (which I
infer given your query about the defragmentation ioctls), you may want
to consider doing a reformat and restore operation as part of your
ext4 migration, at least for filesystem that you plan to use for
active use.  If the filesystem is just going to be an mp3 archive, for
example, it might not be worth it to do the backup/reformat/restore
path.

Regards,

						- Ted

  reply	other threads:[~2009-01-11 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 13:44 Online ext4 defragmention Alex Buell
2009-01-11 20:28 ` Theodore Tso [this message]
2009-01-12 13:39   ` Mike Snitzer
2009-01-12 14:15     ` Theodore Tso
2009-01-12 14:44       ` Mike Snitzer

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=20090111202838.GA29383@mit.edu \
    --to=tytso@mit.edu \
    --cc=alex.buell@munted.org.uk \
    --cc=linux-kernel@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