From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@sun.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2freefrag utility
Date: Wed, 22 Jul 2009 23:59:43 -0500 [thread overview]
Message-ID: <4A67EE3F.4090909@redhat.com> (raw)
In-Reply-To: <20090722074352.GA21869@mit.edu>
Theodore Tso wrote:
...
> Here's the output on my root filesystem (which has been in use since
> February):
>
> Device: /dev/ssd/root
> Blocksize: 4096 bytes
> Total blocks: 18350080
> Free blocks: 10774142 (58.7%)
>
> Chunksize: 1048576 bytes (256 blocks)
> Total chunks: 71681
> Free chunks: 21792 (30.4%)
>
> Min free chunk: 4 KB
> Max free chunk: 568232 KB
> Avg free chunk: 184 KB
>
> HISTOGRAM OF FREE CHUNK SIZES:
> Chunk Size Range : Free chunks
> 4K... 8K- : 35005
> 8K... 16K- : 33639
> 16K... 32K- : 31419
> 32K... 64K- : 33953
> 64K... 128K- : 26397
> 128K... 256K- : 7314
> 256K... 512K- : 1855
> 512K... 1024K- : 1612
> 1M... 2M- : 1160
> 2M... 4M- : 567
> 4M... 8M- : 303
> 8M... 16M- : 106
> 16M... 32M- : 40
> 32M... 64M- : 51
> 64M... 128M- : 123
> 128M... 256M- : 8
> 512M... 1024M- : 1
>
> Yeah.... pretty fragmented. :-(
>
Just for comparison, here's a 30G xfs root that has run for a year or
two, currently about 70% full:
xfs_db> freesp -s
from to extents blocks pct
1 1 1849 1849 0.08
2 3 1383 3293 0.14
4 7 1034 5429 0.23
8 15 1061 12260 0.53
16 31 641 13261 0.57
32 63 355 15601 0.67
64 127 221 19940 0.86
128 255 195 35841 1.54
256 511 173 63066 2.71
512 1023 122 89824 3.86
1024 2047 51 70032 3.01
2048 4095 22 60982 2.62
4096 8191 20 116580 5.01
8192 16383 10 109896 4.72
16384 32767 7 152026 6.53
32768 65535 4 206283 8.87
65536 131071 3 285744 12.28
262144 524287 1 509811 21.91
524288 1048575 1 554838 23.85
total free extents 7153
total free blocks 2326556
average free extent size 325.256
from...to units are in 4k blocks.
Maybe the fancy ext4 defragger will have a good second use case in
cleaning up some of that freespace fragmentation.
-Eric
next prev parent reply other threads:[~2009-07-23 4:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 0:17 [PATCH] e2freefrag utility Andreas Dilger
2009-07-22 7:43 ` Theodore Tso
2009-07-23 4:59 ` Eric Sandeen [this message]
2009-07-23 13:45 ` How to fix up mballoc Theodore Tso
2009-07-23 17:43 ` Eric Sandeen
2009-07-24 0:23 ` Theodore Tso
2009-07-24 2:18 ` Eric Sandeen
2009-07-24 2:25 ` Eric Sandeen
2009-07-24 2:30 ` Andreas Dilger
2009-07-23 17:51 ` Mingming Cao
2009-07-24 0:43 ` Theodore Tso
2009-07-23 17:07 ` [PATCH] e2freefrag utility Andreas Dilger
2009-07-23 17:18 ` Eric Sandeen
2009-07-24 22:32 ` Theodore Tso
2009-07-24 23:14 ` Andreas Dilger
2009-07-25 0:18 ` Theodore Tso
2009-07-27 18:36 ` Andreas Dilger
2009-08-10 3:31 ` [PATCH 0/6] Patches to improve/fix e2freefrag Theodore Ts'o
2009-08-10 3:31 ` [PATCH 1/6] e2freefrag: Clarify e2freefrag's messages Theodore Ts'o
2009-08-10 3:31 ` [PATCH 2/6] e2freefrag: Do not print chunk-related information by default Theodore Ts'o
2009-08-10 3:31 ` [PATCH 3/6] e2freefrag: Fix to work correctly for file systems with 1kb block sizes Theodore Ts'o
2009-08-10 3:31 ` [PATCH 4/6] e2freefrag: Take into account the last free extent in the file system Theodore Ts'o
2009-08-10 3:31 ` [PATCH 5/6] Add V=1 support when linking e2freefrag in misc/Makefile.in Theodore Ts'o
2009-08-10 3:31 ` [PATCH 6/6] libext2fs: Treat uninitialized parts of bitmaps as unallocated Theodore Ts'o
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=4A67EE3F.4090909@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).