Nathanael Nerode <[EMAIL PROTECTED]> writes:
> Package: defrag
> Version: 0.73pjm1-7
> Severity: important
>
> So, e2defrag thinks I have an ext3 filesystem when it's ext2.
>
> doctormoo:/home/neroden# e2defrag /dev/hda7
>
> e2defrag (/dev/hda7): ext3 filesystems not (yet) supported
> doctormoo:/home/neroden# dumpe2fs /dev/hda7
> Filesystem volume name: <none>
> Last mounted on: <not available>
> Filesystem UUID: effbe1b8-36fc-4c3d-b8d0-710ff1fb95d6
> Filesystem magic number: 0xEF53
> Filesystem revision #: 1 (dynamic)
> Filesystem features: dir_index filetype sparse_super
> Default mount options: (none)
> Filesystem state: clean
> ....
>
> This renders it kind of unusable.
>
> What's going on here?
I haven't checked the code but my guess is the dir_index flag causes
this. If I'm right the error message should be rephrased but the
failure is valid.
e2defrag needs some major source changes (variable type but not code)
to compile on !i386 archs that I have pending for after sarge and I'm
realy busy with work and amd64 currently. I hope you can wait a while
for this.
MfG
Goswin
PS: can you reproduce this with a freshly amde fs?
mke2fs [--some-options] /dev/ram0; e2defrag /dev/ram0?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
