public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: e2defrag 0.81 released
Date: Mon, 09 Jul 2012 14:49:51 -0400	[thread overview]
Message-ID: <4FFB27CF.4090901@ubuntu.com> (raw)
In-Reply-To: <CAGpXXZ+B67C9+oxH35sW4Pjg61VC-GdJEjUqwDw57AnLHdUkAw@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 7/9/2012 12:16 PM, Greg Freemyer wrote:
> Of course, even that is better than having to unmount the
> filesystem like you new tool apparently requires.

Old tool... very old tool ;)

I remember using the thing with one of the first releases of slackware
when I first started playing with Linux, and iirc, DOS hadn't yet
included its own defragger.

> I think you're right e4defrag userspace code ignores consolidating 
> freespace to make bigger extents possible and I don't think
> userspace has any file packing specific knowledge.
> 
> Does fallocate itself assist with either?
> 
> ie. since e4defrag uses fallocate to allocate the donor file
> blocks, logically it would make sense to add the intelligence you
> are looking for into fallocate.  And hopefully it is already
> there.

You need a method of requesting specific blocks instead of just asking
for the right number.  Then you need to analyze all of the files on
the disk to figure out where their blocks are, and decide where you
want them to be instead.  Then you could use the donor inode method to
move things around.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP+yfPAAoJEJrBOlT6nu75Y8AH/09qDUt0jdhPjNyXMUUFRVaV
U7Ih5j6r0srRHH9VmS7ppq6ingqpbrFEExbalg8ynTRX1nYDGL0nLiBU79rfK+KK
XOTK0ZYm+CUMElLdO5bYnaHti9vsSHL5xRyGmI5OR0CY7LwfnyJeDw6wS7+WsgyQ
o6ziTPcBEfaJzn9BBS+EP/1WI06lQ/cJbWUqUAJhefu2my3IXJUrjUYjnH46HKGM
2ptPbIJM2fT4QubBNnuPpdTNI5yc56+auzoB3hrK2Nf/Yh17w5R0MomHk/VitzPt
AD7zKLgpk6R9G/IbnajsMVzbLsjBbn8Tcyrhher2uyw3xE0XtJgj2fmPq32ZrL0=
=hMeu
-----END PGP SIGNATURE-----

      reply	other threads:[~2012-07-09 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 23:01 e2defrag 0.81 released Phillip Susi
2012-07-07  6:02 ` Andreas Dilger
2012-07-07 14:53   ` Phillip Susi
2012-07-09 16:16     ` Greg Freemyer
2012-07-09 18:49       ` Phillip Susi [this message]

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=4FFB27CF.4090901@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=adilger@dilger.ca \
    --cc=greg.freemyer@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