shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2025-08-03 08:22:00 +03:00
Code Releases Activity

man lvmlockd: move and update text about vgremove

Browse Source 
The requirement to stop VGs before vgremove applies
to both sanlock and dlm VGs.
This commit is contained in:
David Teigland
2015-09-11 14:34:22 -05:00
parent 6bc3d72a65
commit 8b8103efef
1 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
man/lvmlockd.8.in
View File

@ -352,6 +352,10 @@ be displayed with 'vgs \-o+locktype,lockargs'.
lockd VGs need to be "started" and "stopped", unlike other types of VGs. lockd VGs need to be "started" and "stopped", unlike other types of VGs.
See the following section for a full description of starting and stopping. See the following section for a full description of starting and stopping.
vgremove of a lockd VG will fail if other hosts have the VG started.
Run vgchange \-\-lock-stop <vgname> on all other hosts before vgremove.
(It may take several seconds before vgremove recognizes that all hosts
have stopped a sanlock VG.)
.SS starting and stopping VGs .SS starting and stopping VGs
@ -567,12 +571,6 @@ change the VG lock type back to "sanlock".
To place the lvmlock LV on a specific device, create the VG with only that To place the lvmlock LV on a specific device, create the VG with only that
device, then use vgextend to add other devices. device, then use vgextend to add other devices.
vgremove of a sanlock VG will fail if other hosts have the VG started.
Run vgchange \-\-lock-stop <vgname> on all other hosts before vgremove.
(It may take several seconds before vgremove recognizes that all hosts
have stopped.) This is necessary because while a host has a sanlock VG
started, it is using the internal lvmlock LV.
.SS shared LVs .SS shared LVs