relocation. The bad block relocation policy of all logical volumes
will be set to NONE.
Volume Group version can be successfully changed to 2.1
Review complete. Volume group not modified
3.
After messages from the review indicate a successful migration, you can begin the actual
migration:
a.
Unlike in Review mode, the target volume group must meet certain conditions at execution
time, including being de-activated. Since the target volume group is active, we must
de-activate it before performing the actual migration:
# vgchange -a n vg01
b.
Now, you can perform the actual migration:
# vgversion -v -V 2.1 vg01
Performing "vgchange -a y -l -p -s vg01" to collect data
Activated volume group
Volume group "vg01" has been successfully activated.
The space required for Volume Group version 2.1 metadata on
Physical Volume /dev/disk/disk12 is 8448 KB, but available free
space is 1024 KB.
8 free user extents from the end of the Physical Volume /dev/disk/disk12
will be utilized to accommodate the Volume Group version 2.1 metadata.
Warning: Volume Group version 2.1 does not support bad block
relocation. The bad block relocation policy of all logical volumes
will be set to NONE.
Old Volume Group configuration for "/dev/vg01" has been saved in
"/etc/lvmconf/vgversion_vg01/vg01_1.0.conf"
Deactivating Volume Group "vg01"
Volume group "vg01" has been successfully deactivated.
New Volume Group configuration for "/dev/vg01" has been saved in
"/etc/lvmconf/vgversion_vg01/vg01_2.1.conf"
Removing the Volume Group /dev/vg01 from /etc/lvmtab
Applying the configuration to all Physical Volumes from
"/etc/lvmconf/vgversion_vg01/vg01_2.1.conf"
Volume Group configuration has been restored to /dev/rdisk/disk12
Creating the Volume Group of version 2.1 with minor number 0x5000.
Adding the Volume Group /dev/vg01 to /etc/lvmtab_p
Original Volume Group Version was 1.0
New Volume Group Version is 2.1
Volume Group version has been successfully changed to 2.1"
The output shows that the migration was successful.
4.
To verify the migration:
a.
You can use
vgdisplay
to verify the migration.
vgdisplay
requires its target volume
group to be activated. Since the target volume group could not be active during the
migration, we must activate it:
# vgchange -a y vg01
b.
Once activated, we can use
vgdisplay
to verify the migration:
# vgdisplay vg01 | grep -i version
VG Version 2.1
The version shows the correct final version of
2.1
.
Migration Recovery
When running
vgversion
, recovery configuration files and a recovery script are created so that
you can restore the target volume group to its original version in case there are problems during
the actual migration.
Common LVM Tasks
49