System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Need steps to create a SPECIFIC persistent DSF, or change it.

 
SOLVED
Go to solution

Need steps to create a SPECIFIC persistent DSF, or change it.

Hi,

Scoured the HP Native MP guide, SCSIMGR guide and a number of others NO luck. Saw some other threads on the topic that dance around without directly answering the question. So thought I would start a new thread. I know how to use scsimgr to replace a WWID but that is not quite the thing I need.

I need to change disk38 to be another DSF that I specify. When I add a disk that is automatically assigned to /dev/rdisk/disk38 and remove/readd it comes back again as disk38.

How can I change this? I would like to also be able to match up /dev/rdisk/disk names across more than one system if needed.

How can I remove this disk38 and add it back as disk100 for example? Can I do that? What are my options.

disk 38 64000/0xfa00/0xb esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016041e039a7.0x6000000000000
0/3/0/0/0/0.0x5006016941e039a7.0x6000000000000
0/3/0/0/0/1.0x5006016141e039a7.0x6000000000000
0/3/0/0/0/1.0x5006016841e039a7.0x6000000000000
/dev/disk/disk38 /dev/rdisk/disk38


Thanks!
7 REPLIES
Earl_Crowder
Trusted Contributor

Re: Need steps to create a SPECIFIC persistent DSF, or change it.


iobind(1M) might be what you're looking for.
Mounaam
Trusted Contributor
Solution

Re: Need steps to create a SPECIFIC persistent DSF, or change it.

for example:
# rmsf -x (clean stale)
# set -- $(lssf /dev/disk/disk38)
# echo "$6 disk 100" > infile
# ioinit -f infile
# insf -e -C disk -I 100
# rm /dev/*disk/disk38

Re: Need steps to create a SPECIFIC persistent DSF, or change it.

Earl,

Thank you I will play with that command and get more familiar.


Mounamm,

Thanks VERY MUCH. That worked like a charm. I am very grateful for your help. This answers my questions to the tee and represents one of the most helpful experiences I've had.

disk 100 64000/0xfa00/0xb esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016041e039a7.0x6000000000000
0/3/0/0/0/0.0x5006016941e039a7.0x6000000000000
0/3/0/0/0/1.0x5006016141e039a7.0x6000000000000
0/3/0/0/0/1.0x5006016841e039a7.0x6000000000000
/dev/disk/disk100 /dev/rdisk/disk100



Re: Need steps to create a SPECIFIC persistent DSF, or change it.

One more question if you dont mind. I am looking at the man page but not 100% clear to "me" how to kill a stale entry that the rmsf -x does not seem to clean up.

There is no disk34 at all yet it is somehow bound to a path in the IO system. Can you tell me how to clear out disk34 or get more info when it appears to not be a real disk?

# set -- $(lssf /dev/disk/disk38)
# echo "$6 disk 34" > infile
# ioinit -f infile
ioinit: Instance number 34 already exists for class disk.
Input line 1: 64000/0xfa00/0xb disk 34
# ls /dev/rdisk/disk3*
/dev/rdisk/disk30 /dev/rdisk/disk31 /dev/rdisk/disk32 /dev/rdisk/disk33 /dev/rdisk/disk38
#


Mounaam
Trusted Contributor

Re: Need steps to create a SPECIFIC persistent DSF, or change it.

have you tried:
# rmsf -H 64000/0xfa00/0xb

what is the result of:
# ioscan -C disk -I 34

Regards,
Mounaam

Re: Need steps to create a SPECIFIC persistent DSF, or change it.

Yes thanks I did try that and the command does remove that hardware path device but next time I try to add it as the device I want it gets an error. Somehow it seems like the io config has some junk I cant clean out. The error I get after that is there is NO device with that hw path present in the system.

I can run back through this today and post the exact output if that would be helpful in diagnosis.

It seems like when I added the initial disk 28,29,30,31,32,33 the system was happy and assigning numbers in sequence but later when I created the next sequential lun on the Clariion and presented the 7th lun it came in as disk38. And there seems to be nothing i can do to clean out those apparently occupied slots.

Some of this activity did clean out something because an IOSCAN now brings that 7th disk back online everytime as disk36 now. So that is an improvement I guess. My goal is to know how to stage customer systems and make them identical.

Thanks!! I'll post again today.

Re: Need steps to create a SPECIFIC persistent DSF, or change it.

Mounamm,

Okay this is making sense now but let me explain where the light bulb came on. I guess Iâ d already read this somewhere but had forgotten the details. So I was basically barking up the wrong tree trying to remove the disk# or instances that belonged to paths. DUH!!!

The cool thing is that I was able to rmsf all the devices and reboot and that cleanly reshuffled all the devices so the paths used disk 2-29 for paths (28 total) and then the actual device lun DSFs began at disk30 through 36 (7 total).

The problem before with disk 28-33 created then later adding a 7th lun makes perfect sense. The 7th lun would obviously grab the next four DSFs for lun paths then assign the lun DSF to disk38 which is the next available file name. So I was just being dense on this one. And I threw you a curve.

The bottom line is the information you gave me is 100% perfect for what I need. I am looking real good and I can now document this for our teams. We support EVA and MSA and I assume they work the same exact way.

