You could create another TDEV and make a concatenated meta volume to expand it.  It is also dependent on the host O/S as to whether or not it can pick up on that extra space.  I do not believe that you can make a TDEV larger once created.

Per the "Solutions Enabler Array Control Guide" - Table 11..

Touches on Meta but not non-meta

Expand a thin meta = A bound striped metadevice cannot be expanded.

An unbound striped or concatenated metadevice can be expanded; however,

the new meta member must be unbound. As part of the expansion process, the

new metamember will be bound to the same thin pool. The

protect_data option is not supported

Very Good...

Not sure why I didn't see that primus

Can't do it online and there's a few steps, but there's an option.

I think I'll start off with Meta TDEV's so this won't pose a problem in the future if we suspect a lun may require expansion in the future...

Thanks

Could you provide details?

I tried using SMC, but it wouldn't allow me to extend a meta unless it was already created as a Meta?

I'm new to TDEV's so it's likely I'm missing a step...

Thanks

I don’t think you can migrate within the same pool

If the TDEV is already in use by the host would Virtual LUN Migration be a better option?

Bummer. Hopefully that is something they plan on fixing...

Did they fixed this with VMAX 3?

Can a regular VMAX TDEV (not meta) is expandable?

There is no device expansion available on the VMAX3 yet.