HP-UX System Administrator's Guide: Logical Volume Management (5900-3028, March 2013)

Message Text
LVM: Begin: Contiguous LV (VG mmm 0x00n000, LV Number: p) movement:
LVM: End: Contiguous LV (VG mmm 0x00n000, LV Number: p) movement:
Cause
This message is advisory. It is generated whenever the extents of a contiguous logical volume
belonging to version 2.x volume group is moved using pvmove. This message is generated
beginning with the September 2009 Update.
Recommended Action
None, if both the Begin and End message appear for a particular contiguous LV.
If the End message for a contiguous LV is missing in the syslog file, it probably means that the
pvmove operation could have been aborted while moving the extents of the LV in question. In this
case, the contiguous LV in question could have its extents laid out in a non-contiguous manner. If
so, it is recommended that the user run lvdisplay -v to check if the allocation policy for the
LV is broken. If it is broken, then perform the steps below to make the extents of this LV contiguous:
1. Change the allocation policy of this LV to default (see lvchange(1M)).
WARNING! If the LV is a root/boot/swap/dump volume, changing the LV policy to default
is not allowed. The lvchange command will fail in this case. You need to remove the LV
from boot records using lvrmboot(1M) command prior changing the allocation policy.
Remember to add it back to boot record (use lvlnboot(1M) once the operation is done.
For these reasons, though the pvmove can be done on current boot disk, we recommend you
to perform the movement on DRD clone disk to be safer.
2. Move the extents such that all the physical extents of the logical volume are contiguous (see
pvmove(1M)).
3. Change the allocation policy back to contiguous (see lvchange(1M)).
Message Text
LVM: VG mm 0xnn0000:
Data in one or more logical volumes on PV nn 0x0nn000
was lost when the disk was replaced.
This occurred because the disk contained the only copy of the data.
Prior to using these logical volumes, restore the data from backup.
Cause
LVM cannot synchronize the data on a replaced disk automatically, for example, when LVM
discovers an unmirrored logical volume residing on a disk that was just replaced.
Recommended Action
Restore the contents of the logical volume from backup.
Message Text
LVM: VG mm 0xnn0000: PVLink nn 0x0nn000 Detached.
Cause:
This message is advisory. It is generated whenever a disk path is detached.
Recommended Action
None.
176 Warning and Error Messages