NFS: Unable to create datastore: The specified key, name, or identifier already exists.

Summary:
I have a shared NFS datastore mapped to all my hosts.  So I found it strange that two hosts in a cluster of 5 were not seeing it.  When I would try to map it, I would get the following error:
Unable to create datastore: The specified key, name, or identifier already exists.

This worked for me:
It seems I had an old mapping in place that wasn't showing up in vCenter until I refreshed the storage view to show the 'inactive' mount:
Once the inactive mount appeared, I was able to unmount it, then remount the correct path.
[If the refresh doesn't work, you may need to SSH to the host and run the ESXCLI commands listed toward the bottom of the post]

I found it interesting in that running "vicfg-nas <a bunch of connection options here> --vihost myesxserver -l" did not list this inactive path either.  It might have shown up if I connected directly to the ESXi host w/ the vSphere client, but I did not check.

ESXi 5, you'll need to use the esxcli commands like so:
esxcli storage nfs list

 esxcli storage nfs remove -v nameOfDatastoreVolume

Comments

Anonymous said…
Interesting. Let me know if you believe this is a bug and I'll ask the appropriate resource(s) to check into it.

And congrats on vExpert recognition again for 2013.

~Steve Sieczko
June 3, 2013 at 1:48 PM
Unknown said…
As an additional note, I could not see this "ghost" unmounted datastore from the vSphere web client, but I could see it from the desktop infrastructure client.
August 13, 2014 at 10:28 AM
Unknown said…
As an additional note, I could not see this "ghost" NFS datastore from the vSphere web client, but I could see it from the desktop infrastructure client as shown in this post.
August 13, 2014 at 10:30 AM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more