Your message dated Sun, 13 Apr 2008 23:02:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line defrag has been removed from Debian, closing #396449
has caused the Debian Bug report #396449,
regarding e2defrag - Unable to allocate buffer for inode priorities
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
396449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396449
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: defrag
Version: 0.73pjm1-8
Severity: grave
On Wed, Nov 01, 2006 at 01:10:50AM +0800, Andreas Dilger wrote:
> > So now it was time to defrag, I used this command:
> > thor:~# e2defrag -r /dev/vgraid/data
>
> This program is dangerous to use and any attempts to use it should be
> stopped. It hasn't been updated in such a long time that it doesn't
> even KNOW that it is dangerous (i.e. it doesn't check the filesystem
> version number or feature flags).
In fact we need to create a Debian bug report indicating that this
package should *NOT* be included when the Debian etch distribution
releases.
Goswin, I am setting the severity to grave (a release-critical
severity) because defrag right now is almost guaranteed to corrupt the
filesystem if used with modern ext3 filesystems leading to data loss,
and this satisfies the definition of grave. I believe the correct
answer is either to (a) make defrag refuse to run if any filesystem
features are enabled (at the very least, resize_inode, but some of the
other newer ext3 filesystem features make me nervous with respect to
e2defrag, or (b) since (a) would make e2defrag mostly useless
especially since filesystems with resize inodes are created by default
in etch, and as far as I know upstream abandoned defrag a long time
ago, that we should simply remove e2defrag from etch and probably from
Debian altogether.
If you are interested in doing a huge amount of auditing and testing
of e2defrag with modern ext3 (and soon ext4) filesystems, that's
great, but I suspect that will not at all be trivial, and even making
sure e2defrag won't scramble users' data probably can't be achievable
before etch releases.
Regards,
- Ted
--- End Message ---
--- Begin Message ---
Version: 0.73pjm1-8+rm
The defrag package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/446691 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Lucas
--- End Message ---
