ENQUIRY: Find PVID and VGID on Itaniums

[VK2COT]

Hello everyone,

As part of my own Operations Acceptance Testing
script for HP-UX servers, I added a
check for PVIDs and VGIDs:

http://www.circlingcycle.com.au/Unix-sources/HP-UX-check-OAT.pl.txt

On PA-RISC platforms, I played with seven different methods to check them (including dd(1), C programs, HP tool dump_lvmtab, vgexport with preview). Alas, most of
servers I see around do not have dump_lvmtab installed so I cannot rely on it and vgexport
only deals with VGIDs.

In the end, I settled with:

xd -An -j8200 -N16 -tx /dev/dsk/cXtYdZ

I found it in one older posting on the Net.
I cannot claim credit for it :) It seems to
work fine on different PA-RISC servers
I tested it.

Here is an example for some disks on a SuperDome vPar:

Internal boot disk:

PASS PV /dev/dsk/c0t2d0 available
INFO PV /dev/dsk/c0t2d0 queue depth
immediate_report = 1; queue_depth = 8
PASS PV /dev/dsk/c0t2d0 defined in LVM (/etc/lvmtab)
INFO PV /dev/dsk/c0t2d0 has PVID 4a6d2d1644f67c46
INFO PV /dev/dsk/c0t2d0 is in volume group VGID 4a6d2d1644f67bb7

XP12000 SAN LUN:

PASS PV /dev/dsk/c3t0d0 has alternate link /dev/dsk/c21t0d0
PASS PV /dev/dsk/c3t0d0 available
INFO PV /dev/dsk/c3t0d0 queue depth
immediate_report = 1; queue_depth = 8
PASS PV /dev/dsk/c3t0d0 defined in LVM (/etc/lvmtab)
INFO PV /dev/dsk/c3t0d0 has PVID 4a6d2d1644fcb384
INFO PV /dev/dsk/c3t0d0 is in volume group VGID 4a6d2d1644fcb385

A simple question: what would be a good
equivalent for similar command on Itaniums?
Has anybody tried it (I do not have many
Itaniums to play with).

The xd(1) command from above needs some
modification.

Regards,

VK2COT

[Olivier Masse · Accepted solution]

I'm almost sure it will be the same on ia64 sysems, except if the disks are boot disks; in that case, you'll need to check slice 2 (Example: pvdisplay /dev/dsk/c3t0d0s2). Slice 1 and 3 are reserved for the EFI boot area and the diagnostic partition.

This is possibly messy as I'm not convinced there's a sure way to find it out. You can check if there's an "s" in the device name, but it's not very robust. Maybe you could try idisk to figure it out.

I didn't think hard partitions would do a comback in my career, but that's how HP managed to cram three partitions on the boot disk without requiring too much modifications at the OS level.

There is some information here (most probably elsewhere as well):
http://docs.hp.com/en/5991-2701/apa.html

Good luck

[VK2COT]

Hello,

You are completely right. All I had to use
was the slice 2. I was too blind to
see a tree in the forrest :)

Here is a boot disk check on Itanium server:

xd -An -j8200 -N16 -tx /dev/dsk/c2t1d0s2
88217f8e 40817ba6 88217f8e 40817ba6

As expected, the first two numbers make a
PVID and the last two numbers are VGID.

Confirmed:

# cat /etc/lvmconf/vg00.mapfile
VGID 88217f8e40817ba6
1 lvol1
2 lvol2
3 lvol3
4 lvol4
5 lvol5
6 lvol6
7 lvol7
8 lvol8

This is good. I can update my Perl OAT script
(which now has close to 200 tests)...

Greetings from down-under (Sydney Australia)

VK2COT

[Olivier Masse]

My pleasure :)

VE2OMS

[VK2COT]

And since I see you are in amateur radio...
I have been licensed since 1973.

Morse code - an early adoption of
digital technology :)

73s de VK2COT (ex YU6ZCW, YU6FO, VK4FCW)

PS. I will update my Perl script later today
and maybe someone finds it useful.