Operating System - HP-UX
1834772 Members
3130 Online
110070 Solutions
New Discussion

HP-UX device files after powerpath downgrade

 
JamalEddine
New Member

HP-UX device files after powerpath downgrade

I'm using
emc clariion cx500
hp-ux system
powerpath
The system was running powerpath 4.5 and navisphere agent 6.16 and volume group was bound to the device files. The format of the device files was as follows. c10txdx, c11txdx, c12txdx and c13txdx.

I downgraded the powerpath from 4.5 to 4.3. before downgrading the vg was disable. after the downgrade I run the ioscan and insf -e to create the device files. The host (hpux) is able to see the luns and created the device files. But the name of the new devicefiles becomes like the following format c14txdx, c16txdx, c18txdx and c20txdx whcih is different from before downgrading the poweropath. When i try to enable the vg, i got an error that c10txdx, c11txdx, c12txdx and c13txdx cannot be found. So, i'm not able to create the logical volumes again. Is there any way to recreate the device file to map the old format c10, c11, c12 and c13 (to change the controller number) or what should i do.
BR
13 REPLIES 13
Lynn Hsu_2
Frequent Advisor

Re: HP-UX device files after powerpath downgrade

Hi BR,
We have similar environment. You can export (ex: vgexport -m mapfile04 vg04) then
1. mkdir /dev/vg04
2. mknod /dev/vg04/group c 64 0x040000
3. vgimport -m mapfile04 /dev/vg04 /dev/dsk/CxtYdZ
4. vgchange -a y vg04
5. vgcfgbackup /dev/vg04
6. mount ...
7. lvdisplay /dev/vg04/lvol1

Lynn
Bill Costigan
Honored Contributor

Re: HP-UX device files after powerpath downgrade

HPUX makes up the c numbers you could try to get it to reuse the c10 - c13 by deleting some special files and I think there is a file that might have to be modified.

As for me, I'd just vgimport the VG again using the new device file names.

You might have to do a vgexport first if you don't already have a vg map file.

