From: Thomas Bellman <bellman@nsc.liu.se>
To: Chris Mason <chris.mason@oracle.com>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs wishlist
Date: Wed, 02 Mar 2011 10:05:28 +0100 [thread overview]
Message-ID: <4D6E0858.6030603@nsc.liu.se> (raw)
In-Reply-To: <1299004651-sup-1713@think>
On 2011-03-01 19:39, Chris Mason wrote:
> We'll have raid56, but it won't be variable stripe size. There will be
> one stripe size for data and one for metadata but that's it.
Will the stripe *width* be configurable? If I have something like a
Sun Thor with 48 drives, I would probably not be entirely comfortable
having 46 drives data and 2 drives parity; too little redundancy for
my tastes. 2 drives parity per 10 drives data is more like what I
would run, but that would of course be an individual choice.
/Bellman
next prev parent reply other threads:[~2011-03-02 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 18:35 btrfs wishlist Roy Sigurd Karlsbakk
2011-03-01 18:39 ` Chris Mason
2011-03-01 19:09 ` Freddie Cash
2011-03-02 9:05 ` Thomas Bellman [this message]
2011-03-02 10:43 ` Hugo Mills
2011-03-02 14:18 ` Justin Ossevoort
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=4D6E0858.6030603@nsc.liu.se \
--to=bellman@nsc.liu.se \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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;
as well as URLs for NNTP newsgroup(s).