panic when I vgreduce /dev/vg00 /dev/dsk/c1t6d0

[kapsoo kim]

Hi all.
I have a k380 system.
root disk was mirred but not boot disk connfigured so I tried remirror root disk.
=======================================
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (10/0.6.0) -- Boot Disk
/dev/dsk/c0t5d0 (10/0.5.0)
/dev/dsk/c1t6d0 (10/4/4.6.0)
Boot: lvol1 on: /dev/dsk/c0t6d0
/dev/dsk/c1t6d0
Root: lvol3 on: /dev/dsk/c0t6d0
/dev/dsk/c1t6d0
Swap: lvol2 on: /dev/dsk/c0t6d0
/dev/dsk/c1t6d0
Dump: lvol2 on: /dev/dsk/c0t6d0, 0
Dump: lvol9 on: /dev/dsk/c0t5d0, 1
==========================
lvreduce -m 0 /dev/vg00/lvol1~8 /dev/dsk/c1t6d0
vgreduce /dev/vg00 /dev/dsk/c1t6d0 ---> system panic

I don't know the reason...

[Roger Baptiste]

Before you do a vgreduce
on a disk, you need to make
sure there are no lv on
the disk. This can be
checked with pvdisplay command.
#pvdisplay /dev/dsk/c1t6d0

Even though you reduced
one LV on the disk, there is
a possibility of other LV's
on that disk.

If you system is running ,
can you post the
vgdisplay -v output
as well as the swapinfo -mt
output?

-raj

[harry d brown jr]

You need to post


vgdisplay -v vg00


right away so that we can see the vg00. c1t6d0 and c0t6d0 could be the same physical disk!

[Sridhar Bhaskarla · Accepted solution]

Kapsoo,

From the configuration, you have swap2 mirrored on c1t6d0. There should not be any problem if you try to reduce disks. If there are any physical volumes, then it should give out error and will not let you reduce the disk.
However, I suspect the crash could be due to lvol2 (swap). May be this logical volume was not removed or still active. Do a pvdisplay on this disk and see if there are any logical volumes active.

Also check the latest patches for LVM and make sure you have all the patches installed.

-Sri