I'm under the impression that if disks are added to a thin pool, the data already in the pool is not redistributed across the additional disks.   This is a correct statement for FLARE 28, 30, and OE Block 31 Virtual Provisioning.  is it reasonable to suggest a LUN migration to a new LUN in the same thin pool would redistribute the data out across all the disks?   Its unclear from your statement if 'the same thin' pool has been expanded, or not.  A migration into an 'un-expanded', homogenous (non-FAST VP) pool will result in the data being distributed as evenly as is algorithmically possible across all the available private RAID groups of the pool.  HTH
Stop me if I'm wrong but...  I'm under the impression that if disks are added to a thin pool, the data already in the pool is not redistributed across the additional disks.   Assuming that is accurate: is it reasonable to suggest a LUN migration to a new LUN in the same thin pool would redistribute the data out across all the disks? The end goal is trying to maintain some sense of how many disks the data is actually residing on, ideally that being the number of disks in the pool.  Isn't it fun playing mosaic with LUN's in a maxed out storage array!! [IMAGE][IMAGE]
Clariion FLARE 28 Thin Pool expansion behaviour