I don't know if this is a supported procedure but I run into the following

I have a 10GB lun(/dev/sda), partitioned with a NSS pool + volume.

Now I increase the size of the LUN to 15GB on my HP EVA 4000 with Command
View EVA

In order to see the free space on the disk with NSSMU, I'll need to
perform the following command: sfdisk -R /dev/sda.
Now I see the free space on the disk and NSSMU gives me the option to
expand the pool with 5GB.
However the process ends up in an error and the original NSS Pool and
volume remain unreadable. I have to reinit the disk to be able to create a
new NSS Pool.

Now I have a 15GB lun. I partion the lun with NSS to create a 10GB pool +
volume and I want to expand the pool.
I start NSSMU, go to the pool, select F3 and choose the remaining space on
the disk. The process finishes succesfully !! and I end with a 15GB volume.

What is the difference ???
Does NSS somehow only "remember" the initial disk geometry.
Do I have to perform other actions besides sfdisk -R, because this only
rereads the partition table and disk geometry.

Is this the way to expand storage on OES Linux ?
Or do I have to do it the old-school style: adding an extra LUN and span
the pool accross the luns ?