Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

by mistake I created a non-functional NFS datastore on my ESXi. I can see an error in errorlog (wrong target IP).

The thing is, that I don't see this datastore in the list of datastores, so I can't remove it.

Even more, I'm not able to add any other NFS store, as all attempts end with message that the misconfigured one cannot be created :(

Any suggestions?

THX rezna

share|improve this question

migrated from superuser.com Oct 13 '10 at 14:12

This question came from our site for computer enthusiasts and power users.

2 Answers 2

If it is listed in esxcfg-nas -l from the cli you can try to use esxcfg-nfs -d to try and remove it there.

share|improve this answer
    
Keep in mind since this is ESXi not ESX, CLI is not traditionally available. You can use the vCLI tools (vmware.com/support/developer/vcli) to achieve the same thing, but this requires a licensed vSphere setup. esxcfg-nas may be available by enabling SSH access however. –  brent Oct 13 '10 at 14:19
    
I don't see any datastores when I try to --list them :( –  rezna Oct 13 '10 at 14:56
    
what more - i'm not allowed to add datastores using neither esxcfg-nas nor vicfg-nas - fault.RestrictedVersion.summary - but my ESXi is definitely licensed :/ –  rezna Oct 13 '10 at 14:57
    
What license level of ESXi? –  brent Oct 13 '10 at 15:10
    
not sure - the only thing I see is 'vSphere 4 Hypervisor licensed for 2 CPU...' –  rezna Oct 13 '10 at 15:36

Just delete the NFS export, bounce that particular host, recreate and add again.

share|improve this answer
    
'nfs export'? where to find this? –  rezna Oct 13 '10 at 14:34
    
On whatever is exporting the NFS mount to you - a SAN/NAS somewhere I guess - I don't know your environment obviously. –  Chopper3 Oct 13 '10 at 15:00
    
Ah, the problem is not the side of the NFS mount, the problem is at ESXi itself. I by mistake entered 192.168.3.1 as the NFS host (actually my ESXi address) instead of 192.168.3.7 (my NAS address). Now I only get error regarding not being able to connect to 192.168.3.1, and I'm not able to do anything else (like addin other NAS stores) –  rezna Oct 13 '10 at 15:26
    
fine but I'm saying you may have to unexport/reexport the NFS mount plus bounce the host before you get to reenter it properly. –  Chopper3 Oct 13 '10 at 17:03

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.