PVLink 31 0x090100 Failed!

[Sebastian Szewczyk]

Hello,

I have some problem with Alternate link to some vg group - I think that.
My errors in syslog.log is which i see one time on 4 day.

This error in ssylog.log is:
Oct 31 09:42:31 xtw vmunix: LVM: VG 64 0x010000: PVLink 31 0x090100 Failed! The
PV is still accessible.
Oct 31 09:42:31 xtw vmunix: LVM: VG 64 0x010000: PVLink 31 0x090100 Recovered.
Oct 31 09:42:32 xtw vmunix: LVM: VG 64 0x010000: Lost quorum.
Oct 31 09:42:32 xtw vmunix: This may block configuration changes and I/Os. In or
der to reestablish quorum at least 1 of the following PVs (represented by curren
t link) must become available:
Oct 31 09:42:32 xtw vmunix: <31 0x070100>
Oct 31 09:42:32 xtw vmunix: LVM: VG 64 0x010000: Reestablished quorum.

I have group vgsap which present from EVA.

xtw(root):/dev/dsk# vgdisplay -v vgsap
--- Volume groups ---
VG Name /dev/vgsap
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 2
Open LV 2
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4607
VGDA 2
PE Size (Mbytes) 4
Total PE 4606
Alloc PE 4606
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vgsap/lvol1
LV Status available/syncd
LV Size (Mbytes) 4000
Current LE 1000
Allocated PE 1000
Used PV 1

LV Name /dev/vgsap/lvol2
LV Status available/syncd
LV Size (Mbytes) 14424
Current LE 3606
Allocated PE 3606
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c7t0d1
PV Name /dev/dsk/c9t0d1 Alternate Link
PV Status available
Total PE 4606
Free PE 0
Autoswitch On
My /etc/lvmtab
xtw(root):/etc# strings lvmtab
/dev/vg00
/dev/dsk/c2t1d0s2
/dev/dsk/c3t0d0s2
/dev/vgsap
E6,\
/dev/dsk/c7t0d1
/dev/dsk/c9t0d1

Disk from I have this error is:

xtw(root):/dev/dsk# ll
total 0
brw-r----- 1 bin sys 31 0x000000 Oct 6 10:56 c0t0d0
brw-r----- 1 bin sys 31 0x021000 Oct 6 10:56 c2t1d0
brw-r----- 1 bin sys 31 0x021001 Oct 6 11:43 c2t1d0s1
brw-r----- 1 bin sys 31 0x021002 Oct 6 10:56 c2t1d0s2
brw-r----- 1 bin sys 31 0x021003 Oct 6 10:56 c2t1d0s3
brw-r----- 1 bin sys 31 0x030000 Oct 6 10:56 c3t0d0
brw-r----- 1 bin sys 31 0x030001 Oct 10 15:08 c3t0d0s1
brw-r----- 1 bin sys 31 0x030002 Oct 10 15:08 c3t0d0s2
brw-r----- 1 bin sys 31 0x030003 Oct 10 15:08 c3t0d0s3
brw-r----- 1 bin sys 31 0x070100 Oct 18 12:53 c7t0d1
brw-r----- 1 bin sys 31 0x090100 Oct 18 12:53 c9t0d1

What can I do i that situation. I should remove one alternate link and add them second time. Please give me some advice.

seboizm

[Steven E. Protter]

Shalom,

I should remove one alternate link and add them second time.

If this solves the problem it should be done.

Note this could have been caused by a temporary hardware/san network problem and may recur.

SEP

[Sebastian Szewczyk]

Thanks for your advice.
You can give me procedure how can Ido something like that. I very sorry thath i help you about that simple thing. But I want to have certainty what i must do.

seboizm

[LinuxNotMS]

What type of storage do you use? If you are using an EVA that uses Active / Active pathing, and if you are using Autopath, if a switch reboots you will see this type of error in your syslog. Also, if you are in the configuration I mentioned, then the alternate link at the VG level is not required as Autopath takes care of the alternate link.

[vinod_25]

Hi Seb,

You have decoded the major and minor numbers very well from the syslog.

31 ==> disk
0x090100 ==> c9t0d1
64 ==> Volume Group
0x010000 ==> /dev/vgsap (in your case)

Quorum failed becuase one of the two paths failed, and it got re-established in the very same second... this is what called a hiccup - may be due to SAN switch/network glitch.

Get your SAN team engaged to verify SAN switch port/cabling etc...as you said it occours once in every 4th day... check the time if it is of the same time every fourth day ... then defenitely some maintenance is carried out by your SAN folks.

I dont find any requirement of re-linking the PV.

Nothing to worry. just get in touch with your SAN folks...

or if you still need to know how to relink PV's let me know, i will give you the set of commands... it is so easy

regds,
Vinod

[vinod_25]

Hi Seb,

Also to find whether both the PVlinks corressponds to same PV, you can use this command

# echo "0x2008?4D" | adb /dev/dsk/c9t0d1

2008: 894960601 1067429315 894960601 1067430042

# echo "0x2008?4D" | adb /dev/dsk/c7t0d1

2008: 894960601 1067429315 894960601 1067430042

The command o/p that is displayed is the LVM header of the disks and is displayed in below format.

PVRA: CPU-ID PV-ID CPU-ID VG-ID

You can see that both the o/p are same that means both links to a single PV.

Regards,
Vinod K

[Sebastian Szewczyk]

Ok Ichange the FC cable and after week I have communicate in my syslog.log:
Nov 13 07:53
LVM: VG 64 0x010000: PVLink 31 0x090100 Failed! The PV is still accessible.
LVM: VG 64 0x010000: PVLink 31 0x090100 Recovered.
LVM: VG 64 0x010000: PVLink 31 0x090100 Failed! The PV is still accessible.
LVM: VG 64 0x010000: PVLink 31 0x090100 Recovered.
LVM: VG 64 0x010000: Lost quorum.
This may block configuration changes and I/Os. In order to reestablish quorum at
least 1 of the following PVs (represented by current link) must become availabl
e:
<31 0x070100>
LVM: VG 64 0x010000: Reestablished quorum.

Please give me some advice what can I do with that situation. I think that i need Hp service? Pleace give me some advice.
I think about driver and firmaware of FC card.
Now is:
HP Tachyon XL2 Fibre Channel Mass Storage Adapter
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon
XL2 Driver B.11.23.0512 $Date: 2005/09/20 12:22:47 $Revision: r11.23/1