From: pg@xf2.for.sabi.co.UK (Peter Grandi)
To: Linux fs XFS <xfs@OSS.SGI.com>
Subject: Re: swidth in RAID
Date: Sun, 30 Jun 2013 20:08:35 +0100 [thread overview]
Message-ID: <20944.33331.145353.851055@tree.ty.sabi.co.uk> (raw)
In-Reply-To: <557F888F-34EA-4669-B861-C0B684DAD13D@gmail.com>
> I understand swidth should = #data disks. And the docs say
> for RAID 6 of 8 disks, that means 6. [ ... ] 8 disks/spindles
> working for you and a bit of parity on each. So shouldn't
> swidth equal disks in raid when its concerning distributed
> parity raid?
The main goal is trying to the reduce the probability of
read-modify-write.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-30 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 18:43 swidth in RAID aurfalien
2013-06-30 19:08 ` Peter Grandi [this message]
2013-06-30 21:42 ` Stan Hoeppner
2013-06-30 22:36 ` aurfalien
2013-07-01 1:38 ` Dave Chinner
2013-07-01 1:54 ` aurfalien
2013-07-01 2:09 ` Dave Chinner
2013-07-01 2:47 ` Stan Hoeppner
2013-07-01 2:54 ` aurfalien
2013-07-02 21:48 ` Peter Grandi
2013-07-03 0:15 ` Stan Hoeppner
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=20944.33331.145353.851055@tree.ty.sabi.co.uk \
--to=pg@xf2.for.sabi.co.uk \
--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