diff options
| author | corubba <corubba@gmx.de> | 2022-11-01 22:18:19 +0100 |
|---|---|---|
| committer | David Teigland <teigland@redhat.com> | 2022-11-11 12:08:59 -0600 |
| commit | 779fc3c0453d4a1abdfc62db740517467dbaf0e3 (patch) | |
| tree | e3820fd52e9d9cfcacb4b8f3de6d6925be3a5abb /man | |
| parent | c77384785d3bd3d0c265220395dc392b52e62218 (diff) | |
| download | lvm2-779fc3c0453d4a1abdfc62db740517467dbaf0e3.tar.gz | |
report: adjust lv_active_remotely for shared VGs
Add a note to the manpage that lvmlockd is unable to determine
accurately and without side-effects whether a LV is remotely active.
Also change the value of the lv_active_remotely option from false to
undefined for shared VGs to distinctly communicate that inability to
users. Only for local VGs it can be definitely stated that they are not
remotely active.
Signed-off-by: corubba <corubba@gmx.de>
Diffstat (limited to 'man')
| -rw-r--r-- | man/lvmlockd.8_main | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/man/lvmlockd.8_main b/man/lvmlockd.8_main index 717292dc6..7fa11df54 100644 --- a/man/lvmlockd.8_main +++ b/man/lvmlockd.8_main @@ -878,6 +878,10 @@ If lvmlockd fails or is killed while in use, locks it held remain but are orphaned in the lock manager. lvmlockd can be restarted with an option to adopt the orphan locks from the previous instance of lvmlockd. . +.IP \[bu] +The 'lvs' command does not report any remote state, because lvmlockd is +unable to passively check the remote active or lock state of an LV. +. .SH SEE ALSO . .BR lvm (8), |