RESIZED Lun from EVA to HP UNIX

[ManojK_1]

Hi,

We are using HP Unix 11.23 and the server is connected to EVA8000.

From EVA 9 Lun's are presented to the HP Unix Servers. From that 8 of the lun's are using for ASM (ORACLE) as raw disk and one lun is using for FileSystem.

Now we want to increase the size of lun's from 200GB to 300GB for one of the lun's using for ASM and Filesystem.

From EVA it is possible to resize the existing LUN. What about HP Unix Servers?

How i can able to get the new lunsize 300GB in HP Unix servers?

We don't want to present any extra lun to the server as the sanp clone is having some limitations regarding the maximum number of lun's?

Manoj K

[Steven E. Protter]

Shalom,

Best bet is to present larger LUNS and migrate the the data.

You may have to do it one LUN at a time if you don't have the space.

That is the best way. Increasing them in place works sometimes with HP provided EVA/MSA disk, sometimes does not.

I would schedule some downtime and see how an increase works. If it is not recognized, go for the new LUN idea.

SEP

[Emil Velez]

see this vgmodify white paper

It works great.. Just be very very careful

[Basheer_2]

Emily attachment has all the information.

after changing the LUN size to 300GB

you can verify the size by
diskinfo /dev/rdsk/c#t#d#

If you dont want to take vgmodify route. Then you can do this online

I have done this for filesystem NOT for the ASM
1) create a new lun 300GB (atleast for the filesystem) on the EVA
2) ioscan
3) insf -e -C disk
4) diskinfo /dev/rdsk/c#t#d#
5) pvcreate /dev/rdsk/c#t#d#
6) vgextend /dev/dsk/c#t#d# vgname
7) mirror the exiting lvol to the new disk lvextend -m 1
8) after it is done
9) break the mirror form the old lun lvextend -m 0
10) vgreduce the old-lun (200GB)
11) delete this lun from eva
12) rmsf the dev files for the old lun

[ManojK_1]

Hi All,

Thanks for the support.

We have achived the same for the RAW Disks which is configured in ASM (ORACLE).

The only problem with the Lun extension is we have to stop the ASM (Complte Database) because after only stopping the ASM OS is recogonizing the NEW size of lun.

Then we were started the ASM and run the following command and it is worked fine with out any data lose.

ALTER DISKGROUP RESIZE DISK SIZE 300G;

For file system we are not at all able to extend the size in lvm after OS recogonized the new size also.

Manoj K

[ManojK_1]

I am closing the thread as per the above given details.