linux-ext4 - Re: [PATCH 1/3] e4defrag: output blocks per extent by -c option

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87f94c370910020828p2a21d52cu1451a80d6fdb8a34@mail.gmail.com>
Date:	Fri, 2 Oct 2009 11:28:56 -0400
From:	Greg Freemyer <greg.freemyer@...il.com>
To:	Kazuya Mio <k-mio@...jp.nec.com>
Cc:	linux-ext4@...r.kernel.org, Theodore Tso <tytso@....edu>
Subject: Re: [PATCH 1/3] e4defrag: output blocks per extent by -c option

2009/10/1 Kazuya Mio <k-mio@...jp.nec.com>:
> 2009/10/01 3:28, Greg Freemyer wrote::
>> 2009/9/30 Kazuya Mio <k-mio@...jp.nec.com>:
>>> e4defrag with -c option outputs "ratio" that means the levels of
>>> fragmentation. However, it's difficult for users to understand, so we will
>>> use blocks per extent instead of ratio.
>>>
>>> Before:
>>> # e4defrag -c /mnt/mp1/file
>>> <File>                                         now/best          ratio
>>> /mnt/mp1/file                                   14/1             0.01%
>>>
>>>  Total/best extents                             14/1
>>>  Fragmentation ratio                            0.01%
>>>  Fragmentation score                            0.10
>>>  [0-30 no problem: 31-55 a little bit fragmented: 55- needs defrag]
>>>  This file(/mnt/mp1/file) does not need defragmentation.
>>>  Done.
>>>
>>> After:
>>> # e4defrag -c /mnt/mp1/file
>>> <File>                                         now/best        blk/ext
>>> /mnt/mp1/file                                   14/1              7142
>>>
>>>  Total/best extents                             14/1
>>>  Average blocks per extent                      7142
>>>  Fragmentation score                            0
>>>  [0-30 no problem: 31-55 a little bit fragmented: 55- needs defrag]
>>>  This file(/mnt/mp1/file) does not need defragmentation.
>>>  Done.
>>
>> RFC
>>
>> If we are going go that far (which I like), how about adding the avg
>> extent size in bytes.  (ie. 7142 * blocksize I assume).
>>
>> Also a note about the max blocks / extent might be good.
>>
>> ie. Add a more or less hard coded line
>> Ext4 max blocks per extent     32,768  (128MiB)
>
> Your ideas sound good. How about the following output image?
>
> # e4defrag -c /mnt/mp1/file
> <File>                                         now/best         KB/ext
> /mnt/mp1/file                                   14/1              4000
>
>  Total/best extents                             14/1
>  Min bytes per extent                           1024 KB
>  Max bytes per extent                           20489 KB
>  Average bytes per extent                       4000 KB
>  Fragmentation score                            0
>  [0-30 no problem: 31-55 a little bit fragmented: 55- needs defrag]
>  This file(/mnt/mp1/file) does not need defragmentation.
>  Done.
>
> Regards,
>
> Kazuya Mio

I was thinking more of the theoretical max bytes per extent, not the
largest extent found in the actual file.

I say this because most users of e4defrag won't know what perfection
is, so they won't know if and when they have come close if they don't
know what the ultimate goal is.

Specifically, think of a admin hosting a few virtual machines where
the virtual disks are ext4 files.  They could easily be 100's of GB so
they may think even 128MB / extent can be improved on, even though
they have already achieved the theoretical max.

Greg
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html