this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
#vgchange -a y /dev/vg01
vgchange: Warning: Couldn't attach to the volume group physical volume
"/dev/dsk/c0t3d0":
A component of the path of the physical volume does not exist.
Volume group "/dev/vg01" has been successfully changed.
Another sign of disk problem is seeing stale extents in the
lvdisplay
command output. If there
are stale extents on a logical volume even after running the
vgsync
or
lvsync
commands, you
might have an issue with an I/O path or one of the disks used by the logical volume, but not
necessarily the disk showing stale extents. For example:
# lvdisplay –v /dev/vg01/lvol3 | more
…
LV Status available/stale
…
--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2
0000 /dev/dsk/c0t3d0 0000 current /dev/dsk/c1t3d0 0100 current
0001 /dev/dsk/c0t3d0 0001 current /dev/dsk/c1t3d0 0101 current
0002 /dev/dsk/c0t3d0 0002 current /dev/dsk/c1t3d0 0102 stale
0003 /dev/dsk/c0t3d0 0003 current /dev/dsk/c1t3d0 0103 stale
…
All LVM error messages indicates which device file is associated with the problematic disk. This is
useful for the next step, confirming disk failure.
See
“Messages For All LVM Commands” (page 164)
for more information on messages from LVM
commands, their causes and recommended actions.
Disk Troubleshooting and Recovery Procedures
119