HP-UX 11i v3 Using LVM Logical Volume Snapshots (September 2010)

34
The pvmove operation fails if the logical volumes specified are inoperative or if the physical
volumes specified contain logical volumes that are inoperative. Delete all such inoperative snapshot
logical volumes that have caused the pvmove operation to fail and retry.
• Error: The specified logical volume "/dev/vg01/lvol1_S2" is
inoperative.
lvextend cannot be performed on logical volumes that are
inoperative.
Increasing the number of pre-allocated extents of an inoperative space-efficient snapshot logical
volume using lvextend failed. A snapshot logical volume is of no use because read and write
I/Os to the snapshot fail and it is no longer a point-in-time image of the original LV. Delete all such
inoperative snapshot logical volumes.
• Cannot find a free physical extent for pre-allocated extent
of logical volume "/dev/vg01/lvol1_S2".
If no free physical extent is found for a pre-allocated extent of a space-efficient snapshot logical
volume, pvmove fails. Add a physical volume to the volume group or free up extents to create free
user extents that pvmove can use, based on the allocation policy of the snapshot logical volume.
• Space worth 5 extents will be freed from the Physical Volume
"/dev/disk/disk4" during the conversion. Please run vgmodify(1M) to
utilize the freed up space.
The on-disk metadata space required for a volume group with Version 2.2 is greater than that
required for a volume group with Version 2.0 or 2.1. During conversion from a Version 2.2 volume
group to a Version 2.1 or 2.0 volume group (using vgversion), some metadata space is freed
up, which you can use by running vgmodify.
• The size of the volume group has been increased to 4194304m during
conversion in order to include the unused space on the physical volumes
present in the volume group.
During conversion from a Version 1.0 volume group to a Version 2.x volume group (using
vgversion), the maximum size of the volume group is increased, taking into account all the
unused space on the physical volumes present in the volume group.
• Error: The Logical Volume "/dev/vg01/lvol1_S2" has pre-allocated
extents associated with it. Automatic re-balance operation is not
supported for the logical volumes having pre-allocated extents.
If a logical volume has pre-allocated extents associated, the automatic rebalance operation using
pvmove is not supported. Use pvmove without the rebalance option to move extents of the
logical volume.
• Error: The Physical Volume "/dev/disk/disk4" has pre-allocated
extents associated with it. Automatic re-balance operation is not
supported on physical volumes having pre-allocated extents.
If a physical volume has pre-allocated extents associated, the automatic rebalance operation using
pvmove is not supported. Use pvmove without the rebalance option to move extents of the
physical volume.
• Warning: The volume group configuration for volume group "/dev/vg01" has
not been backed up. If the existing configuration backup file is
restored on to all the physical volumes, then, the data contained in the
logical volumes may be corrupt after the next activation. It is
recommended that the volume group be deactivated only after the volume
group configuration is backed up successfully.