Reboot and volume group not active

[Coolmar]

I have the following in the syslog:

There is a problem with the LVM configuration.

It keeps repeating over and over.

vgdisplay -v /dev/vg01
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 2
Open LV 2
Max PV 16
Cur PV 4
Act PV 4
Max PE per PV 8192
VGDA 8
PE Size (Mbytes) 4
Total PE 14622
Alloc PE 6944
Free PE 7678
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg01/lvol1
LV Status available/syncd
LV Size (Mbytes) 13888
Current LE 3472
Allocated PE 3472
Used PV 1

LV Name /dev/vg01/lvol2
LV Status available/syncd
LV Size (Mbytes) 13888
Current LE 3472
Allocated PE 3472
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c6t12d6
PV Name /dev/dsk/c4t12d6 Alternate Link
PV Status available
Total PE 3472
Free PE 3472
Autoswitch On

PV Name /dev/dsk/c6t12d5
PV Name /dev/dsk/c4t12d5 Alternate Link
PV Status available
Total PE 3472
Free PE 3472
Autoswitch On

PV Name /dev/dsk/c38t0d0
PV Name /dev/dsk/c35t0d0 Alternate Link
PV Status available
Total PE 3839
Free PE 367
Autoswitch On

PV Name /dev/dsk/c38t0d1
PV Name /dev/dsk/c35t0d1 Alternate Link
PV Status available
Total PE 3839
Free PE 367
Autoswitch On

LVINFO:
--- Logical volumes ---
LV Name /dev/vg01/lvol1
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 13888
Current LE 3472
Allocated PE 3472
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c38t0d0 3472 3472

--- Logical volumes ---
LV Name /dev/vg01/lvol2
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 13888
Current LE 3472
Allocated PE 3472
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c38t0d1 3472 3472

[Coolmar]

Something else interesting, I was able to have a LUN assigned from another IBM Shark SAN (DS800) and it worked perfectly, even after a reboot. Now the SAN I am having problems with is a DS8300 (newer model) but it should still work, shouldn't it?

[Scott Riley]

Sally,

I still think it's settings on the Shark array. It really seems like a storage problem, not a host problem at this point. Has your storage group confirmed the configuration on both arrays is the same?

[Coolmar]

Well this is what the SAN guy said, and I really don't know SAN technology at all so I can't help him.

Other then the fact that the interfaces on the ds8300 are different then the shark 800, they appear to be configured the same. I added another server (clustered AIX) to the same array and the luns are ok after a reboot. There are only 2 places in the config that allow me to choose the type of O/S type. The first is when the host is configured and SERVERA is showing that the host is HP-UX (HP). The other area is when we create the Volume group and in here and I selected HP. When I select HP it adds all the others you see in the screen capture. if I try to deselect the others it also removed HP.

[Sundar_7]

Hey Sally,

Since you are running out of ideas, let me through something at the table for you to try :-). If you want, try increasing the PVtimeout for the PV and reboot. May be, PV is not responding at boot time fast enough for the probe ? This may not even help but worth giving it a try

# pvchange -t 180 /dev/dsk/devicefile

Sundar

[Coolmar]

Thanks Sundar...I tried that and it didn't work. I still got the same error.

S.

[Coolmar]

After further investigation, it seems the errors are with the alternate paths to the disk. The primary seem to be fine. So when I reboot I get the error in my first post. However, the vg01 filesystems are mounted. I can do an lvdisplay and everything is fine. When I do a vgdisplay though, I get the following:

vgdisplay -v /dev/vg01
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c38t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c38t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 2
Open LV 2
Max PV 16
Cur PV 4
Act PV 4
Max PE per PV 8192
VGDA 8
PE Size (Mbytes) 4
Total PE 14622
Alloc PE 10416
Free PE 4206
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c38t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c38t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.


The c38t0d0 that it is complaining about is the alternate path to one of the disks. When I do a vgchange -a y /dev/vg01 everything is fine. So I suspect I could just add the vgchange -a y /dev/vg01 to the startup scripts but that is merely a bandaid and I want to fix the root of the problem. Why aren't the alternate paths found at boot time, but the primary paths are?

Thanks for all the help on this one everybody.

[Coolmar]

Another thing...I notice my original post has both primary and alternate missing. I wonder if running pvchange -t 180 on the disks fixed it for the primary disks. When I ran it on the c35 disks (primary paths) it worked fine. When I ran it on the c38 (alternate paths) it said :

Device file path "/dev/dsk/c38t0d1" is an alternate path
to the Physical Volume. Using Primary Link "/dev/dsk/c35t0d1".
Physical volume "/dev/dsk/c35t0d1" has been successfully changed.

[freddy_21]

please check with fcmsutil to check about fibre connection for disk c38txtx.

Did you already upgrade driver fcmsutil and patches for fibre chanel card?

You must check with ioscan command. i am afraid your device changes because rebooted that server.


Good luck
Freddy