From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: LWN.net article: creating 1 billion files -> XFS looses
Date: Tue, 7 Sep 2010 08:20:07 +0200 [thread overview]
Message-ID: <201009070820.08354@zmi.at> (raw)
In-Reply-To: <20100907033134.GF7362@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 1251 bytes --]
On Dienstag, 7. September 2010 Dave Chinner wrote:
> # mkfs.xfs -n size=64k
> (-n = naming = directories. -d = data != directories)
Thank you, Dave. Do I interpret that parameter right:
When a new directory is created, per default it would occupy only 4KB,
with -n size=64k would be reserved. As the directory fills, space within
that block will be used, so in the default case after 4KB (how many
inodes would that be roughly? 256 Bytes/Inode, so 16 entries?) XFS would
reserve the next block, but in your case 256 entries would fit.
That would keep dir fragmentation lower, and with todays disks, take a
minimal more space, so it sounds very good to use that option.
Especially with RAIDs, where stripes usually are 64KB or bigger. Or
would the waste of space be so big that it could hurt?
Last question: Is there a way to set that option on a given XFS?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-07 6:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 11:12 LWN.net article: creating 1 billion files -> XFS looses Michael Monnerie
2010-08-19 12:05 ` Christoph Hellwig
2010-08-19 12:45 ` Michael Monnerie
2010-08-19 13:55 ` Stan Hoeppner
2010-08-20 7:55 ` Dave Chinner
2010-08-19 13:10 ` Emmanuel Florac
2010-09-06 13:42 ` Emmanuel Florac
2010-09-06 22:04 ` Dave Chinner
2010-09-06 22:58 ` Michael Monnerie
2010-09-07 3:31 ` Dave Chinner
2010-09-07 6:20 ` Michael Monnerie [this message]
2010-09-07 7:01 ` Dave Chinner
2010-09-08 5:42 ` Michael Monnerie
2010-09-07 6:46 ` Emmanuel Florac
2010-09-16 10:13 ` LWN.net article: creating 1 billion files -> Tests we did Emmanuel Florac
2010-09-16 21:53 ` Stan Hoeppner
2010-09-17 7:54 ` Michael Monnerie
2010-09-17 19:29 ` Peter Grandi
2010-09-18 11:25 ` Emmanuel Florac
2010-09-18 11:16 ` Emmanuel Florac
2010-09-17 19:57 ` Peter Grandi
2010-09-18 11:39 ` Emmanuel Florac
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=201009070820.08354@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=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