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: update method for changing lock type

Browse Source 
The old description did not work.
This commit is contained in:
David Teigland 2015-07-13 16:33:58 -05:00
parent 3da88b8917
commit d41bab4028
1 changed files with 32 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
man/lvmlockd.8.in
View File

@ -500,20 +500,43 @@ A small sanlock VG dedicated to holding the global lock can avoid the case
where the GL lock must be manually enabled after a vgremove.
.SS changing lock type
To change a local VG to a lockd VG:
vgchange --lock-type sanlock|dlm <vg_name>
.SS changing a local VG to a lockd VG
All LVs must be inactive to change the lock type.
To change a clvm VG to a lockd VG:
lvmlockd must be configured and running as described in USAGE.
vgchange --lock-type sanlock|dlm <vg_name>
Change a local VG to a lockd VG with the command:
.br
vgchange \-\-lock\-type sanlock|dlm <vg_name>
Changing a lockd VG to a local VG is not yet generally allowed.
(It can be done partially in certain recovery cases.)
Start the VG on any hosts that need to use it:
.br
vgchange \-\-lock\-start <vg_name>
.SS changing a clvm VG to a lockd VG
All LVs must be inactive to change the lock type.
1. Change the clvm VG to a local VG.
Within a running clvm cluster, change a clvm VG to a local VG with the
command:
vgchange \-cn <vg_name>
If the clvm cluster is no longer running on any nodes, then extra options
can be used forcibly make the VG local. Caution: this is only safe if all
nodes have stopped using the VG:
vgchange \-\-config 'global/locking_type=0 global/use_lvmlockd=0'
.RS
\-cn <vg_name>
.RE
2. After the VG is local, follow the steps described in "changing a local
VG to a lockd VG".
.SS vgremove and vgreduce with sanlock VGs