pvchange(1M)
Message Text
Unable to detach the path or physical volume via the pathname provided.
Either use pvchange(1M) -a N to detach the PV using an attached path
or detach each path to the PV individually using pvchange(1M) –a n
Cause
The specified path is not part of any volume group, because the path has not been successfully
attached to the otherwise active volume group it belongs to.
Recommended Action
Check the specified path name to make sure it is correct. If the error occurred while detaching a
physical volume, specify a different path. If it is not clear whether any path was attached before,
individually detach each path to the physical volume using
pvchange
with the
–a n
option.
Message Text
Warning: Detaching a physical volume reduces the availability
of data within the logical volumes residing on that disk.
Prior to detaching a physical volume or the last available path to it,
verify that there are alternate copies of the data available on other
disks in the volume group. If necessary, use pvchange(1M) to reverse
this operation.
Cause
This warning is advisory. It is generated whenever a path or physical volume is detached.
Recommended Action
None.
vgcfgbackup(1M)
Message Text
Invalid LVMREC on Physical Volume pvname
Cause
The LVM header on the disk is incorrect. This can happen when an existing LVM disk is overwritten
with a command like
dd
or
pvcreate
. If the disk is shared between two systems, one system
might not be aware that the disk is already in a volume group. The corruption can also be caused
by running
vgchgid
incorrectly when using BC split volumes.
Recommended Action
Restore a known good configuration to the disk using
vgcfgrestore
. Be sure to use a valid copy
dated before the first occurrence of the problem. For example:
# vgcfgrestore –n vgname pvname
vgcfgrestore(1M)
Message Text
Cannot restore Physical Volume pvname
Detach the PV or deactivate the VG, before restoring the PV.
166 Warning and Error Messages