https://community.emc.com/thread/117240

everything that was mentioned in that thread applies to thin devices.

Thanks for the link.

I saw this very precisely, but most of the parts re descriped on normal devices not thin devices. Little eloboration on thin device will definitely help me to understand better...

If thin device was created as concatenated meta - yes, you can expand with no imact by adding new thin device to exiting meta. If thin device was created as stripped - you still can expand it with no impact, but procedure is a lot more difficult and requires creation of BCV device with exact geometry. If thin device was created as single device - you would have to turn it into meta, by creating meta out of existing thin device and new second device. This procedure however will require downtime as single thin device would have to be unmasked\unmapped.

How it helps.Max.

if it is on current microcode you can turn a single thin device into a meta now without having to unmap it.

i am on 5875.198 and can't do it ..what version are you on Robert ?

yep, i am doing the same thing only from the cli ( 7.3.1) ...this is interesting.

I just did this on 5875 198 148 code.

Create thin device and assign to server.

Create another thin device; do not bind to a pool.

used the create FBA meta in SMC and picked first device as meta head and second device to be added as a concatenated meta volume.  Previewed successfully and then commited it to be sure.

The device you are adding to the meta is not bound to a pool right.  Our version of SYMCLI is also 7.3.1

not bound , I’ll create another device and try again.