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 steps for changing lock type

Browse Source 
were not quite correct
This commit is contained in:
David Teigland 2017-11-21 10:37:00 -06:00
parent bbaaf4f1d3
commit ea0463791d
1 changed files with 37 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
man/lvmlockd.8_main
View File

@ -706,19 +706,24 @@ To change the dlm cluster name in the VG when the VG is still used by the
original cluster: original cluster:
.IP \[bu] 2 .IP \[bu] 2
Stop the VG on all hosts: Start the VG on the host changing the lock type
.br
vgchange --lock-start <vgname>
.IP \[bu] 2
Stop the VG on all other hosts:
.br .br
vgchange --lock-stop <vgname> vgchange --lock-stop <vgname>
.IP \[bu] 2 .IP \[bu] 2
Change the VG lock type to none: Change the VG lock type to none on the host where the VG is started:
.br .br
vgchange --lock-type none <vgname> vgchange --lock-type none <vgname>
.IP \[bu] 2 .IP \[bu] 2
Change the dlm cluster name on the host or move the VG to the new cluster. Change the dlm cluster name on the hosts or move the VG to the new
The new dlm cluster must now be active on the host. Verify the new name cluster. The new dlm cluster must now be running on the host. Verify the
by: new name by:
.br .br
cat /sys/kernel/config/dlm/cluster/cluster_name cat /sys/kernel/config/dlm/cluster/cluster_name
@ -735,13 +740,14 @@ vgchange --lock-start <vgname>
.P .P
To change the dlm cluster name in the VG when the dlm cluster name has To change the dlm cluster name in the VG when the dlm cluster name has
already changed, or the VG has already moved to a different cluster: already been changed on the hosts, or the VG has already moved to a
different cluster:
.IP \[bu] 2 .IP \[bu] 2
Ensure the VG is not being used by any hosts. Ensure the VG is not being used by any hosts.
.IP \[bu] 2 .IP \[bu] 2
The new dlm cluster must be active on the host making the change. The new dlm cluster must be running on the host making the change.
The current dlm cluster name can be seen by: The current dlm cluster name can be seen by:
.br .br
cat /sys/kernel/config/dlm/cluster/cluster_name cat /sys/kernel/config/dlm/cluster/cluster_name
@ -768,21 +774,44 @@ All LVs must be inactive to change the lock type.
lvmlockd must be configured and running as described in USAGE. lvmlockd must be configured and running as described in USAGE.
.IP \[bu] 2
Change a local VG to a lockd VG with the command: Change a local VG to a lockd VG with the command:
.br .br
vgchange --lock-type sanlock|dlm <vgname> vgchange --lock-type sanlock|dlm <vgname>
.IP \[bu] 2
Start the VG on hosts to use it: Start the VG on hosts to use it:
.br .br
vgchange --lock-start <vgname> vgchange --lock-start <vgname>
.P
.SS changing a lockd VG to a local VG .SS changing a lockd VG to a local VG
Stop the lockd VG on all hosts, then run: All LVs must be inactive to change the lock type.
.IP \[bu] 2
Start the VG on the host making the change:
.br
vgchange --lock-start <vgname>
.IP \[bu] 2
Stop the VG on all other hosts:
.br
vgchange --lock-stop <vgname>
.IP \[bu] 2
Change the VG lock type to none on the host where the VG is started:
.br .br
vgchange --lock-type none <vgname> vgchange --lock-type none <vgname>
.P
If the VG cannot be started with the previous lock type, then the lock
type can be forcibly changed to none with:
vgchange --lock-type none --lock-opt force <vgname>
To change a VG from one lockd type to another (i.e. between sanlock and To change a VG from one lockd type to another (i.e. between sanlock and
dlm), first change it to a local VG, then to the new type. dlm), first change it to a local VG, then to the new type.