Recommended Action
See the recommended actions under the
“vgchange(1M)” (page 167)
error messages.
vgextend(1M)
Message Text
vgextend: Not enough physical extents per physical volume.
Need: #, Have: #.
Cause
The disk size exceeds the volume group maximum disk size. This limitation is defined when the
volume group is created, as a product of the extent size specified with the
–s
option of
vgcreate
and the maximum number of physical extents per disk specified with the
–e
option. Typically, the
disk is successfully added to the volume group, but not all of the disk is accessible.
Recommended Action
Use the
vgmodify
command to adjust the maximum number of physical extents per disk. Alternately,
you can re-create the volume group with new values for the
–s
and
–e
options.
vgimport(1M)
Message Text
vgimport: "/dev/vgname/group": not a character device.
Cause
The volume group device files do not exist, and this version of the
vgimport
command does not
automatically create them.
Recommended Action
Create the directory for the volume group, and create a group file, as described in
“Creating the
Volume Group Device File” (page 44)
.
Message Text
Verification of unique LVM disk id on each disk in the volume group
/dev/vgname failed.
Cause
There are two possible causes for this message:
1.
The
vgimport
command used the
–s
option and two or more disks on the system have the
same LVM identifier; this can happen when disks are created with BC copy or cloned with
dd
.
2.
LVM was unable to read the disk header; this can happen when you create new logical units
on a SAN array.
Recommended Action
1.
Use
vgimport
without the
–s
option. Alternately, use
vgchgid
to change the LVM identifiers
on copied or cloned disks.
2.
Retry the
vgimport
command.
vgextend(1M)
171
