From: Andrea Mazzoleni <amadvance@gmail.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: Andrea Mazzoleni <amadvance@gmail.com>,
Neil Brown <neilb@suse.de>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: [RFC v2 0/2] New RAID library supporting up to six parities
Date: Tue, 7 Jan 2014 12:15:48 +0100 [thread overview]
Message-ID: <20140107111548.GD16044@gmail.com> (raw)
In-Reply-To: <CAK2H+efOLtq6onYASnZ5DsghVMp5AN70fx_uN8Ha5Wr3RxKx3A@mail.gmail.com>
Hi Mark,
On 01/06, Mark Knecht wrote:
> Question: As an end-user type who currently uses mdadm RAID6, if I
> wanted to set up a dedicated machine to do some SnapRAID testing then
> what's the minimum disk hardware I'd need assuming Linux is just on
> it's own disk?
The patch I sent is not related to SnapRAID. It's the same raid engine,
but this is not going to change how mdadm RAID is working.
When and if this patch will be accepted in the Linux kernel, you can
expect to have mdadm to support triple/quad/and more parity just like RAID5
and RAID6 are supported today.
But at now there is no new functionality to try. We still miss the
required changes inside mdadm, that likely will happen in a second
time.
Ciao,
Andrea
next prev parent reply other threads:[~2014-01-07 11:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 9:31 [RFC v2 0/2] New RAID library supporting up to six parities Andrea Mazzoleni
2014-01-06 9:31 ` [RFC v2 1/2] lib: raid: " Andrea Mazzoleni
2014-01-06 9:31 ` [RFC v2 2/2] fs: btrfs: Extends btrfs/raid56 to support " Andrea Mazzoleni
2014-01-06 14:12 ` Chris Mason
2014-01-07 10:35 ` Andrea Mazzoleni
2014-01-06 11:59 ` [RFC v2 0/2] New RAID library supporting " joystick
2014-01-06 13:11 ` Alex Elsayed
2014-01-06 15:49 ` joystick
2014-01-06 16:08 ` Alex Elsayed
2014-01-06 16:08 ` Alex Elsayed
2014-01-07 11:06 ` Andrea Mazzoleni
2014-01-06 17:02 ` Phil Turmel
2014-01-06 17:27 ` David Sterba
2014-01-06 18:13 ` Mark Knecht
2014-01-07 11:15 ` Andrea Mazzoleni [this message]
2014-01-14 9:25 ` David Brown
2014-01-14 14:41 ` Mark Knecht
2014-01-07 11:19 ` Andrea Mazzoleni
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=20140107111548.GD16044@gmail.com \
--to=amadvance@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=neilb@suse.de \
/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).