diff options
author | David Teigland <teigland@redhat.com> | 2015-09-11 14:34:22 -0500 |
---|---|---|
committer | David Teigland <teigland@redhat.com> | 2015-09-11 14:34:22 -0500 |
commit | 8b8103efef9cc23eb8fe47cd7d16629560ffd2e3 (patch) | |
tree | 03c19e9335b7debbf7b4a21ac045eeda322be76d | |
parent | 6bc3d72a655395a7f1ca299d85000ff65280d24d (diff) | |
download | lvm2-8b8103efef9cc23eb8fe47cd7d16629560ffd2e3.tar.gz |
man lvmlockd: move and update text about vgremove
The requirement to stop VGs before vgremove applies
to both sanlock and dlm VGs.
-rw-r--r-- | man/lvmlockd.8.in | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/man/lvmlockd.8.in b/man/lvmlockd.8.in index 8567651a0..4e7abdf81 100644 --- a/man/lvmlockd.8.in +++ b/man/lvmlockd.8.in @@ -352,6 +352,10 @@ be displayed with 'vgs \-o+locktype,lockargs'. 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. +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 @@ -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 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 |