viano8 TBM Resolving LVM and Hard Disk PVID Issues - United States Resolving LVM and Hard Disk PVID Issues Technote (FAQ) Question Technote that discusses various issues with PVIDs and how to resolve them. Answer ‘The Logical Volume Manager (LVM) on AIX uses a Physical Volume Identiter (PVID) to keep track of disk drives that are part of an LVM volume group. Ths is system-generated 16-digt number that is stored physicaly on the harddrive and read into the. (00M, LVM also stores this PVID in the Volume Group Descriptor Area (VGDA) forthe volume group. Each PVID on a system ‘uniquely identifies one physical volume. Problems with PVIDs Duplicate PVID, ‘The same PVIO shows up on more than one disk Problem Diagnosis 1. Verify that you have a duplicate PVIO on multiple disks. $ Ispy Ifyou know the name of an imported volume group having the problem use: $ Ispy | grep VoNae The Ispy command reads out of the ODM, it does not read the PVID from disk. We need to check ifthe PVID listed in the ODM is the same as the PVID on disk 2. To read the PVID off the disk, you must og in as root or Suto it, and use: # Lquerypy -h /dev/ndisk7 80 10 Example output 98900080 @B92IACE 5610594 o98de0e0 909000 |... ‘The PVID of he disk is in colurnns 2 and 3. Possible Cause and Solution 1: ODM and PVID en Disk Do Not Match Ifthe PVID on disk does not match the ODM output from lspy, use the chdev command to re-read the proper PVID in from isk and repopulate the ODM, Example: # Aso | oreo hdiskea hp. ibm comisupportidocviow.wss7u vevino TBM Resolving LVM and Hard Disk PVID Issues - United States hdiskaa ceadbeefdeadveet None ‘Check to see ifthe PVID writen tothe disk is correct: # lquerypy -h /dev/ndisi2a 80 10 9900080 9BOSAARS 57708A61 eAeAe0ee 9000000 |...-K).d.-.-.-0+] So the ODM version does not match what is written onto the disk. Another way to vert isis to query the ODM directy # odaget -q “name-hdisk24 and atteibute-pvid Cut cust: rane = “hdisk22" attribute = "pvid' jeacbeetdeadbeef0029000000000000" value = type generic = "D rep = *s nls_index = 2 Force the system to re-read the PVID off disk and repopulate the ODM: # chdev -a pvsyes -1 hdiskas hdisk26 changed Now check that lspv shows the correct PUIO: 4 spy | grep héisk2e hdiskaa 00s0385577d8a62 None You can algo double-check the ODM cirectly # odnget -q “nameshdisk24 and attribute-pvid™ cust cunt name = “hdiska atteibute = "pyid’ value = "e90sea85577d8a610900000000000000" type = generic = "0 rep nis_index = 2 Possible Cause and Solution 2: The Disks Are Copies of Each Other Tinrecent years, SAN storage has become a popular way to attach new disks to systems using. fibrechannel network. Some of these SAN storage systems include way to make a bit-or-bit copy of each disk (or LUN) in order to take that to another site or computer. The copy is exact, down to the VGDA and PVID areas of the LUNs It bath of these disks, the original and the cony, are zoned to the same host and seen by efgmgr, twill cause the system to show duplicate PVIDs in commands such as Ispv, (Sv, and in the OOM. Varyonyg (either called from importvg or varyonvg) wil fal due to duplicate PVIDs: 28sano TBM Resolving LVM and Hard Disk PVID Issues - United States # importug -y datavg hdisk2e 0516-775 varyonvg: Physical volumes héisk21 and hdiskZ@ have identical PVIDs (#@@S@a8S470czeeb). 0516-788 inportvg: Unable to inport voluee group fron hdiskz9. [A.Find out it these disks are indeed copies of each other. fa copy ofthe volume group on the second disk (or set of disks) is not needed, the VGDA and PVID areas can be wiped out, allowing the user to create anew volume group on the disks One word of watning, this is a permanent change tothe disks. First, wipe the PVID of the drive using # chdev -a pveclear -1 hdiskx (If using another path manager, the name may be different) Next lear the VGDA olf the driv # chpy -C naiskx Thon you may use the mkvg command to create a new volume group on the disks, or add them toan existing volume group with extendvg. 8. If, however, the disks are copies of each other for use in a backup strategy, and BOTH the source and backup (or target) volume group need to exist on the same machine, then the target volume group will need to be imported using recreatevg. The benefit of using recreatevgis that it can change the PVIDs ofthe disks a itimports the volume group, and update the VGDA with ‘those new PVIDs, It should be noted at this point that AIX doos not allow two logical volumes to have the same name, or two filesystems to have ‘the same mount point. The recreatevg command by default will change the logical volume names and mount points, since i is ‘meant for recreating an oxsting volume group. By default recreatevg will change the existing logical volume names by avefixing them with the string filesystem mount point paths with "/fs’ These can be changed by using the ~L andy flags to recreatevg. and prefxing the For example, iT have volume group “origyg witha flesystem and log device, and a SAN copy of it on hdlisk: 4 Isvg -1 origve origvg Lv Name TPE LPs PPS PVs LV STATE MOUNT POINT loglver jfs2log 2 a 1 closed/syned N/A Fslve2 ses2 256255 «1 Closed/syncd_/data # Ispy | grep oriave disks easaansera3scec origvg, active disks easaassef23scec onteve, active J can clear the PVID off hdiské and then run recreatevg against it # chdev -a pveclear -1 hdisks hdisks changed # Aspy hdisks easaa8ser3356e orieve, active disks one None ae