Unable to access file ds error while creating VM on NFS datastore created using 7 mode volume

[coral vigil]

Hi Team,

We have created volume on 7Mode NetApp storage.

Using this volume NFS datastore is created on VMware.

Now when we try to use this datastore e.g Deploy vm ,we are getting error :

Unable to access file ds:///vmfs/volumes/f3eb1e20-e042a3bc/New Virtual Machine

When we create NFS Datastore by qtree and try to deploy vm on it it works smoothly.

Please confirm on priority , is it mandatory to create qtree on volume to use datastore ?

OR any additional settings required to make NFS datastore using volume usable ?

Thanks in advance.

Posted same question in community :
https://community.netapp.com/t5/ONTAP-Discussions/Unable-to-access-file-ds-error-while-creating-VM-on-NFS-datastore-created-using/m-p/446319

Regards,

Priyanka Adsul

Technology Lead Quality Assurance

Cumulus-Systems

Please provide inputs asap.

[slim saddle]

How are your export policies configured on NetApp? Qtree are not mandatory

[brittle gorge]

your export needs root rights... please share the output of the exportfs command.
Also, 7mode is really old by now, consider using something that still has support 🙂

[coral vigil]

Netapp-pune1> exportfs
/vol/vol1/marsbuild -sec=sys,rw=192.168.10.12:192.168.20.43:192.168.20.138:1 92.168.20.142:192.168.20.135
/vol/lun_20_246_vol -sec=sys,rw,nosuid
/vol/vol_NFS_QA1 -sec=sys,rw,nosuid
/vol/vol_prededup -sec=sys,rw,nosuid
/vol/san1 -sec=sys,rw,nosuid
/vol/UCS_Datastore1_vol -sec=sys,rw,nosuid
/vol/quota_volume -sec=sys,rw,nosuid
/vol/vol0/home -sec=sys,rw,nosuid
/vol/vol0 -sec=sys,rw,anon=0,nosuid
/vol/vol_NFS_QA -sec=sys,rw,nosuid
/vol/san1/qtree_nfs -sec=sys,rw
/vol/vol1 -sec=sys,rw,root=192.168.20.5,nosuid
/vol/vol2 -sec=sys,rw,nosuid
/qtree3 -actual=/vol/vol1/qtree3,sec=sys,rw
/vol/vol_postdedup -sec=sys,rw,nosuid
/vol/NFSTest1 -sec=sys,rw,nosuid
/vol/delete_vol_2 -sec=sys,rw,nosuid
/vol/vol1/testnfs -sec=sys,rw
/vol/sas1 -sec=sys,rw,nosuid
/vol/UCS_Datastore1_vol/ora_rac -sec=sys,rw=192.168.100.50:192.168.100.49,nosuid
/vol/NFSTest -sec=sys,rw,nosuid
/vol/corp_share -sec=sys,rw,nosuid
Netapp-pune1>

[brittle gorge]

oh wow. "anon=0" on vol0, which is exported to the world...

anyway, I guess you need to disable root squashing on the exports: the root=... flag for the export security... (see man na_exports for the parameter. to make sure that's the issue though, check the security style of your volume and qtree. It should be unix, not NTFS

[coral vigil]

/vol/vol_NFS_QA -sec=sys,rw,nosuid => We have created datastore using this volume and VM deployment failed for the same.

Please suggest anything need to be change for this volume ?

[brittle gorge]

please share the security style of the volumes (qtree status I think? both for the volume(s) and the qtree within). Also, please share which export (mount point) works, and which doesn't, in the list above

[coral vigil]

qtree is not created for this volume

[brittle gorge]

please show the security style of the volume. the command to show security style is qtree status

[coral vigil]

/vol/vol_NFS_QA1 -sec=sys,rw,nosuid => This mount path works

/vol/vol_NFS_QA -sec=sys,rw,nosuid =>Not worked

[coral vigil]

PFA command outputs.

[slim saddle]

Is there an fpolicy on place? The default blocks VM files for NFS.

[brittle gorge]

I'm confused. This is supposed to be an NFS datastore, however, there are LUNs in it? But yeah, it's not the security style that's the problem. Also not the export rule...

[slim saddle]

@brittle gorge that's why I thought of a fpolicy. Have seen it once at a customer.

[coral vigil]

Hello Team, We have checked fpolicy details, but no policy configured on our storage.

[coral vigil]

We have tried to mount datastore just by creating volume too. Datastore is not accessible. What could be issue?