If the thin devices in question have allocated tracks from thin pools then after the unbind command completes the system will begin reclaiming the allocated tracks from the thin devices. Once all of the tracks are deallocated from the thin devices they will show as being unbound from the pool. So what you are most likely seeing is the "draining" process of the thin devices.
Hello All.  I have a question/issue.  I have TDEVs in the size of 35gb each, that Iuse to create metas of 68gb, 136gb and 272gb.  They are bound to either ATA or fiber channel.  While I was reclaiming space, I unmapped the metas and ran an unbind.  Then umbner of metas varied. However, they were in excess of 15 for each unbind.  While symconfigure said that the command completed successfully, the device went into Not Ready mode, but tey were still bound to the thin pool. It took over an hour for them to no longer be associated to a thin pool.  An example of the command I used is below:  symconfigure -sid xxx -cmd "unbind tdev 1000:100a from pool ATA_R6_3;" comm  I've done it from the command line and from within Unisphere.  The results were the same, still took over an hour for the dev to be unassociated from the thin pool.  I ran that command before the dissolve and after I unmapped the devices.  These are STD devices.  Any help is appreciated/  Regards,  Nathan
Over an hour to unbind TDEVs