I referenced this in an earlier post, but we continue to have datastore alarm problems on hosts running 4.0U2 connected to a 4.1 vCenter. In some cases, the timestamp on the datastore does not update, so it’s not just the alarm having a problem but also the datastore timestamp. As a stopgap measure, we scheduled a little PowerCLI script to automatically run to ensure all of the datastores are refreshed. We then accelerated our upgrade plans to quickly eliminate the problem from our primary datacenter. We now only have it in our DR site, so it’s not critical anymore, just annoying.
if ( (Get-PSSnapin -Name VMware.VimAutomation.Core -ErrorAction SilentlyContinue) -eq $null ) { Add-PsSnapin VMware.VimAutomation.Core } Connect-VIServer yourserver.foo.com $ds = Get-Datastore foreach ( $dst in $ds ) { $dsv = $dst | Get-View Write-Host "Refreshing "$dsv.Name $dsv.RefreshDatastore() } |
Alex
Same problem under vCenter 6 here.
pkremer
Unfortunately, I don’t know. The issue resolved itself when we upgraded the hosts from 4.0U2 to 4.1 and I haven’t seen anything like this since. I never saw an official KB article about it or anything, the claim about it being a known bug came from VMware support.
Anders Olsson
I have two customers experiencing this on vSphere 5.0 U1/U2.
Anders Olsson
Nice workaround, but has anybody gotten the root problem solved by VMware?