Please look at my the datastore: datastore1
It shows 40% in filled (550GB+), but I can't find any file in size. This data show empty in my VI client. du also show also 0 size.
Why?
/vmfs/volumes # df
Filesystem Bytes Used Available Use% Mounted on
NFS 2950680141824 44194631680 2906485510144 1% /vmfs/volumes/NAS1
VMFS-5 1494917054464 597961998336 896955056128 40% /vmfs/volumes/datastore1
VMFS-5 491773755392 337140252672 154633502720 69% /vmfs/volumes/ESX35:storage1
vfat 4293591040 20643840 4272947200 0% /vmfs/volumes/4ecea299-dc68e46b-6328-000347def8e0
vfat 261853184 147202048 114651136 56% /vmfs/volumes/Hypervisor1
vfat 261853184 133627904 128225280 51% /vmfs/volumes/Hypervisor2
vfat 299778048 185286656 114491392 62% /vmfs/volumes/Hypervisor3
/vmfs/volumes # du -s /vmfs/volumes/datastore1
0 /vmfs/volumes/datastore1
The VI client is not seeing the correct NFS datastore size, you can correct this by:
1. Waiting until the next time the VI client polls for the datastore size
2. Run the following command on one of the ESX consoles. "service mgmt-vmware restart" (the ESX server will go "grey" and then come back and you'll see the correct datastore size)
Regards,
Milton
This problem has been existing for a few days. Both of the ESXi 5 host and vcenter server have been rebooted several times. So everything had been restarted. It didn't fix the issue.
This is a testing environment. This issue was started after a RAID 1 rebuild. 1 disk was failed, I tried to force bring the failed disk online. After that, the datastore appeared missing some VM which was built recently. I did storage vMotion to move the rest VM to other datastore , because I want to unmount this datastore. But I wasn't able to unmount it, it always report that there is VM existing in the datastore.
Hi,
have you checked what kind of files are there ("ls -la" in datastore1 dir)?
Reg
Christian
Sure. That was the first thing to check.
ls shows there is less than 1GB content in the folder. There suppose to be 500+GB
/vmfs/volumes # cd datastore1
/vmfs/volumes/4c43053e-a5f22d79-c94f-000347def8e0 # ls -al
drwxr-xr-t 1 root root 1400 Feb 19 05:11 .
drwxr-xr-x 1 root root 512 Feb 19 23:02 ..
-r-------- 1 root root 7372800 Jul 18 2010 .fbb.sf
-r-------- 1 root root 63143936 Jul 18 2010 .fdc.sf
-rwxr-xr-x 1 root root 1048576 Feb 11 20:30 .iormstats.sf
drwxr-xr-x 1 root root 420 Feb 19 05:11 .mpx.vmhba2:C0:T0: L0
-r----S--- 1 root root 1179648 Feb 11 20:48 .pb2.sf
-r-------- 1 root root 255655936 Jul 18 2010 .pbc.sf
-r-------- 1 root root 260374528 Jul 18 2010 .sbc.sf
-r-------- 1 root root 4194304 Jul 18 2010 .vh.sf
/vmfs/volumes/4c43053e-a5f22d79-c94f-000347def8e0 #
I wonder about this here:
drwxr-xr-x 1 root root 420 Feb 19 05:11 .mpx.vmhba2:C0:T0: L0
That isn't the right place for that device.
What device is it?
Reg
Christian
This device is the LUN of my datastore1.
Can you see the picture I post here?