Do you happen to have the bug number on this, I was about to do lots of Storage vMotion on v3.2.1 and I want to open a support ticket to get some more information. Do you know what release the bug was in? Was it definitely a fix for a combined vMotion/Storage vMotion? This is such a strange bug. Thank you.