From: Alex Lieflander <firstname.lastname@example.org>
Subject: [linux-lvm] Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
Date: Wed, 27 Apr 2022 13:11:36 -0400 [thread overview]
Message-ID: <7534073B-7DBD-46B5-9CA5-BFB3C603C75E@icloud.com> (raw)
Thank you for your continued work on LVM(2).
I have 4 disks that I’d really like to put into a RAID6. I know about RAID10, but it wouldn’t work well for me for several reasons. Buying another disk would also be a waste of money because I don’t need 3-disks-worth of usable capacity.
I know there was a question regarding this a few years ago, and the consensus was to not natively support that configuration. I can respect that (although I would urge you to reconsider), but I’d still like to do it on my machine.
So far I’ve tried removing the restrictions from the source code and recompiling (I don’t know C, but I’m familiar with general code syntax). I’ve slowly gotten further in the lvconvert process, but there seems to be many similar checks throughout the code.
I’m hoping someone could point me in the right direction towards achieving this goal. If I successfully bypass the user-space tool restrictions, will the rest of LVM likely work with my desired config? Would you be willing to allow the --force option to bypass the restrictions that are not strictly necessary, even at the expense of expected stability? Is there anything else you could suggest?
linux-lvm mailing list
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next reply other threads:[~2022-04-27 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 17:11 Alex Lieflander [this message]
2022-05-02 0:36 ` [linux-lvm] Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks John Stoffel
2022-05-02 19:22 ` Alex Lieflander
2022-05-02 21:54 ` John Stoffel
2022-05-07 3:33 ` Alex Lieflander
2022-05-07 20:41 ` Stuart D Gathman
2022-05-07 23:14 ` Alex Lieflander
2022-05-08 13:25 ` Stuart D Gathman
2022-05-09 0:18 ` John Stoffel
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).