The other day I was working on a customer VMware vCenter server along with some Netapp storage. The storage being NFS mounted to each ESXi server.
I noticed that the datastore appeared to be read only, i.e. when I browsed the datastore within either the web client or vsphere client, I could not create any new folder or file. However if I logged into an ESXi host via the CLI and tried to create a file or folder within the datastore, I could.
Another test I ran was tried to create a new Virtual Machine, which was successful. So surely the NFS permissions were correct on the storage.
I ran through all the storage settings just to double check the NFS permissions and they were all correct.
I then proceeded to have a look at the vmkernel.log file and saw the following:
8C2B4C36-000000A8-c5] [VpxLRO] -- ERROR task-internal-1676 -- -- vim.FileManager.makeDirectory: vim.fault.CannotCreateFile: --> Result: --> (vim.fault.CannotCreateFile) { --> dynamicType = , --> faultCause = (vmodl.MethodFault) null, --> file = "[datastore1] New Folder", --> msg = "Received SOAP response fault from []: MakeDirectory --> ", --> } --> Args: --> 2016-11-18T15:28:18.457+11:00 [05552 info 'commonvpxLro' opID=4125134] [VpxLRO] -- BEGIN task-internal-1677 -- -- vmodl.query.PropertyCollector.retrieveContents -- ff59bd5c-aee1-7ce0-09e8-19b49ddb1d81(5272807c-a4dc-b3f0-ae5c-1c5ac91f2578
It appears the error is specific to vCenter. I ran a last test which was connect the vSphere client directly to the ESXi host and attempt to create a new file or folder within the datastore. This test was successful.
Looking throught the customer’s setup I found that the same datastores had been mounted twice, once in one vmware cluster and again in another cluster, all running under the same vCenter.
The fix was quite easy, once I unmounted the datastores from the second cluster I could successfully write to the datastore.
The post FileManager.makeDirectory VMware vCenter Error appeared first on SYSADMINTUTORIALS IT TECHNOLOGY BLOG.