From: David Teigland <teigland@sourceware.org>
To: lvm-devel@redhat.com
Subject: main - man: lvmraid update limitations
Date: Mon, 5 Jun 2023 15:44:17 +0000 (GMT) [thread overview]
Message-ID: <20230605154417.2ED61388202D@sourceware.org> (raw)
Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=8e53b3bc14a03c243d10fc6bd9a7a8dc43d0a4d4
Commit: 8e53b3bc14a03c243d10fc6bd9a7a8dc43d0a4d4
Parent: e2ecc6c763557462a4bc3d88bbc883917eb0f010
Author: David Teigland <teigland@redhat.com>
AuthorDate: Mon Jun 5 10:43:51 2023 -0500
Committer: David Teigland <teigland@redhat.com>
CommitterDate: Mon Jun 5 10:43:51 2023 -0500
man: lvmraid update limitations
---
man/lvmraid.7_main | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/lvmraid.7_main b/man/lvmraid.7_main
index 26938da83..086f53491 100644
--- a/man/lvmraid.7_main
+++ b/man/lvmraid.7_main
@@ -839,7 +839,7 @@ to do this.)
RAID LVs with integrity cannot yet be used as sub LVs with other LV types.
.P
The following are not yet permitted on RAID LVs with integrity: lvreduce,
-pvmove, snapshots, splitmirror, raid syncaction commands, raid rebuild.
+pvmove, lvconvert --splitmirrors, lvchange --syncaction, lvchange --rebuild.
.
.SH RAID1 TUNING
.
reply other threads:[~2023-06-05 15:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230605154417.2ED61388202D@sourceware.org \
--to=teigland@sourceware.org \
--cc=lvm-devel@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