VMware Cloud Community
brainslice
Enthusiast
Enthusiast
Jump to solution

cannot remove NFS datastore

I noticed that there is a duplicate nfs datastore showing up on one of my ESX hosts. When I try to delete the dastore the VI client throws an error saying "The object has already been deleted or has not been completely created" Also, I can browse the duplicate datastore just fine. Tried restarting vcenter and that did nothing.

Reply
0 Kudos
1 Solution

Accepted Solutions
lamw
Community Manager
Community Manager
Jump to solution

vCenter gets its information from the ESX host, I assume you've tried to refresh the storage view?

You could try to refresh the datastore information from ESX and see if that information propagate to vCenter, try to do both:

[root@himalaya ~]# vmware-vim-cmd hostsvc/datastore/refresh <datastore_name>

If that still does not work, a quick fix is to restart the management agent on the ESX host by doing:

service mgmt-vmware restart 

this should force an update and the storage information should be correct afterwards.

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

View solution in original post

Reply
0 Kudos
7 Replies
brainslice
Enthusiast
Enthusiast
Jump to solution

Just logged into the ESX host directly with vSphere client and the duplicate datastore does not show up there. It's only showing when logging into vCenter and viewing that host's storage tab.

Reply
0 Kudos
lamw
Community Manager
Community Manager
Jump to solution

vCenter gets its information from the ESX host, I assume you've tried to refresh the storage view?

You could try to refresh the datastore information from ESX and see if that information propagate to vCenter, try to do both:

[root@himalaya ~]# vmware-vim-cmd hostsvc/datastore/refresh <datastore_name>

If that still does not work, a quick fix is to restart the management agent on the ESX host by doing:

service mgmt-vmware restart 

this should force an update and the storage information should be correct afterwards.

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

Reply
0 Kudos
brainslice
Enthusiast
Enthusiast
Jump to solution

Had to do the service mgmt-vmware restart. Refreshing the datastores in vSphere client and on the esx host did nothing.

Thank you for the fix.

Reply
0 Kudos
gbil
Contributor
Contributor
Jump to solution

I had a similar issue with a local datastore on ESXi 4 and based on your suggestion I did

/usr/sbin/services.sh restart

and it worked.

Thanks for the help

Reply
0 Kudos
mdri
Enthusiast
Enthusiast
Jump to solution

In addition to the problem of not removing an NFS datastore, I have the problem of the ESX host reporting it properly, but vCenter reports two. For example, I create a datastore named NFS1. In vCenter, two entries appear: NFS1 and NFS1 (1). Is is because some hosts list one name in their storage tab where others report the other name.

Executing the esxcfg-nas -l command on all hosts list only NFS1 as expected. This is true for both 3.5 hosts and 4.0 hosts. The hosts know the real deal, but vCenter 4.0 doesn't.

Another example. When I add the NFS datastore with a different name, such as MYNFSDS, it appears with this name on the host as expected, but vCenter lists the new datastore as NFS1 (1).

Restarting services resolves the issue for a time on an individual host, but the problem returns. And with eight hosts, having one actual NFS datastore presented as two different names in vCenter is problematic for many reasons. One is that vCenter users create VMs on datastore NFS1 and other users create VMs on datastore NFS1 (1)-- they just choose the name listed in the choice of datastores. Once that occurs, I lose the administrative ability to clean this up by restarting services as this causes VMs to disconnect from vCenter because their files can't be located.

What explains the inconsistency between datastore names on hosts vs. vCenter? Why does the (1) appear in vCenter only, and how can this be prevented?

Reply
0 Kudos
zmrok
Contributor
Contributor
Jump to solution

i'm agree. it's fix problem

Reply
0 Kudos
jkdiaz
Contributor
Contributor
Jump to solution

Yep resolved my issue as well. Had to reconnect host but it did resolve that issue.

Thanks,

Reply
0 Kudos