We are currently moving from some Hitachi sans to Compellent. Compellent thin-provisions any volume you create.
We create vm's as the default thick. The problem I have is that if I storage vmotion say a 100gb vm from Volume1 to Volume2 on the Compellent, Volume2 will show the increase Active space, but Volume1 will still have the 100gb reported because thin-provisioning already allocated those blocks.
I do not know of anyway to have esx zero-out a vm on the source after it vmotions, which I assume is the only thing that will fix this issue. And converting to eagerzeroedthick I do not think will help us either.
So anyone with a compellent know the issue I am talking about?
Thanks!