linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Cyclic Group Z_1 <cyclicgroup-z1@yahoo.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Question on RAID integrity limitations
Date: Mon, 5 Jun 2023 10:33:43 -0500	[thread overview]
Message-ID: <20230605153343.GA32210@redhat.com> (raw)
In-Reply-To: <2119294287.3320828.1685752201585@mail.yahoo.com>

On Sat, Jun 03, 2023 at 12:30:01AM +0000, Cyclic Group Z_1 wrote:
> The lvmraid documentation says the following: "To work around some
> limitations, it is possible to remove integrity from the LV, make the
> change, then add integrity again. (Integrity metadata would need to
> initialized when added again.) ... The following are not yet permitted
> on RAID LVs with integrity: lvreduce, pvmove, snapshots, splitmirror,
> raid syncaction commands, raid rebuild." Does this mean that RAID
> rebuilds can only be done with integrity temporarily turned off?

It refers specifically to running the command "lvchange --rebuild".  I'm
not entirely sure how important that command is, but I'd be happy to hear
more about its usefulness.

> This seems risky given that rebuilds are often when RAID arrays undergo the
> most stress and are thus vulnerable to failures/errors (namely, for
> parity RAID). Additionally, is the suggested workaround for snapshots to
> temporarily turn off integrity when taking/using snapshots?  Thank you!

Snapshots were recently enabled:
https://sourceware.org/git/?p=lvm2.git;a=commit;h=fd6e113bba5fed5ee41152cde33220294c24ce2b

Dave

_______________________________________________
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:[~2023-06-05 15:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <2119294287.3320828.1685752201585@mail.yahoo.com>]

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=20230605153343.GA32210@redhat.com \
    --to=teigland@redhat.com \
    --cc=cyclicgroup-z1@yahoo.com \
    --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).