linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Bypassing LVM Restrictions - RAID6 With Less Than 5 Disks
Date: Mon, 2 May 2022 17:54:43 -0400	[thread overview]
Message-ID: <25200.21283.981034.416787@quad.stoffel.home> (raw)
In-Reply-To: <324D8F25-90D3-4165-BE86-11B217DAFDE4@icloud.com>

>>>>> "Alex" == Alex Lieflander <atlief@icloud.com> writes:

Alex> I actually used to use MDADM with LVM on top. I switched to pure
Alex> LVM for simplicity and per-disk host-managed
Alex> integrity-checking. I don’t know if MDADM has since gained the
Alex> ability to correct single-disk inconsistencies, but without
Alex> per-disk integrity-checking it would be technically impossible
Alex> to do this if 1 disk had already failed.

Can you tell me what you mean by "per-disk host-managed
integrity-checking"?  Are you running dm-integrity in your setup?  Can
you post the output of:

    lsblk

so we understand better what you have?  But in any case, good luck
with getting RAID6 solid and working as a pure LVM setup.  I don't
think you're going to make it happen any time soon, and I honestly
prefer to have seperate layers for my setup so that each layer does
it's own think and does it well.

John

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2022-05-02 21:54 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
2022-05-02 21:54     ` John Stoffel [this message]
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

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=25200.21283.981034.416787@quad.stoffel.home \
    --to=john@stoffel.org \
    --cc=linux-lvm@redhat.com \
    /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).