From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Stan Hoeppner <stan@hardwarefreak.com>,
John Bokma <contact@johnbokma.com>
Subject: Re: 30 TB RAID6 + XFS slow write performance
Date: Thu, 21 Jul 2011 08:19:54 +0200 [thread overview]
Message-ID: <201107210820.01019@zmi.at> (raw)
In-Reply-To: <20110720230126.GH9359@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 1866 bytes --]
On Donnerstag, 21. Juli 2011 Dave Chinner wrote:
> No, they'll get sunit aligned but default, which would be on 64k
> boundaries.
OK, so only when <quote Dave> "swalloc mount option set and the
allocation is for more than a swidth of space it will align to swidth
rather than sunit" </quote Dave>.
So even when I specify swalloc but a file is generated with only 4KB, it
will very probably be sunit aligned on disk.
> > That way, all stripes of a 1GB partition would be full when
> > there are roughly 1170 files (1170*896KiB ~ 1GB). What would happen
> > when I create other files - is XFS "full" then, or would it start
> > using sub- stripes? If sub-stripes, would they start at su
> > (=64KiB) distances, or at single block (e.g. 4KiB) distances?
>
> It starts packing files tightly into remaining free space when no
> free aligned extents are availble for allocation in the AG.
That means for above example, that 16384 x 2KiB files could be created,
and each be sunit aligned on disk. Then all sunit start blocks are full,
so additional files will be sub-sunit "packed", is it this?
That would mean fragmentation is likely to occur from that moment, if
there are files that grow. And files >64KiB are immediately fragmented
then. At this time, there are only 16384 * 2KiB = 32MiB used, which is
3,125% of the disk. I can't believe my numbers, are they true?
OK, this is a worst case scenario, and as you've said before, any
filesystem can be considered full at 85% fill grade. But it's incredible
how quickly you could fuck up a filesystem when using su/sw and writing
small files.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// Haus zu verkaufen: http://zmi.at/langegg/
[-- 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:[~2011-07-21 6:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 19:58 30 TB RAID6 + XFS slow write performance John Bokma
2011-07-19 0:00 ` Eric Sandeen
2011-07-19 8:37 ` Emmanuel Florac
2011-07-19 22:37 ` Stan Hoeppner
2011-07-20 0:20 ` Dave Chinner
2011-07-20 5:16 ` Stan Hoeppner
2011-07-20 6:44 ` Dave Chinner
2011-07-20 12:10 ` Stan Hoeppner
2011-07-20 14:04 ` Michael Monnerie
2011-07-20 23:01 ` Dave Chinner
2011-07-21 6:19 ` Michael Monnerie [this message]
2011-07-21 6:48 ` Dave Chinner
2011-07-22 6:10 ` Michael Monnerie
2011-07-22 18:05 ` Stan Hoeppner
2011-07-22 23:10 ` Dave Chinner
2011-07-24 6:14 ` Stan Hoeppner
2011-07-24 8:47 ` Michael Monnerie
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=201107210820.01019@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=contact@johnbokma.com \
--cc=stan@hardwarefreak.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.