VC 2 datastore display issue

mldmld · ‎09-12-2007

All,

We are running VC 2.0 (VMware-vpx-2.0.2-50618).

One of the datastore is a NFS share, it's called "drivers".

It is declared to all our ESX servers.

If we browse this datastore from a server in VC, the share appears empty.

However it displays the total size and the free space in the datastore list.

If we connect using VI Client to a ESX server directly (it is managed by VC). One can see the contents of "drivers".

If we try, using the ssh access, one can see the contents of the NFS share in /vmfs/volumes/drivers

So why VC can't display the contents.

We reboot the VC server without success.

We tried to remove the drivers datastore, then reconnect it to an ESX using VC without more success.

Thanks for any help

Regards

ML

masaki · ‎09-12-2007

Is the NFS share configured as written in the manual?

is there the no_root_squash option enabled?

You could not have all necessary rights to browse the datastore.

What kind o file system? ext3?

mldmld · ‎09-13-2007

Hi,

The netapp equivalent of no_root_squash is anon=0 in the /etc/exports file.

filer1> rdfile /etc/exports

#Auto-generated by setup Tue May 24 11:42:53 CEST 2005

/vol/vol0 -sec=sys,rw,anon=0,nosuid

drivers is a qtree undel vol0

Here is the errors shown in VC log in C:\WINDOWS\Temp\vpx\

2007-09-13 11:16:18.469 'App' 4968 info] \[VpxLRO] -- FINISH task-internal-54 -- datacenter-2 -- vim.Datastore.GetSummary

\[2007-09-13 11:16:18.484 'App' 3596 info] \[VpxLRO] -- BEGIN task-internal-55 -- datacenter-2 -- vim.ManagedEntity.GetEffectiveRole

\[2007-09-13 11:16:18.500 'App' 3596 info] \[VpxLRO] -- FINISH task-internal-55 -- datacenter-2 -- vim.ManagedEntity.GetEffectiveRole

\[2007-09-13 11:16:18.844 'App' 4304 info] \[VpxLRO] -- BEGIN session\[0D16F95E-14DB-4D22-A134-0AB15BBD930C]BE32D593-74F3-4ECC-87A3-9FCD1E140A98 -- datacenter-2 -- vim.host.DatastoreBrowser.search

\[2007-09-13 11:16:20.219 'App' 4304 error] GetResult failed: not well-formed (invalid token)

\[2007-09-13 11:16:20.219 'App' 4304 warning] ============BEGIN FAILED METHOD CALL DUMP============

\[2007-09-13 11:16:20.219 'App' 4304 warning] Invoking \[searchDatastore] on \[vpxapi.VpxaService:vpxa]

\[2007-09-13 11:16:20.250 'App' 4304 warning] Arg url:

"netfs://10.231.226.3//vol/vol0/drivers/"

\[2007-09-13 11:16:20.250 'App' 4304 warning] Arg recursive:

false

\[2007-09-13 11:16:20.250 'App' 4304 warning] Arg spec:

(vim.host.DatastoreBrowser.SearchSpec) {

dynamicType = ,

fileType = true,

fileSize = true,

modification = true,

},

searchCaseInsensitive = true,

sortFoldersFirst = true,

}

\[2007-09-13 11:16:20.250 'App' 4304 warning] Fault has an empty message

\[2007-09-13 11:16:20.250 'App' 4304 warning] ============END FAILED METHOD CALL DUMP============

\[2007-09-13 11:16:20.328 'App' 4304 info] \[VpxLRO] -- FINISH session\[0D16F95E-14DB-4D22-A134-0AB15BBD930C]BE32D593-74F3-4ECC-87A3-9FCD1E140A98 -- datacenter-2 -- vim.host.DatastoreBrowser.search

\[2007-09-13 11:16:20.437 'App' 5884 info] \[VpxLRO] -- BEGIN task-internal-56 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:20.437 'App' 5884 info] \[VpxLRO] -- FINISH task-internal-56 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.031 'App' 6108 info] \[VpxLRO] -- BEGIN task-internal-57 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.047 'App' 6108 info] \[VpxLRO] -- FINISH task-internal-57 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.062 'App' 5268 info] \[VpxLRO] -- BEGIN task-internal-58 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.062 'App' 5268 info] \[VpxLRO] -- FINISH task-internal-58 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.062 'App' 3988 info] \[VpxLRO] -- BEGIN task-internal-59 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.062 'App' 3988 info] \[VpxLRO] -- FINISH task-internal-59 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.078 'App' 4408 info] \[VpxLRO] -- BEGIN task-internal-60 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.094 'App' 4408 info] \[VpxLRO] -- FINISH task-internal-60 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.109 'App' 1132 info] \[VpxLRO] -- BEGIN task-internal-61 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.109 'App' 1132 info] \[VpxLRO] -- FINISH task-internal-61 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.141 'App' 4920 info] \[VpxLRO] -- BEGIN task-internal-62 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.141 'App' 4920 info] \[VpxLRO] -- FINISH task-internal-62 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.250 'App' 3860 info] \[VpxLRO] -- BEGIN task-internal-63 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.250 'App' 3860 info] \[VpxLRO] -- FINISH task-internal-63 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.281 'App' 3812 info] \[VpxLRO] -- BEGIN task-internal-64 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:31.281 'App' 3812 info] \[VpxLRO] -- FINISH task-internal-64 -- -- vmodl.query.PropertyCollector.Filter.destroy

\[2007-09-13 11:16:35.984 'App' 1464 info] *** UserData destructor called: %s

