adding space on SAN and dynamically recognized by hp-ux

[Doug_3]

Hi, our system admin is adding 10 gig of space using a xiotech-brocade san unit to an n class. In preparing to add space to our database engine I ran ioscan and vgdisplay to see what was available. However hp-ux does not recognize the new space.

What are the options available for hp-ux to see the new space on the existing hw path?

Regards,
Doug

[Sundar_7 · Accepted solution]

Doug,

After ioscan, execute insf -e to create the device files.

and then you need to pvcreate and add it to the vg. Then vgdisplay will display the available space.

-- Sundar

[Michael Tully]

An ioscan will show the new hardware path, but does not create a device file.

Suggest:

# ioscan -fnk >/tmp/wrk1
# ioscan -fn >/tmp/wrk2

Do a diff on the two files, this will tell if there are any new hardware.

If you recognise a new address, create a device file using insf -e

# insf -e

If this does not work, then there must be an additional procedure needed for the server to see that hardware. CHeck with you SAN dude for this. vgdisplay will not have the new hardware until it has been added by using 'pvcreate' and 'vgextend' to a volume group. See the man pages.

[Con O'Kelly]

Hi Doug

My guess is that if you can't see the new disks through an ioscan then a step has been missed in allocating the space from the SAN.

In the case of adding EMC SAN disks the brocade switich first needs to be zoned and after that the disks allocated to the server using EMC software (Volume Logix). Perhaps one of these steps has been missed or the switch zoning was not done correctly??
I'd check with the SAN admin.

As the others have said once the disks are visible to your server use pvcreate and then allocate them to a volume group using vgcreate or vgextend.

Cheers
Con

[Steven E. Protter]

Might need to use insf -C

It is possible to get HP-UX to recognize the new space without a boot. Its not the same process with all SAN's

SEP

[Ted Buis]

There is also the possibility that you extended an existing LUN, rather than creating a new LUN. LVM won't see that an existing disk suddenly got bigger. One way to do it is create a new LUN, add it to the volume group and then extend the lvols as desired. Hopefully you won't need more PEs than were allowed when you originally set up the VG.