I am not sure if this is a VMware question best posted on their forums or a NetApp question best posted here. However, since there are people here that use NetApp with VMware I figured some one would have seen this happen.
We recently attached a 2 TB data store to a VM farm. We started to migrate VM to the store and all went well until the last two were to migrate and they failed with an insufficient space error. We had only moved 500 GB of virtual machines to the store. The admin added 500 more GB to the store and the migrations failed again with the same error. The interesting thing is every machine we were moving were either Windows servers made from a template or a virtual appliance except for the two we are having issues with and they are Linux machines made from scratch.
I shut the VMs down and they vMotioned over correctly but when I attempted to bring them up VMware complained about not enough room and now I cannot vMotion them off of the data store.
Rule Index: 1 Access Protocol: nfs3 List of Client Match Hostnames, IP Addresses, Netgroups, or Domains: 0.0.0.0/0 RO Access Rule: sys RW Access Rule: any User ID To Which Anonymous Users Are Mapped: 65534 Superuser Security Types: any Honor SetUID Bits in SETATTR: true Allow Creation of Devices: true
Have you checked that there is sufficent space within the aggregate that hosts the flexvol on the storage? Is your flexvol volume thin provisioned (IE "space-guarantee = none")? Also what's the snapshot policy applied to the flexvol? If you are taking freqent snapshots whilst you are migrating to the volume you are probably consuming space for snapshots.
Here are some example commands to check the storage configuration:
Our Snap shot policy is the default policy and that is barely filling the volume. I created two more NFS volumes and these same two machines failed to vMotion over to them as well. One of the new volumes had a restricted host list.
I created a new VM the same way these were created and it was able to move between all of the volumes. I believe this is moving more to the VM side of the house than the NetApp side.