how to map device files.

[aruns_s]

Hi Gurus,

I hv a HP box connected to IBM san storage. Storage team has already created some LUNs and they hv given me the LUN serial numbers. My task is to created a new file systems on the newly created LUNs. My query is how can I map new LUN numbers to device files? Do I need to do an 'insf -e'(I would like to get rid of doing an 'insf -e')? Please advise me the rest of proceedure to create a filesystem on newly created LUNs. Thanks to all

[Steven E. Protter]

Shalom,

Normally for non-hp arrays a reboot is required.

The reboot runs a command called:

insf -C disk

Which might be worth trying to save you the reboot.

pvcreate -f
lvcreate -L
newfs -F vxfs

SEP

[hboo]

Hello!!
Once you have been created disk volumes you must follow the next steps:

In sever: execute ioscan -fnC disk to discover new disks

Execute insf -e to create the new devices

If you require create a physic volume you must do the following thing:

pvcreate /dev/rdsk/cxtxdx to extend a already existing Vg

vgextend /dev/vgxx

vgdisplay /dev/vgxx to verify that the disk is in vgxx

[Sp4admin]

Hi aruns,

When you reboot you will be able to see the new devices. After you have the device path then you can create volume groups and logical volumes, along with your mount points. Use the ioscan -fnC disk to see the new devices, If you don't see them then do "insf -e" but as Steven said above the insf -C disk should run on reboot.

Sp,

[Coolmar]

I had many HP-UX systems attached to IBM SANS and always had to run insf -e in order for the devices to be created. I don't think you can get away from that command. You might be able to then "link" that device to something less cryptic and more condusive to your environment afterwards, if that is what you want to do. Then create your volume groups, logical volumes, and filesystems as per normal.

[Coolmar]

I had many HP-UX systems attached to IBM SANS and always had to run insf -e in order for the devices to be created. I don't think you can get away from that command. You might be able to then "link" that device to something less cryptic and more condusive to your environment afterwards, if that is what you want to do. Then create your volume groups, logical volumes, and filesystems as always.

[Bill Hassell]

You can't get away with not running insf -e -- it is run for you every time the system is rebooted (/sbin/ioinitrc). The -e is a simple way to recreate everything that needs recreating. However, you can manually create the device files with insf by specifying the hardware path (-H) and you can also specify the instance number (-I) to control the device file names.