From: Alex Lieflander <firstname.lastname@example.org>
To: LVM general discussion and development <email@example.com>
Subject: Re: [linux-lvm] Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
Date: Mon, 2 May 2022 15:22:30 -0400 [thread overview]
Message-ID: <324D8F25-90D3-4165-BE86-11B217DAFDE4@icloud.com> (raw)
Thanks for the response.
John> Alex> 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.
John> Can you explain those reasons? In general, RAID10 gives you only 50% capacity, but much improved performance over RAID5/6 in terms of read/write performance.
John> But if you want to be able to handle the failure of any two disks in your RAID6, then I can understand your decision.
1. Resilience to any two disk failures/inconsistencies
2. Ability to safely and easily add single disks in the future† (Having 5 disks with my desired resiliency would require RAID6)
3. Ability to safely and easily switch between 1-disk-resiliency and 2-disk-resiliency in the future† (Going from a clean raid6_ls_6 to a clean raid5_ls is extremely easy by comparison)
†All conversions need to be online. With RAID10 I’d need to go from RAID10 -> RAID0 -> RAID5 (-> RAID6). This process is both lengthy and vulnerable to any single disk failure during part of the conversion.
John> Alex> Buying another disk would also be a waste of money because I don’t need 3-disks-worth of usable capacity.
John> That's fair.
John> Alex> 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.
John> I would instead build your RAID6 using MD, and then layer LVM on top of it. It works, it's solid and it runs really well.
John> Alex> 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.
John> If you don't know the code, then you're not going to get working RAID6 up and running any time soon.
John> Alex> 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?
John> I really can only suggest you setup RAID6 using the MD raid tools (mdadm) and then create your LVM PVs, VGs and LVs on top of that. It really works well.
John> Yes, you now need to have another tool to manage another layer, but since the MD system is well tested, reliable and just works, then I would go with it as the base.
I actually used to use MDADM with LVM on top. I switched to pure LVM for simplicity and per-disk host-managed integrity-checking. I don’t know if MDADM has since gained the ability to correct single-disk inconsistencies, but without per-disk integrity-checking it would be technically impossible to do this if 1 disk had already failed.
linux-lvm mailing list
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-05-02 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 17:11 [linux-lvm] Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks Alex Lieflander
2022-05-02 0:36 ` John Stoffel
2022-05-02 19:22 ` Alex Lieflander [this message]
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).