archive mirror
 help / color / mirror / Atom feed
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] (Why) Does lvmcreate --raid6 need 5 drives?
Date: Tue, 18 Sep 2018 09:41:25 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> We do have a constraint in lvm2 to require the raid6 minimum for N to 
> be 3.
> Configuring a raid6 LV (an array by MD terms) with 2 data stripes is
> suboptimal for performance,
> because data striping is minimal in this case.  In addition, the
> metadata overhead is maximal
> for parity, P- and Q-syndromes being half of the brutto size of the 
> raid6 LV.
My apologies.  I googled "brutto size" but came up with nothing.  I do 
have a basic understanding of P and Q syndromes so I think I have a 
vague understanding of your meaning.

I understand it's suboptimal, but not non-existent.  In particular why 
is this a restriction and not just a warning?

Performance aside, I could also argue that there's a use case for a 
minimal (and not degraded) set before expansion.


  reply	other threads:[~2018-09-17 23:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-16 23:36 [linux-lvm] (Why) Does lvmcreate --raid6 need 5 drives? tudor
2018-09-17 12:41 ` Heinz Mauelshagen
2018-09-17 23:41   ` tudor [this message]
2018-09-18  9:14     ` Heinz Mauelshagen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).