From: Eric Sandeen <sandeen@sandeen.net>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: XFS for lots of small files
Date: Sat, 24 May 2008 22:25:14 -0500 [thread overview]
Message-ID: <4838DC1A.5010206@sandeen.net> (raw)
In-Reply-To: <200805062055.36755.Martin@lichtvoll.de>
Martin Steigerwald wrote:
> And there is quite some fragmentation on it:
>
> xfs_db> frag
> actual 653519, ideal 587066, fragmentation factor 10.17%
No, there's not.
You have 653519 extents out of an "ideal" 587066.
That is 653519/587066 = 1.113 extents per file.
It is not "quite some" fragmentation, it is near perfect (although this
is subjective, and also depends on the size of your files... if they are
all 8k then 1.113 extents per file might be a bit high; if they average
1G then 1.113 extents on average is pretty darned good.)
-Eric
next prev parent reply other threads:[~2008-05-25 3:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 16:11 XFS for lots of small files Leszek Dubiel
2008-05-06 16:23 ` Nicolas KOWALSKI
2008-05-06 18:55 ` Martin Steigerwald
2008-05-23 0:44 ` Linda Walsh
2008-05-24 16:16 ` Martin Steigerwald
2008-05-25 3:25 ` Eric Sandeen [this message]
2008-05-25 11:38 ` Martin Steigerwald
2008-05-25 15:39 ` Eric Sandeen
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=4838DC1A.5010206@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Martin@lichtvoll.de \
--cc=linux-xfs@oss.sgi.com \
/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