Your help has been superb.

SYSTEM REBOOTED SEE NEW ASSIGNMENTS DISK 30-36 (7 each)
# ioscan -m lun
Class I Lun H/W Path Driver S/W State H/W Type Health Description
======================================================================
disk 1 64000/0xfa00/0x0 esdisk CLAIMED DEVICE online HP IR Volume
0/2/1/0.0x5384177e4c706d9.0x0
/dev/disk/disk1 /dev/rdisk/disk1
/dev/disk/disk1_p1 /dev/rdisk/disk1_p1
/dev/disk/disk1_p2 /dev/rdisk/disk1_p2
/dev/disk/disk1_p3 /dev/rdisk/disk1_p3
disk 30 64000/0xfa00/0x5 esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016041e039a7.0x0
0/3/0/0/0/0.0x5006016941e039a7.0x0
0/3/0/0/0/1.0x5006016141e039a7.0x0
0/3/0/0/0/1.0x5006016841e039a7.0x0
/dev/disk/disk30 /dev/rdisk/disk30
disk 31 64000/0xfa00/0x6 esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016041e039a7.0x1000000000000
0/3/0/0/0/0.0x5006016941e039a7.0x1000000000000
0/3/0/0/0/1.0x5006016141e039a7.0x1000000000000
0/3/0/0/0/1.0x5006016841e039a7.0x1000000000000
/dev/disk/disk31 /dev/rdisk/disk31
disk 32 64000/0xfa00/0x7 esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016041e039a7.0x2000000000000
0/3/0/0/0/0.0x5006016941e039a7.0x2000000000000
0/3/0/0/0/1.0x5006016141e039a7.0x2000000000000
0/3/0/0/0/1.0x5006016841e039a7.0x2000000000000
/dev/disk/disk32 /dev/rdisk/disk32
disk 33 64000/0xfa00/0x8 esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016041e039a7.0x6000000000000
0/3/0/0/0/0.0x5006016941e039a7.0x6000000000000
0/3/0/0/0/1.0x5006016141e039a7.0x6000000000000
0/3/0/0/0/1.0x5006016841e039a7.0x6000000000000
/dev/disk/disk33 /dev/rdisk/disk33
disk 34 64000/0xfa00/0x9 esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016041e039a7.0x3000000000000
0/3/0/0/0/0.0x5006016941e039a7.0x3000000000000
0/3/0/0/0/1.0x5006016841e039a7.0x3000000000000
0/3/0/0/0/1.0x5006016141e039a7.0x3000000000000
/dev/disk/disk34 /dev/rdisk/disk34
disk 35 64000/0xfa00/0xa esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016941e039a7.0x4000000000000
0/3/0/0/0/0.0x5006016041e039a7.0x4000000000000
0/3/0/0/0/1.0x5006016841e039a7.0x4000000000000
0/3/0/0/0/1.0x5006016141e039a7.0x4000000000000
/dev/disk/disk35 /dev/rdisk/disk35
disk 36 64000/0xfa00/0xb esdisk CLAIMED DEVICE online DGC RAID 5
0/3/0/0/0/0.0x5006016941e039a7.0x5000000000000
0/3/0/0/0/0.0x5006016041e039a7.0x5000000000000
0/3/0/0/0/1.0x5006016841e039a7.0x5000000000000
0/3/0/0/0/1.0x5006016141e039a7.0x5000000000000
/dev/disk/disk36 /dev/rdisk/disk36

NOW TRY TO REASSIGN TO DISK 2 and see how itâ s already allocated
# rmsf -x
# set -- $(lssf /dev/rdisk/disk30)
# echo "$6 disk 2" > infile
# ioinit -f infile
ioinit: Instance number 2 already exists for class disk.
Input line 1: 64000/0xfa00/0x5 disk 2

ALL of these instances from #2 to #29 are reserved for these 7 luns x 4 paths = 28 total plus the local instance #1. So 1 + 28 = 29 and the accessible lun DSFs begin at the next available lun 30. And if I add another lun with 4 paths it will likely take up disk31-34 for paths and assign the lun DSF as disk35.

# ioscan -C disk -I 2
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.4.255.0.0.0 disk DGC R AID 5
# ioscan -C disk -I 30
# ioscan -C disk -I 3
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.4.255.0.0.1 disk DGC RAID 5
# ioscan -C disk -I 4
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.4.255.0.0.2 disk DGC RAID 5
# ioscan -C disk -I 5
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.4.255.0.0.3 disk DGC RAID 5
# ioscan -C disk -I 6
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.4.255.0.0.4 disk DGC RAID 5
# ioscan -C disk -I 7
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.4.255.0.0.5 disk DGC RAID 5
# ioscan -C disk -I 8
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.4.255.0.0.6 disk DGC RAID 5
# ioscan -C disk -I 9
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.6.255.0.0.0 disk DGC RAID 5
# ioscan -C disk -I 10
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.6.255.0.0.1 disk DGC RAID 5
# ioscan -C disk -I 11
H/W Path Class Description
===============================================================
0/3/0/0/0/0.105.6.255.0.0.2 disk DGC RAID 5

And so on until disk 29⠦⠦⠦