Unbind a dev

Yeah sorry I failed to mention that. Need to run a quick symdev not_ready on the device before unmapping it. This is all why that -unmap parameter is so great

Run a "symcfg show -pool -thin -detail -gb -sid "

The -detail is important as otherwise the TDEVs wont be shown. If the device is no longer in the bound device list it is correctly unbound. If the unbind completely succesfully it will be unbound, but that is a way to check to be sure. You can also do a symdev show on the device and look for the Bound Thin Pool Name line. If nothing is there it is unbound.

Okay if i do that, the unbind storage will adds to that pool

The meta remains configured. If you want to dissolve the meta you must do it manually after the unbind operation.

Do i need to dissolve Meta dev or when i unbind the dev from pool meta will automatically dissolves ?

Firstly, You dont need to delete the masking view unless you want to reclaim all devices in the view, you can just remove the devices in question from the storage group.

2. Before you unbind the device it needs to be unmapped from the FA's, you need to specify the -unmap options in CLI or check the Unmap option in SMC when you remove devices form SG.

3. After the devices are unmapped, you need to unbind them from the pool, after unbinding the devices will show as not ready.

4. Then you need to break the Meta's

5. Finally you can delete the devices and the space is reclaimed...

To be clear the device is reclaimed as soon as you unbind the TDEV--you do not need to delete the device to reclaim the space from the thin pool. For thick/standard devices only is the capacity released only upon the deletion of the device.

My process for deleting a device is:

1. Remove from storage group with symsg -sg remove dev XXXX
2. Set to not ready with symdev not_ready XXXX
3. Unmap with symconfigure -cmd "unmap dev XXXX from dir all:all;" commit (do a preview first)
4. Unbind with symconfigure -cmd "unbind tdev XXXX from pool ;" commit (again, do preview first)
5. Dissolve the meta with symconfigure -cmd "dissolve meta dev XXXX;" commit
6. Delete the devices with symconfigure -cmd "delete dev XXXX:YYYY;" commit

If you need to see the device range for the delete command run symdev list -noport

The process changes a little if this is the last device in a storage group but other than that I've not had problems following this process.

You can either look at the symapi log for the command history (c:\program files\emc\symapi\log is the default location in windows) or you can run this command against the array to check:

symaudit -sid list -v -start_date xx/xx/xxxx

I have unmapped from ports. Unfortunately i have noted the ports. How can i check the ports after unmapped is there any way.

Here is my case.

I have deleted masking view long back. Today i start removing devices from storage group. Below is the process i use

symdev -sid 64 not_ready -dev 091B

unmap dev 091B from dir all:all;

symaccess -sid 64 -name BACKUPVG1_CLONES_SG -type stor remove dev 091B

unbind tdev 091B from pool PROD_SATA7k;

dissolve meta dev 091B;

delete dev 091B:091F

after prepare i use commit

Check the symapi log, or the symaudit log. Should tell you which ports you had unmapped it from

You say you used "symconfigure -sid 64 -cmd "unmap dev 0867 from dir all:all;" -nop prepare".  This command will not actually unmap anything; it will check the syntax of the command and see if there are any problems running it.  To actually unmap this device you need to change "prepare" to "commit":

symconfigure -sid 64 -cmd "unmap dev 0867 from dir all:all;" -nop commit

I used symconfigure -sid 64 -cmd "unmap dev 0867 from dir all:all;" -nop prepare