SLVM Single-Node Online Reconfiguration (SLVM SNOR)

6. Export the changes to other cluster nodes if required.
If the configuration change required the creation or deletion of a new logical or
physical volume (i.e. any of the following commands were used: lvcreate(1M),
lvreduce(1M), vgextend(1M), vgreduce(1M), lvsplit(1M), lvmerge(1M)), then the
following sequence of steps is required.
Warning: If one of the above commands was used to change the configuration of the
VG, and the mapfile, reflecting the change of configuration, is not imported on all
the other nodes, then unexpected errors could occur. For example, errors would be
reported if:
a) A vgchange tries to reattach PVs which were removed using vgreduce.
b) A logical volume which was reduced via lvreduce is opened.
6.1 From node1, export the mapfile for vg_shared.
vgexport -s -p -m /tmp/vg_shared.map vg_shared
6.2 Copy this mapfile /tmp/vg_shared to all the other nodes of the cluster.
6.3 On the other cluster nodes, export vg_shared and re-import it using the new map
file.
ls -l /dev/vg_shared/group
crw-rw-rw- 1 root sys 64 0x050000 Nov 16 15:27 /dev/vg_shared/group
Note the minor number (0x050000 in the above example)
vgexport vg_shared
mkdir /dev/vg_shared
mknod /dev/vg_shared/group c 64 0x050000 (minor number should match with above)
vgimport -m /tmp/vg_shared.map -s vg_shared
Note: The vgimport(1M)/vgexport(1M) sequence will not preserve the order of
physical volumes in the /etc/lvmtab file. If the ordering is significant due to the
presence of active-passive devices, or if the volume group has been configured to
maximize throughput by ordering the paths accordingly, the ordering would need to
be repeated. In this case it may be better to use the vgexport and vgimport with the -f
flag instead and manually edit the file if device paths differ.
7. Change the activation mode back to shared in all the cluster nodes