From: Theodore Tso <tytso@mit.edu>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Yea old defrag
Date: Wed, 22 Oct 2008 14:03:42 -0400 [thread overview]
Message-ID: <20081022180342.GA26257@mit.edu> (raw)
In-Reply-To: <48FF506F.6060701@cfl.rr.com>
On Wed, Oct 22, 2008 at 12:10:23PM -0400, Phillip Susi wrote:
> I'm writing this to Theodore Ts'o because he has worked on the package
> in the past, and currently maintains e2fsprogs. I am CCing lkml since
> there are likely to be other interested parties, and there does not seem
> to be a separate list for e2fsprogs.
>
> The old defrag package for doing offline defragmentation of ext2 has not
> been maintained in many years. About two years ago I fixed a few bugs
> that were causing it to not work on ext3 and placed the changes in
> Ubuntu. I would like to see this program continue to live since it
> still serves a purpose, but because it has had no upstream maintainer in
> so long, Debian and thus Ubuntu have dropped the package. I am trying
> to resurrect it.
>
> I was wondering why it was never integrated into e2fsprogs, and if this
> could now be done. It seems to me that e2fsprogs would be the proper
> home for it, and a neutral upstream for everyone. If not, then I will
> try to maintain it as an Ubuntu native package in a bazaar branch on
> launchpad.
The problem with the defrag code has always been that I haven't had
time to give it proper love and attention, and it needs a *lot* of
work before I would be willing to stand behind it as a useful and
"safe" tool to use. Basically, I don't want to get the hate mail from
people who lose their data due to bugs or other potential failures
from e2defrag.
I have a vague memory it doesn't even work if the filesystem blocksize
is greater than 1k, but I'm not 100% certain that is still true.
There is also an on-line defragmetter that requires kernel support
that some folks from NEC are working on for ext4 (which can also
support ext3 filesystems). My thinking is that it's more worthwhile
to focus my attentions on helping Akira Fujita and Takashi Sato finish
theiron-line ext4 defragmentation patches than to worry about
e2defrag. Of course, if you'd like to give some love and attention to
e2defrag, that's great. But e2defrag doesn't use the ext2fs
libraries, and it would be a huge amount of work to make sure it
supports things like extended attributes and other newer format
enhancements that have been made to the ext3 filesystem.
Regards,
- Ted
next prev parent reply other threads:[~2008-10-22 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 16:10 Yea old defrag Phillip Susi
2008-10-22 18:03 ` Theodore Tso [this message]
2008-10-22 20:01 ` Phillip Susi
2008-10-22 20:40 ` Theodore Tso
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=20081022180342.GA26257@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
/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