Deactivated state of a data device (thin pool source device)

you would deactivate data devices if you want to disable any new writes to it. For example if you want to remove certain data device from a pool you would deactivate it first, start draining it. So while it's being drained application can still read from it but not write to it. This used to be the technique to rebalance virtual pool whenever you add new devices but on the new code there is a automated pool rebalance option so you don't have to manually deactivate/drain/re-enable.

Thanks for the helpful reply....

It means that if we directly start draining(copying tracks to other enabled devices) on enabled devices, then at that time applications may write the data parallely while draining?

Also, rebalancing is the operation which is there on the enabled devices only of the pool. So how the deactivate operation comes into the picture here as deactivate is a disabled device?

Thanks,

yes, application write  i/o on thin device. but not on the deactive data device.

after draining you can remove device from pool.

all the way you cannot remove active device from pool.

Thanks boom. It would really help.

Ya thats true but deactivate state of a data device comes into the picture for SYMCLI 7.1 only.

In case of SYMCLI 7.0 where there is not any state like deactivate, when we give the command to disable the enabled data device, and when it changes the state from Enabled to Draining (just before Disabled state would come), then while the data device is in draining state (in case of SYMCI 7.0), then whether it is possible for an application on a thin device which was initially taking space from this data device to write on the thin device now when the corresponding data device is in DRAINING state.

Thanks,