Error Message when cloning VM on a cDOT 8.1 NFS Datastore

[GREGOR_STOEK]

Hi Community,

we get the following error message when trying to clone a VM on a Cluster-Mode NFS Datastore:

Relocate virtual machine xxxxx Could not complete network copy for file /vmfs/volumes/7163b10b-094a869d/xxxxx/xxxxx (bb22951b-dda8-40cb-a27f-383b3c8-fc93c) Copying Virtual Machine files xxxxxxxxx  11.11.2013 09:17:12 11.11.2013 09:17:12 11.11.2013 09:17:13

Clone virtual machine TPL-WIN2k8R2 (52adf066-b3ec-4183-9752-ec45622ada4c) Could not complete network copy for file /vmfs/volumes/990cbd44-705e5083/TPL-WIN2k8R2 (52adf066-b3ec-4183-9752-ec45622ada4c)/TPL-WIN2k8R2 (52adf066-b3ec-4183-9752-ec45622ada4c)-000001.vmdk Copying Virtual Machine files xxxx\xxxxxxxxxxx    xxxxt 11.11.2013 14:16:51 11.11.2013 14:16:51 11.11.2013 14:16:52

Doing the same on a 7-Mode Metro-Cluster is working fine.

Anybody an idea?

THX a lot

Gregor

[ADVUNIBN1]

We get the same error with the following components when we try to do a Clone or Storage Migration:

Netapp cDOT 8.2.P4

ESXi 5.5 Build 1623387

NFS VAAI Plugin 1.21

We recognized if the vstorage (VAAI) option on the vserver is disabled Clone and StoragevMotion works in traditional way (Netzwork copy):

vserver nfs modify -vserver <name> -vstorage enable

We get NO error with the following components when we try to do a Clone or Storage Migration (SIS clones and xcopy Migration!) in our Lab:

Netapp cDOT 8.2.1RC2

ESXi 5.5 Build 1623387

NFS VAAI Plugin 1.21

Our Idea is that 8.2P6 perhaps fix the issue, but we found nothing in Bug Comparison...

Did you solve the issue??

Regards Benny

[ALAN_HARRINGTON]

any update or ideas?

we started have this issue shortly after going to 8.2.1p1.

we had to disable vaai as a work around, planning on opening a support ticket with netapp.

[ADVUNIBN1]

Please have a look here:

https://kb.netapp.com/support/index?page=content&id=1014234&locale=en_US&access=s

We resolved the issue by changing the export-policy for the root volume...

[ALAN_HARRINGTON]

Odd, it was working for a bit before it started working, however after following the guideline you are posted we are back!!

Thank you very much for the quick response

alan

[Daren]

This fixed my problem also. Came down to VAAI and the requirement for NFS4 calls.