From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: data switchs su,sw and sunit,swidth
Date: Mon, 20 Jul 2009 13:22:21 +0200 [thread overview]
Message-ID: <200907201322.22102@zmi.at> (raw)
In-Reply-To: <4A626EC5.3090100@tlinx.org>
[-- Attachment #1.1: Type: text/plain, Size: 1631 bytes --]
On Sonntag 19 Juli 2009 Linda Walsh wrote:
> Then, for RAID 1 (mirror) would 'sw'==1? Would setting the su/sw
> value for a RAID 1 actually matter in any way? Ie, technically --
> it would fill in numbers for OS book-keeping, but wouldn't change
> anything in terms of performance or layout, vs. 'physically' -- where
> it could change disk layout or performance?
>
> At RAID 0, I'd guess sw==2?
Both RAID0 and RAID1 use sw=0.
> In RAID 5, would it be sw == #Disks-1? So even w/6 disks, it
> still only uses 1 disk for parity and sw == 5?
RAID5: sw = #Disks-1 ( so with 8 disks use 7)
RAID6: sw = #Disks-2 ( so with 8 disks use 6)
> I wonder what becomes a max-safe RAID 5 size? (or is the number of
> parity disks a settable option with RAID 5?)
RAID5 always only has 1 parity disk (well, technically it's not a
physical disk, but the parity is distributed over all disks in the
array).
Don't know what you mean by "max-safe" size. The more disks you have,
the bigger the chance that a single disk breaks. Also, I tested with
Areca controllers, using more than 7 disks in a single RAID array
doesn't improve speed anymore. So I use RAID-6 for up to 8 disks, and
make it RAID-60 for up to 16 disks (with Areca controllers).
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-07-20 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 0:54 data switchs su,sw and sunit,swidth Linda Walsh
2009-07-20 11:22 ` Michael Monnerie [this message]
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=200907201322.22102@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 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.