From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: 128TB filesystem limit?
Date: Fri, 26 Mar 2010 01:09:08 -0500 [thread overview]
Message-ID: <4BAC4F84.9010005@hardwarefreak.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1003252152350.16138@asgard.lang.hm>
david@lang.hm put forth on 3/25/2010 11:56 PM:
>>> the next fun thing is figuring out what sort of stride, etc parameters I
>>> should have used for this filesystem.
>>
>> mkfs.xfs should suss that out for you automatically based on talking
>> to md;
>> of course you'd want to configure md to line up well with the hardware
>> alignment.
>
> in this case md thinks it's working with 10 12.8TB drives, I really
> doubt that it's going to do the right thing.
>
> I'm not exactly sure what the right thing is in this case. the hardware
> raid is useing 64K chunks across 16 drives (so 14 * 64K worth of data
> per stripe), but there are 10 of these stripes before you get back to
> hitting the same drive again.
It would be helpful if you told us the primary application(s) that will be
writing to this large multi-level RAID setup. Primarily large files or
small? Database? ??
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-03-26 6:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 23:15 128TB filesystem limit? david
2010-03-25 23:54 ` Dave Chinner
2010-03-26 0:03 ` david
2010-03-26 0:35 ` Dave Chinner
2010-03-26 2:02 ` david
2010-03-26 4:35 ` Eric Sandeen
2010-03-26 4:56 ` david
2010-03-26 6:09 ` Stan Hoeppner [this message]
2010-03-26 7:26 ` Steve Costaras
2010-03-27 9:06 ` Emmanuel Florac
2010-03-27 14:28 ` Steve Costaras
2010-03-27 18:45 ` david
2010-03-28 21:17 ` Peter Grandi
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=4BAC4F84.9010005@hardwarefreak.com \
--to=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.