Another approach (not that I'm recommending it) is to use the mknod command to recreate the old device file names using the major and minor numbers of the new device files.
IT_2007
Honored Contributor

Re: HP-UX device files after powerpath downgrade

If you want re-use them then you need to bounce the box.

If you don't want to bounce the box then you can use new device files by using the method in the 1st reply.
JamalEddine
New Member

Re: HP-UX device files after powerpath downgrade

Hi,
What are the special files to delete and what is the other one to modify

-HPUX makes up the c numbers you could try
-to get it to reuse the c10 - c13 by
-deleting some special files and I think
-there is a file that might have to be
-modified.

BR
Jim Mallett
Honored Contributor

Re: HP-UX device files after powerpath downgrade

A PowerPath version change alone shouldn't change the disk device files, I've upgraded a number of times, and downgraded PP before without a change. Did something else change like what switch ports are in use, or what HBAs are being used?

Unless there are other reasons it is important you reuse the old device files, I would just use Lynn's suggestion with a twist. "If you haven't already vgexported the VGs" you can use the -s option, this will allow for discovery of the new paths because the mapfile will contain the VGID. When you do the vgimport, each device will be searched for this VGID.

- Create a mapfile for each VG.
# vgexport -p -v -s -m /vgXX.mapfile vgXX

- Check the mapfiles for consistency (not required but good practice).
The first line should contain the VGID, and there should be a subsequent line for each LVOL.
# more /vgXX.mapfile
VGID c2644d3e4501d78a (example)
1 lvol1
2 lvol2

- Export the volume groups.
# vgexport vgXX

- You have already done the ioscan and insf -e.

- Make the directory and special file.
# mkdir /dev/vgXX
# mknod /dev/vgXX/group c 64 0x0?0000

- Import the VGs, again using the -s option.
# vgimport -v -s -m /vgXX.mapfile vgXX

- Activate VG and mount LVs.
# vgchange -a y vgXX
# mount -a

This will get your VGs running with the new paths. There are other ways, but this is by far the easiest.

Jim
Hindsight is 20/20
JamalEddine
New Member

Re: HP-UX device files after powerpath downgrade

Actually we are using Mc Data switch DS24M2
and the HBA A6795A. What happened is when we downgraded the system, the system reboots and hanged. Then we rebooted it again but I unplugged the FC cables. After doing so, we were able to boot the system. Then installed the PP and NaviAgent. Finally, we did the ioscan -fnC disk and insf -e. I noticed that new device files were created inaddition to the existing ones. I think, the system has a parameter that we have to reset to start numbering the device files like the previous ones.
Your help is highly appreciated since the application is still down.

BR
Khairy
Esteemed Contributor

Re: HP-UX device files after powerpath downgrade

Remove the old special files
# rmsf -a /dev/dsk/c10txdx
# rmsf -a /dev/dsk/c11txdx
# rmsf -a /dev/dsk/c12txdx
# rmsf -a /dev/dsk/c13txdx

Remove the new special files
# rmsf -a /dev/dsk/c14txdx
# rmsf -a /dev/dsk/c16txdx
# rmsf -a /dev/dsk/c18txdx
# rmsf -a /dev/dsk/c20txdx

Scan the disk again.
# ioscan -fnC disk

Run insf again to recreate the special files. It should have the old special files if no changes done in the san switch or disk array.
# insf -ve

If you haven't export the affected vg, then just activate it.
# vgchange -a y vgXX

Mount back all the filesystem.
# mount -a

Good luck! Inform us the outcome.
Yang Qin_1
Honored Contributor

Re: HP-UX device files after powerpath downgrade

It looks like you swapped two FC cable when you plug them back. The device files should not be changed if you do not change your hardware connections. No matter how you downgrade your system/software.

Try to swap those two FC cable and see if you can get orignal deive files.

Even you cannot get the same c number as long as those t numbers and d numbers are the same, it is not a disaster. You can easily import your VGs back -- that is what I do for our DR tests every year.

Yang
JamalEddine
New Member

Re: HP-UX device files after powerpath downgrade

Pursuant to the problem. I exported the vg before i downgrade the Powerpath. Whenever i execute the following command i get:

root@mmsc01 / # vgchange -a y vg02

vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c20t0d1":
Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Cross-device link
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t0d2":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t0d3":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t0d4":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t0d5":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t0d6":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t0d7":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t1d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t1d1":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t1d2":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t1d3":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t1d4":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t1d5":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t1d6":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t1d7":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t2d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t2d1":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t2d2":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t2d3":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t2d4":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t2d5":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t2d6":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t2d7":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t3d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t3d1":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t3d2":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t3d3":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t3d4":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t3d5":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t3d6":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t3d7":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c14t4d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c20t4d1":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "vg02":
Quorum not present, or some physical volume(s) are missing.

Yang Qin_1
Honored Contributor

Re: HP-UX device files after powerpath downgrade

"Cross-device link" point to LUN's conflect -- the LUNs used in more than one VG. You may need to double check vgimport input (those device files). If you can still find /etc/lvmconf/vg##.conf.old, run

strings vg##.conf.old |more

write down orignal device files for each VG and map them with your new device files vgimport those VGs again.

Yang
JamalEddine
New Member

Re: HP-UX device files after powerpath downgrade

this is the output of my vg02.conf.old
---------------------------------------
root@mmsc01 /etc/lvmconf # strings vg02.conf.old
CONFIG01
/dev/vg02
/dev/rdsk/c20t0d1
/dev/rdsk/c14t0d2
/dev/rdsk/c20t0d3
/dev/rdsk/c14t0d4
/dev/rdsk/c20t0d5
/dev/rdsk/c14t0d6
/dev/rdsk/c20t0d7
/dev/rdsk/c14t1d0
/dev/rdsk/c20t1d1
/dev/rdsk/c14t1d2
/dev/rdsk/c20t1d3
/dev/rdsk/c14t1d4
/dev/rdsk/c20t1d5
/dev/rdsk/c14t1d6
/dev/rdsk/c20t1d7
/dev/rdsk/c14t2d0
/dev/rdsk/c20t2d1
/dev/rdsk/c14t2d2
/dev/rdsk/c20t2d3
/dev/rdsk/c14t2d4
/dev/rdsk/c20t2d5
/dev/rdsk/c14t2d6
/dev/rdsk/c20t2d7
/dev/rdsk/c14t3d0
/dev/rdsk/c20t3d1
/dev/rdsk/c14t3d2
/dev/rdsk/c20t3d3
/dev/rdsk/c14t3d4
/dev/rdsk/c20t3d5
/dev/rdsk/c14t3d6
/dev/rdsk/c20t3d7
/dev/rdsk/c14t4d0
/dev/rdsk/c20t4d1
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
LVMREC01
~VGDA0001
VGSA0001DV
root@mmsc01 /etc/lvmconf #
Yang Qin_1
Honored Contributor

Re: HP-UX device files after powerpath downgrade

Apparently, it is not an old vg02.conf before the change or say you imported vg02 several times after the change. Is it possible to find back those vg##.conf or /etc/lvmtab before the change?

The other thing you can try is list all devices from all VGs which uses storage LUNs and "strings /etc/lvmtab". Cross check if there are some LUNs configured in more than one VG.


Yang
Bill Costigan
Honored Contributor

Re: HP-UX device files after powerpath downgrade

If you vgexported the volume group before doing the powerpath changes, the old PV device files wouldn't be in the /etc/lvmtab file. (unless you used the -p option which doesn't really do the export)

Once you receate the /dev/vg02 direcory and /dev/vg02/group you can do a vgimport using the map file you created with the vgexport and your new list of device files.

BTW - the file that contains the mapping of the c numbers to H/W paths is /etc/ioconfig which is used by ioinit. I suggest you stick with the vgexport/vgimport method.