Yes, when you select the properties of the lun the option to extend to the maximum size appear blocked.

you mean in disk administrator it still shows 204G ?

Is the metaLUN you wish to expand is a part of Snapshot,SnapClone, Mirror View or SAN Copy?

Are you working on Windows Server ?

you can use
navicli -h getlun -xxxxxxx -stack

to see which drivers are associated with the lun in question. if you see any drivers attached (like snapview) but the lun is not a clone or snap then you will have to talk to emc to get that cleaned up.

xxxxxx = password - contact Support for correct command

Message was edited by: kelleg

is this array at pre-release 19? especially Release 16? in some releases you could create meta while the lun was part for clone...or was the code upgraded to R19 later on?

here is the extract from primus that will help you...(incidently, its written off by the person on this thread i guess)

For Release 16 and earlier, if the base LUN that you are expanding is a part of a Clone Group (or a SnapView snapshot or MirrorView mirror), you cannot view the additional space after the operation completes. You will not be prevented from performing the operation.

For Release 19 and later, this operation will fail before you try to see extra space on the host. For example, if you create a clone, and then to try to include it in a metaLUN, Navisphere Release 19 reports the following error:

"You cannot change the LU capacity at this time. Selected LU is being used by a feature of the storage system.
The LUNs you have chosen will be reserved for future growth of this LU."

To work around the issue:

Fracture the Clone Group.
Remove the source LUN from the Clone Group and then create a metaLUN.
Do a rescan disk on the server and then add the source LUN to the Clone Group.

There's another thread with the same quesetion:

http://forums.emc.com/forums/thread.jspa?threadID=49531&tstart=0

Try this thread for instructions for determining if the metaLUN componenet has a layered driver attached.

glenk