I came across this error after setting up and FlexVolume on a Netapp filer and trying to connect to it from vSphere ESX host.
I had run through the wizard and made sure that each of the ESX hosts had read/write access as well as “Root” access to the export/volume but I continued to get this error:
“Error during the configuration of the host: Cannot open volume: /vmfs/volumes/270c64e8-cae0114b”
Originally I thought it may be that I had underscores in my export name as described in the Vmware KB article. I changed the export name to something without an underscore but still no dice.
It turns out even if you specify Unix security when creating the export, the Netapp filer will create it using NTFS by default! Why it sets the underlying security to NTFS on a NFS export with Unix security is beyond me. It may be the version of OnTap on our old dev filer (184.108.40.206)
To change this you need to do the following:
- Logon to your filer web management interface
- Expand “Volumes”
- Expand “Qtrees”
- Click “Manage”
- Click on the “NTFS” link next to the export you need to change
- Change the security style to “Unix” and then apply
- Go back to your host and try adding the NFS volume
I recommended getting familiar with this Netapp and vSphere best practices document as well.