shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity

man lvmlockd: mention pvmove restriction

Browse Source
This commit is contained in:
David Teigland 2016-01-12 12:01:53 -06:00
parent 0c6946b4ce
commit 9e336582f4
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
man/lvmlockd.8.in
View File

@ -566,7 +566,8 @@ where the GL lock must be manually enabled after a vgremove.
A sanlock VG contains a hidden LV called "lvmlock" that holds the sanlock
locks. vgreduce cannot yet remove the PV holding the lvmlock LV. To
remove this PV, change the VG lock type to "none", run vgreduce, then
change the VG lock type back to "sanlock".
change the VG lock type back to "sanlock". Similarly, pvmove cannot be
used on a PV used by the lvmlock LV.
To place the lvmlock LV on a specific device, create the VG with only that
device, then use vgextend to add other devices.
@ -852,8 +853,8 @@ stopped the VG lockspace. Stop the VG on all hosts using vgchange
\-\-lock-stop.
.IP \[bu] 2
vgreduce of a PV in a sanlock VG may fail if it holds the internal
"lvmlock" LV that holds the sanlock locks.
vgreduce or pvmove of a PV in a sanlock VG will fail if it holds the
internal "lvmlock" LV that holds the sanlock locks.
.IP \[bu] 2
lvmlockd uses lock retries instead of lock queueing, so high lock