Shared NFS3 datastore - thin provision problem

[adartu]

We have a problem when trying to clone or import a VM using a NFS 3 shared datasore. Even though thin provision is selected from Web UI when importing/cloning, the VM will have storage type "Thick provision eager zeroed". It is true for vSphere UI and for ESXi UI also. If the VM is created from scratch, the disk will be Thin Provisioned, as expected. If we use a VMDK datastore for importing/cloning, the disk will be Thin Provisioned.

Versions:

vSphere Web Client: Version 6.7.0.20000 Build 10244845

ESXi version: 6.7.0

[daphnissov]

What type of storage is this and have you installed the NFS VAAI plug-in for this storage?

[adartu]

Correcting the post above: If we use a VMDK VMFS 5 datastore for importing/cloning, the disk will be Thin Provisioned.

[daphnissov]

Ok, you're confusing me. Your thread title says "NFS". Your last couple sentences say the same thing:  importing a VM is thin provisioned. Why don't you try this one more time?

[adartu]

So, when you try to import or clone a VM on a NFS 3 Shared Datastore using Thin Provisioning, the created VM will have hardisk type: "Thick provision lazy zeroed". If you try the same thing on a VMFS 5 datastore, the resulting VM will have hardisk type: "Thin provision", so in this case it is ok.

[daphnissov]

Ok, so back to my first response which you didn't answer.

What type of storage is this and have you installed the NFS VAAI plug-in for this storage?