From: Mike Frysinger <vapier@gentoo.org>
To: linux-ext4@vger.kernel.org
Subject: e4defrag seems too optimistic
Date: Thu, 29 Apr 2021 01:33:38 -0400 [thread overview]
Message-ID: <YIpFK3or2Creo1qg@vapier> (raw)
i started running e4defrag out of curiosity on some large files that i'm
archiving long term. its results seem exceedingly optimistic and i have
a hard time agreeing with it. am i pessimistic ?
for example, i have a ~4GB archive:
$ e4defrag -c ./foo.tar.xz
<File> now/best size/ext
./foo.tar.xz
39442/2 93 KB
Total/best extents 39442/2
Average size per extent 93 KB
Fragmentation score 34
[0-30 no problem: 31-55 a little bit fragmented: 56- needs defrag]
This file (./foo.tar.xz) does not need defragmentation.
Done.
i have a real hard time seeing this file as barely "a little bit fragmented".
shouldn't the fragmentation score be higher ?
as a measure of "how fragmented is it really", if i copy the file and then
delete the original, there's a noticeable delay before `rm` finishes.
-mike
next reply other threads:[~2021-04-29 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 5:33 Mike Frysinger [this message]
2021-04-29 20:47 ` e4defrag seems too optimistic Andreas Dilger
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=YIpFK3or2Creo1qg@vapier \
--to=vapier@gentoo.org \
--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