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: Wed, 20 Jul 2011 16:04:31 +0200 [thread overview]
Message-ID: <201107201604.33419@zmi.at> (raw)
In-Reply-To: <4E26C5C5.1090802@hardwarefreak.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 1023 bytes --]
On Mittwoch, 20. Juli 2011 Stan Hoeppner wrote:
> I thought this was packing multiple small files into
> a single stripe write, which you just explained XFS does not do.
This is interesting, I jump in here. Does that mean that if I have a XFS
volume with sw=14,su=64k (14*64=896KiB) that when I write 10 small files
in the same dir with 2KB each, each file would be placed at a 896KiB
boundary? 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?
I hope I could explain my thoughts in an understandable way ;-)
--
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-20 14:04 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 [this message]
2011-07-20 23:01 ` Dave Chinner
2011-07-21 6:19 ` Michael Monnerie
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=201107201604.33419@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.