When Good Disks Go Bad: Dealing with Disk Failures Under LVM (5900-3153, June 2013)
57
overwritten with a command like dd or pvcreate. If the disk is shared between two
systems, it is likely that one of the systems was not aware that the disk was already in a
volume group. The corruption can also be caused by running vgchgid incorrectly when
using BCV 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.
# vgcfgrestore –n vgname pvname
vgcfgrestore
Cannot restore Physical Volume pvname Detach the PV or deactivate the
VG, before restoring the PV.
Cause:
The vgcfgrestore command was used to initialize a disk that already belongs to an
active volume group.
Recommended Action:
Detach the physical volume or deactivate the volume group before attempting to restore
the physical volume. If there is reason to believe that the data on the disk is corrupted, the
disk can be detached and marked using vgcfgrestore then attached again without
replacing the disk. This causes LVM to reinitialize the disk and synchronize any mirrored
user data mapped there.
vgchange
Warning: couldn't query physical volume "pvname":
The specified path does not correspond to physical volume attached to
this volume group
Warning: couldn't query all of the physical volumes.
Cause:
This error has several possible causes:
a. The disk was missing when the volume group was activated, but was later restored.
This typically occurs when a system is rebooted or the volume group is activated with
a disk missing, uncabled, or powered down.
b. The disk LVM header was overwritten with the wrong volume group information. If the
disk is shared between two systems, it is likely that one of the systems was not aware
that the disk was already in a volume group. To confirm, check the volume group
information using the dump_lvmtab command, available from your HP support
representative, and look for inconsistencies. For example:
# dump_lvmtab -s | more
SYSTEM : 0x35c8cf58
TIME : 0x3f9acc69 : Sat Oct 25 15:18:01 2003
FILE : /etc/lvmtab
HEADER : version:0x03e8 vgnum:7
VG[00] VGID:35c8cf58 3dd13164 (@0x00040c) pvnum:2 state:0
/dev/vg00
(00) VGID:35c8cf58 3dd13164 PVID:35c8cf58 3dd13164
/dev/dsk/c0t6d0
(01) VGID:35c8cf58 3dd13164 PVID:35c8cf58 3dda4694
/dev/dsk/c4t6d0
VG[01] VGID:065f303f 3e63f01a (@0x001032) pvnum:92 state:0
/dev/vg01
(00) !VGID:35c8cf58 3f8df316 PVID:065f303f 3e63effa
/dev/dsk/c40t0d0
(01) !VGID:35c8cf58 3f8df316 PVID:065f303f 3e63effe