We have many CX4 arrays and some of them have more space than required and some don't have enough. To meet the need I am trying to migrate the data from certain DAEs to another Thin pool: Example: FC_Pool to SATA_Pool or vise versa.

This has happened occasionally and wondering if this is a software issue.  When I have a thin lun on say the SATA pool and I create a new thin lun (of the same size) on the FC pool and initiate a migration, sometimes it works, sometimes it doesn't.

What I mean is, even though the migration says it has completed, and though the SATA pool says it's empy, the new thin lun that was migrated says it is still attached to the SATA pool, not the FC pool where I moved it to.  This normally happens on the last 2 or 3 thin luns from the current pool that I am migrating over to the new pool.  These are CX4-240s with Flare 4.30 version and all have licensing from EMC.

I can see that the pool says none of it's capacity is used, but again, the thin lun says it is still attached to that pool.  I definitely do not want to delete the pool with that sort of error with a chance of blowing up a production lun.

Anyone ever had that issue?  Sometimes I can clear it out by performing the lun migration several times and sometimes, as was the last attempt, the lun never said it was attached to the correct pool.  To fix this, I had to create a new FC thin lun, attach it to the host and have the admin copy the data over on the OS before I could actually delete the SATA thin lun and be sure that no luns were left on the SATA pool.

Thoughts?