50 lines
1.4 KiB
Diff
50 lines
1.4 KiB
Diff
From a8871780844b22491314ab49b60cc10d802d9aa2 Mon Sep 17 00:00:00 2001
|
|
From: David Teigland <teigland@redhat.com>
|
|
Date: Thu, 25 Jun 2026 11:50:38 -0500
|
|
Subject: [PATCH 09/16] man lvmlockd: improve setlockargs description
|
|
|
|
(cherry picked from commit 41cbab67e9e21ac736cfe4f25ecf8d72db508358)
|
|
---
|
|
man/lvmlockd.8_main | 19 +++++++++++++++----
|
|
1 file changed, 15 insertions(+), 4 deletions(-)
|
|
|
|
diff --git a/man/lvmlockd.8_main b/man/lvmlockd.8_main
|
|
index a7a17c4df..c86a0a130 100644
|
|
--- a/man/lvmlockd.8_main
|
|
+++ b/man/lvmlockd.8_main
|
|
@@ -383,16 +383,27 @@ For more information on using PR with LVM in general, see
|
|
The vgcreate options to enable PR-based lock recovery in a new VG are shown above.
|
|
.P
|
|
To enable PR-based lock recovery in an existing VG, first enable PR (if
|
|
-not already), then change the lock args:
|
|
+not already), then change the lock args. Changing lock args can involve
|
|
+stopping/starting PR and locking at different stages. Changing the PR or
|
|
+lock args settings requires the VG to be stopped on all other nodes.
|
|
+.P
|
|
+.I Example
|
|
+.br
|
|
+.B $ vgcreate --shared
|
|
+.I VG
|
|
+.I devices
|
|
.br
|
|
.B $ vgchange --setpersist y
|
|
.I VG
|
|
.br
|
|
+.B $ vgchange --persist start
|
|
+.I VG
|
|
+.br
|
|
.B $ vgchange --setlockargs persist,notimeout
|
|
.I VG
|
|
-.P
|
|
-Changing the PR or lockargs settings requires the VG to be stopped on all
|
|
-other nodes.
|
|
+.br
|
|
+.B $ vgchange --persist start --lockstart
|
|
+.I VG
|
|
.P
|
|
Display the VG attributes configured by setpersist and setlockargs:
|
|
.br
|
|
--
|
|
2.54.0
|
|
|