topic Re: unknown reason cause VG activation failed. in Operating System - HP-UX

unknown reason cause VG activation failed.

stephen peng — Fri, 18 Feb 2011 15:52:59 GMT

guys,
vgspstest contained c23t2d0 and c25t2d0(alternate link),syslog told:
vmunix: LVM: WARNING: VG 64 0x250000: LV 2: Some I/O requests to this LV are waiting
vmunix: indefinitely for an unavailable PV. These requests will be queued until
vmunix: the PV becomes available (or a timeout is specified for the LV).
vmunix: LVM: VG 64 0x250000: PVLink 31 0x172000 Wrong Disk!
vmunix: LVM: VG 64 0x250000: PVLink 31 0x192000 Wrong Disk!
vmunix: LVM: VG 64 0x250000: Lost quorum.
vmunix: 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 available:
vmunix: <31 0x172000>
vmunix: vxfs: WARNING: msgcnt 1 mesg 038: V-2-38: vx_dataioerr - /dev/vgspstest/lvspspt file system file data write error in dev/block 0/23283028
vmunix: LVM: NOTICE: VG 64 0x250000: LV 2: All I/O requests to this LV that were
vmunix: waiting indefinitely for an unavailable PV have now completed.
vmunix: Synchronous Page I/O error occurred while paging to/from disk
diskinfo of c23t2d0 and c25t2d0 was ok, and vgdisplay vgspstest:
--- Logical volumes ---
LV Name /dev/vgspstest/lvsps
LV Status available/syncd
LV Size (Mbytes) 268160
Current LE 4190
Allocated PE 4190
Used PV 1

LV Name /dev/vgspstest/lvspspt
LV Status available/syncd
LV Size (Mbytes) 256000
Current LE 4000
Allocated PE 4000
Used PV 1

--- Physical volumes ---
PV Name /dev/dsk/c23t2d0
PV Name /dev/dsk/c25t2d0 Alternate Link
PV Status unavailable
Total PE 8191
Free PE 1
Autoswitch On
Proactive Polling On
c23t2d0 and c25t2d0 were links of LUN on MSA1500. I reboot the server, then vgspstest was unable to activate, telling could not query c23t2d0 and c25t2d0, and pvdisplay could not query those two disks either.
what could be the cause of this issue? I could not get the status of the MSA1500, if there was disk failure causing LUN problem, diskinfo should fail to query that LUN, right?

regards
Stephen

Re: unknown reason cause VG activation failed.

nijokj — Sat, 19 Feb 2011 04:47:06 GMT

as per the above information your vg vgspstest having one physical volume PV Name /dev/dsk/c23t2d0 which is showing unavailable and PV Name /dev/dsk/c25t2d0 is the alternate link of /dev/dsk/c23t2d0 .That is why your vg is not activated

First of all check with ioscan whether this disk is CLAIMED or not.

ioscan -fnC disk

if it is showing CLAIMED check with diskinfo

diskinfo -v /dev/dsk/c23t2d0

if it is showing output then you need to check whther the disk is having any bad sector or tracks.

if all the above command are failed or ioscan showing "NO_HW" contact with hardware support to check whether there is any disk or cabling related issue.

Re: unknown reason cause VG activation failed.

Manix — Sat, 19 Feb 2011 06:47:56 GMT

vmunix: LVM: VG 64 0x250000: PVLink 31 0x172000 Wrong Disk!
vmunix: LVM: VG 64 0x250000: PVLink 31 0x192000 Wrong Disk!
>>>vmunix: LVM: VG 64 0x250000: Lost quorum.

So it says clearly ..the reason you asked for..
quorum at least 1 of the following PVs (represented by current link) must become available:

So we not why the vg didn`t got activated ..

Now we check the PV mapping again to the VGs,run vgscan -v -p -a (preview )& see if there is any change in the paths mapping.

PV Name /dev/dsk/c23t2d0
PV Name /dev/dsk/c25t2d0>>> Alternate Link

NOTE :: the other one is just a link so there
is just one physical disk.

check with "dd" command if the disk is fine
could be due to path not accessible while reboot.

Thanks

Manix

Re: unknown reason cause VG activation failed.

Manix — Sat, 19 Feb 2011 08:36:50 GMT

Do post vgscan -v -p -a output !!

Thanks
Manix

Re: unknown reason cause VG activation failed.

Ismail Azad — Sat, 19 Feb 2011 11:55:16 GMT

Hi,

How many PVs are there in the VG? Just one right or do you have a missing disk... You will notice that the device files mentioned are just coming from different controllers or in apt terminology sense they are "PV links" and as pointed you don't have 2 disks visible by LVM. A volume group will not activate if 51% of the available disks are available and at this point you have 0% available and hence VG will not activate. Neither will you be able to configure because it does not meet the "running quorum" of that VG. Please post the output mentioned by Manix.

Regards
Ismail Azad

Re: unknown reason cause VG activation failed.

Ismail Azad — Sat, 19 Feb 2011 11:57:25 GMT

Hi,

Typo error above

A volume group will not activate if 51% of the available disks are NOT AVAILABLE and at this point you have 0% available and hence VG will not activate.

Re: unknown reason cause VG activation failed.

stephen peng — Sat, 19 Feb 2011 14:52:16 GMT

guys,
application personel decided to recreate vgspstest yesterday so I could not post vgscan output!
string /etc/lvmtab showed that vgspstest only consisted one PV, do there was no PV lost situation.
after I reboot the box, ioscan said c23t2d0 and c25t2d0 were CLAIMED and diskinfo showed the exact size of these two disk, no I/O error. In fact, when that issue occured, bdf told:
bdf: /export/home/mboss/sps: I/O error
bdf: /export/home/mboss/spssd: I/O error
and vgdisplay output as I posted before, and I've got syslog as attachment.
I just wonder whether something happened at Storage site caused this issue.

regards
Stephen