I'm moving some bound volumes between two different thin pools (and backing storage groups) to appease a DBA manager.

I've done a VLUN migration, pinned the volume, confirmed that it completed, then terminated the session.  The name of the LUN still exist as a bound volume in the original thin pool and has 0% allocated, while the same name exists as other pool bond volumes and has 100% allocated.

I was under the impression that the VLUN migration would take the LUN from one thin pool to another thin pool transparently and not leave some residual volume pointer around.

I tried it with another volume in the same thin pool, and did a VLUN migration.  This time, I did not pin the volume, selected the same thin pool (different from the original) and confirmed both from SMC and the SE (using symmigrate) that the migration completed.  When I terminated that session, I don't see that volume in the new thin pool, as a bound volume, or as an other pool bound volume.

Ideas?