Cannot expand metaLUN's user capacity

Question

I have a 100GB metaLUN (concatenated) that was created in the past by one of my co-workers and at the time of creation, the meta was not expanded to full capacity to the extent that it was presented to the server with only 50GB usable. I am trying to expand that meta using the following command:
naviseccli -address xxx.xxx.xxx.xxx metalun -modify -metalun x -tomaxcap

The response I'm getting is this:

"This metaLUN is not qualified to increase user capacity. Reason: Selected LU is being used by a feature of the storage system."

Any ideas would be very helpful

Thanks in advance,

Kevin

scn1 · Accepted Answer

navicli -h setfeature -xxxxxxx -off -feature sancopy -lun

Run the navicli -h getlun -xxxxxxx -stack. If K10CpmAdmin is still listed run....

navicli -h setfeature -xxxxxxx -off -feature K10CpmAdmin -lun

xxxxxx = password - contact Support for correct command

Message was edited by: kelleg

EKellerman · Answer

Is one of the meta members currently being used by SnapView, MirrorView or SAN Copy?

scn1 · Answer

naviseccli -address xxx.xxx.xxx.xxx getlun

One of the last things in the list should tell you if has any snaps associated for sure.

There is a hidden command that someone from support can run to dump the driver stack on the LUN to see if any Clone or Snap providers are installed as well. They can then be turned off via navicli.

kwsmith1 · Answer

No... I should have mentioned that at first. I checked all those before I posted and they appear no different than any othe meta except that I can't expand the user capacity.

kwsmith1 · Answer

There aren't any snaps, but I did notice that both the component LUNs that make up this meta are on 0,0,0-4. Could this have any bearing on the situation?

Kiran3 · Answer

There is a hidden command that someone from support

I think its available in many customer primus solutions...so no more hidden

navicli -h getlun -messner -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.

Kiran3 · Answer

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...

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.

kwsmith1 · Answer

That did it....Thanks for all the help!

kwsmith1 · Answer

That got rid of the driver, lets see if I can modify the lun now...... So far so good.

kwsmith1 · Answer

This LUN has driver K10CpmAdmin associated with it so I guess I have to find out how to remove it right? Btw, the array is at Release 19, but the LUN in question isn't a clone that I can find. It doesn't seem as if I have any Clones, Snaps or Mirrors on this array at all.

Thanks for all the help so far.

Kevin

scn1 · Answer

navicli -h setfeature -off -feature K10CpmAdmin -lun I think that will force it off. This driver is the Sancopy driver.

kwsmith1 · Answer

I think the syntax is slightly off. I got this usage error:
usage: setfeature -on|-off {-feature rm|sancopy -lun lun_number|-lunuid uid]

It doesn't seem to have a place to put the driver in that syntax. I'm sure I'm missing something and If you could help clarify it I'd appreciate it.

CLARiiON

Cannot expand metaLUN's user capacity

Was this post helpful?