VmFileSystem: Slow refresh failed: Unable to get FS Attrs for /vmfs/volumes/60b12569-6bc6e15c-3bc9-2

[tarena1232]

version: esxi 7.0.0 (Build 15843807)

DELL  PowerEdge R7515

ssd 480G *2 RAID1  (ESXI7.0.0)

HDD 4TB (vms)

I use ssh to login the system .I use df -h,it say ：

[root@localhost:/vmfs/volumes/60b12569-6bc6e15c-3bc9-2cea7fa39851] df -h
VmFileSystem: Slow refresh failed: Unable to get FS Attrs for /vmfs/volumes/60b12569-6bc6e15c-3bc9-2cea7fa39851
VmFileSystem: Slow refresh failed: Unable to get FS Attrs for /vmfs/volumes/60b14637-04e9c5d4-5e8a-2cea7fa39851
VmFileSystem: Slow refresh failed: Unable to get FS Attrs for /vmfs/volumes/60b14e42-c5fd9900-4386-2cea7fa39851
VmFileSystem: Slow refresh failed: Unable to get FS Attrs for /vmfs/volumes/60b12569-60d741b8-60e6-2cea7fa39851
Error when running esxcli, return status was: 1
Errors:
Error getting data for filesystem on '/vmfs/volumes/60b12569-6bc6e15c-3bc9-2cea7fa39851': Unable to get FS Attrs for /vmfs/volumes/60b12569-6bc6e15c-3bc9-2cea7fa39851, skipping.
Error getting data for filesystem on '/vmfs/volumes/60b14637-04e9c5d4-5e8a-2cea7fa39851': Unable to get FS Attrs for /vmfs/volumes/60b14637-04e9c5d4-5e8a-2cea7fa39851, skipping.
Error getting data for filesystem on '/vmfs/volumes/60b14e42-c5fd9900-4386-2cea7fa39851': Unable to get FS Attrs for /vmfs/volumes/60b14e42-c5fd9900-4386-2cea7fa39851, skipping.
Error getting data for filesystem on '/vmfs/volumes/60b12569-60d741b8-60e6-2cea7fa39851': Unable to get FS Attrs for /vmfs/volumes/60b12569-60d741b8-60e6-2cea7fa39851, skipping.

But the vms on the Esxi is Ok . what can I do to deal with the problem ? Please help me . Thank you very much .

[Mutadel]

Hello, 

I have the same problem, have you found any solution for this? 

thanks. 

[jonmad]

We have the same problem. I first notice an issue when our Veeam backups fail because they cannot create a snapshot on the affected host. When I do a DF I get the same output. The only resolution so far is to reboot the host, it will then work for another few weeks but ultimately happen again. Happens to the other two hosts in our cluster too. Had tickets in with VMware, Veeam and our SAN storage provider and none of them can figure out the issue.