From: Eric Sandeen <sandeen@sandeen.net>
To: Reindl Harald <h.reindl@thelounge.net>, linux-ext4@vger.kernel.org
Subject: Re: e4defrag don't work really well
Date: Thu, 16 Feb 2023 13:56:51 -0600 [thread overview]
Message-ID: <abcc1ec6-a1d6-28a2-d0f5-29baac0722b8@sandeen.net> (raw)
In-Reply-To: <95b1df7e-3eb9-484c-d655-c42501ce7429@thelounge.net>
On 2/16/23 12:21 PM, Reindl Harald wrote:
>
>
> Am 16.02.23 um 17:50 schrieb Eric Sandeen:
>> On 2/12/23 12:14 PM, Reindl Harald wrote:
>>>
>>> what's wrong with e4defrag that it pretends it reduced th efragments of a file to 1 while in the next "e4defrag -c" (why does that only list 5 files at all) the same file is listed again with the same old frag count?
>>
>> You might want to examine the actual allocation before and after with "filefrag -v"
>> which could offer some clues to whether anything was modified by e4defrag.
>>
>> (I would also suggest that there is no need to defragment a 3-extent 2 megabyte
>> file, in general.)
>
> it's not a question if it's needed
>
> the point is it pretends "Success: [1/1]" but a following "e4defrag -c" still says "now/best 3/1"
I understand. It seems that your irritation at my parenthetical caused you
to skip over the request for more information from filefrag, though.
-Eric
next prev parent reply other threads:[~2023-02-16 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 18:14 e4defrag don't work really well Reindl Harald
2023-02-16 16:50 ` Eric Sandeen
2023-02-16 18:21 ` Reindl Harald
2023-02-16 19:56 ` Eric Sandeen [this message]
2023-02-16 20:35 ` Reindl Harald
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=abcc1ec6-a1d6-28a2-d0f5-29baac0722b8@sandeen.net \
--to=sandeen@sandeen.net \
--cc=h.reindl@thelounge.net \
--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