From: ajs124 <linux-lvm@ajs124.de>
To: <linux-lvm@redhat.com>
Subject: [linux-lvm] raidintegrity on non top level LVs
Date: Tue, 2 Aug 2022 16:27:53 +0200 [thread overview]
Message-ID: <20220802162753.6c214fe5@desk> (raw)
Hi,
I've been wondering. Why does lvconvert not allow me to add raid
integrity to LVs that are not top level?
It only says "Integrity can only be added to top level raid LV."
Skimming the commit that added this [1] did not provide me with
an answer, so I thought I'd ask here.
Best Regards
[1]: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=d9e8895a96539d75166c0f74e58f5ed4e729e551
_______________________________________________
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/
next reply other threads:[~2022-08-03 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 14:27 ajs124 [this message]
2022-08-03 15:15 ` [linux-lvm] raidintegrity on non top level LVs David Teigland
2022-08-03 21:14 ` ajs124
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=20220802162753.6c214fe5@desk \
--to=linux-lvm@ajs124.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).