Whilst working on issues with VMotion and slow ll listing of /vmfs/volumes I have noticed some discrepencies on what should be static VMFS volumes. When I say static, I mean that the volume contains metadata, a heartbeat region and a Virtual machine disk file. Basically the VMFS volume is using more space then I can account to it; the volume below lists as 50.750GB in VC, working back from a vdf operation this volume size matches up on the host.
When I ll -lah on the volume I get the following for the root of the volume and the VM folder;
drwxrwxrwt 1 root root 1.1K Oct 12 23:56 .
drwxrwxrwx 1 root root 512 Oct 29 10:52 ..
1 root root 896K Oct 12 15:16 .fbb.sf
1 root root 62M Oct 12 15:16 .fdc.sf
1 root root 244M Oct 12 15:16 .pbc.sf
drwxr-xr-x 1 root root 560 Oct 12 23:56 RESVPWMINT01
1 root root 248M Oct 12 15:16 .sbc.sf
1 root root 4.0M Oct 12 15:16 .vh.sf
From the VM folder also;
drwxr-xr-x 1 root root 560 Oct 12 23:56 .
drwxrwxrwt 1 root root 1.1K Oct 12 23:56 ..
-rw------- 1 root root 50G Oct 18 04:57 RESVPWMINT01-flat.vmdk
-rw------- 1 root root 345 Oct 16 20:26 RESVPWMINT01.vmdk
Rounding all those files that are listed below 1M to 1M and adding the values together equals 50.565GB, which therefore by my rekoning means the volume should have 0.185GBs free space available to it.
The problem for me is that the volume is only reporting as having 1M free space, which is unfortunate - as VMFS needs between 4M and 5M for journalling operations.
What is using this space?
The heartbeat region is represented above i assume by the file vh.sf
The Metadata by the files, fbb.sf, fdc.sf,pbc.sf & sbc.sf
The Virtual machine hard disk is the files -flat.vmdk and *.vmdk.
There is nothing else listed on the volume, so again what is utilising the space?
The fact that these volume is reporting as full is undoutabably what is causing the issues with VMotion and the slow processing of VDF and an 'll' from /vmfs/volumes.
Another concern for me is that I can see this descrepency on all of the volumes presented from the SAN to the hosts, less volume space reported as usable then what should be.
I'd really appreciated it if somebody could take the time to compare the free space listed on a SAN attached LUN from a vdf operation, with the files that make up the volume. For clarification, I'd like to see a LUN that only contains VMDK files and does not house virtual machine VMX or VSWP etc.
First two posters to attach/copy the requested output will be awarded helpful points.