\[2007-09-13 11:16:40.812 'App' 4348 info] \[VpxLRO] -- BEGIN task-internal-65 -- host-143 -- VpxdInvtHostSyncHostLRO.Synchronize

\[2007-09-13 11:16:40.812 'App' 4348 info] \[VpxdHostSync] Synchronizing host: intel01.labtech.pls.renault.fr (10.231.226.19)

\[2007-09-13 11:16:42.000 'App' 4348 info] \[VpxdHostSync] Retrieved host update to 16860

\[2007-09-13 11:16:42.094 'App' 4348 info] \[VpxdHostSync] Completed host synchronization

\[2007-09-13 11:16:42.094 'App' 4348 info] \[VpxLRO] -- FINISH task-internal-65 -- host-143 -- VpxdInvtHostSyncHostLRO.Synchronize

[u]But, from the ESX server it works. The log /var/log/vmware/hostd says :[/b][/u]

\[2007-09-13 11:27:39.670 'DatastoreBrowser' 5901232 verbose] filer1.labtech.pls.renault.fr:/vol/vol0/drivers-datastorebrowser::GetDatastore

\[2007-09-13 11:27:41.129 'DatastoreBrowser' 3076477056 verbose] filer1.labtech.pls.renault.fr:/vol/vol0/drivers-datastorebrowser::GetDatastore

\[2007-09-13 11:27:42.447 'DatastoreBrowser' 7228336 verbose] filer1.labtech.pls.renault.fr:/vol/vol0/drivers-datastorebrowser::Search Path = \[drivers] / Spec = (vim.host.DatastoreBrowser.SearchSpec) {

dynamicType = ,

dynamicProperty = (vmodl.DynamicProperty) [],

path = "a_supprimer",

fileSize = 4096,

modification = "2007-09-12T14:34:33+02:00"

And, to proove the root access from an ESX :

\[root@blade1-1 root]# cd /vmfs/volumes/drivers/

\[root@blade1-1 drivers]# chown bin:bin Hahaha

\[root@blade1-1 drivers]# ll

\[...]

-rw-rr 1 bin bin 0 Sep 13 10:44 Hahaha

\[...]

\[root@blade1-1 drivers]# rm Hahaha

rm: remove regular empty file `Hahaha'? y

\[root@blade1-1 drivers]# ll Hahaha

ls: Hahaha: No such file or directory

Thanks for your help

Best regards

ML

MikeTedescucci · ‎10-03-2007

Hello,

I am seeing this issue as well. All of a sudden I am not able to browse one of my datastores from any of my hosts through VI Client. If I SSH into the host I can do whatever I need to do. Has this been resolved?

Mike

kevio · ‎10-23-2007

I have also encountered this issue. this was after I added a ESX 3.0.2 server into the VC2 cluster.

Does anyone have a resolution?

Kevio

kdamak · ‎10-23-2007

As a first I would try to restart all the agents before getting into any in depth troubleshooting...

service mgmt-vmware restart

service vmware-vpxa restart

--restart the Virtual Center Server service from the Virtal Center Server --

Ensure you have not modified the default VM power on options otherwise it may restart your virtual machines.

Elgo · ‎10-31-2007

Hi,

I worked with mldmld on this problem.

In fact, it seems that one of our ESX servers was causing troubles in VC, despite the fact that we removed it from the managed servers in VC some times ago.

After trying to reinsert this particular ESX server in VC (we didn't know then he was the source of our problem), we saw an error message (as far as I remember, it said no more than a really explicit "internal error"). As we further investigate in this ESX linux/vmware logs, we saw that it complained about the vpxuser user being already existing.

After manually removing this user on the problematic ESX, we successfully re-added it to VC pool and.... we were able to browse the datastore again.

I have no explanation for this, neither does VMware support...

kdamak · ‎10-31-2007

That is a very interesting observation re: vpxuser account.

Another way which would probably fix this would be to run the agent uninstall script from the Virtual Center Server.

C:\Program Files\VMware\VMware VirtualCenter 2.0\upgrade

Copy the uninstall file corresponding to the build of the agents on the host

- rpm -qa | grep -i vpx

Run the uninstall script

sh vpx-uninstall-esx-6-linux-61426

To install the agents again you can just add the host back into VC, or run the install script corresponding to build of your Virtual Center Server.

Christian_Lager · ‎11-05-2007

I had exactly the same fault but on SAN.... When connecting to the host via SSH or via the VI client everything was OK. When connecting via VC I couldn't browse storage devices...

I solved the problem by creating one new DataCenter and then use "drag and drop" to move one ESX host after another to the new Datacenter. After each move I tried to browse one storage device. When it stoped working i knew which host that had the problem. Removed it and continued until all hosts was moved. Then i reinstalled the faulty hosts. (I had one....)

Good luck!

Regards

/Christian Lagerhorn

paagc · ‎12-11-2007

Hello,

I had the same problem and i finally discover why. I have done many tests, client installations, VC instalation, Services for UNIX, etc, etc.

Finally i discover a folder name SSD´s was causing the problem. I then remove the (´) from the name SSDs and voilá!!! problem solve.

Thanks

AHandtmann · ‎12-11-2007

Hi paagc!

Do you have any wishes for christmas? Thanks to your post I resolved this issue without reinstalling ESX or VC - I was searching for a solution quite some time and didn´t find any other reasonable hint to this topic (and still don´t believe that an ESX reinstall would resolve this issue).

THANKS!

Best regards,

Arne

P.S.: Did you submit this as a bug report to VMWare yet?