the results for RVC command "vsan.obj_status_report" showed that there are some unassigned objects. Some of them are relatively easy to identify and resolve, but one object pointed to a directory which contains even recent stats.db -objects. In that directory we have:
vsan.obj_status_report -t .
| Unassociated objects | | |
| a4d61158-7c82-63b6-9409-a0369f7c09b8 | | 3/3 |
Running objtool tells that this is related to stats
/usr/lib/vmware/osfs/bin/objtool getAttr -u a4d61158-7c82-63b6-9409-a0369f7c09b8 | grep -i -E 'name|class|path'
User friendly name:.vsan.stats
Object class: vmnamespace
Object path: /vmfs/volumes/vsan:5220b70abd6996cc-9f2efa8fc8d95916/
In that directory we have:
ls -l a4d61158-7c82-63b6-9409-a0369f7c09b8/
-rw-r--r-- 1 root root 28672 Mar 18 2018 config.db
-rw-rw-rw- 1 root root 0 Oct 27 2016 stats.db.lck
-rw-r--r-- 1 root root 164864 Nov 30 2018 stats.db.tpl
-rw-rw-rw- 1 root root 32130048 Jul 11 12:45 stats.db_345600_4522
-rw-rw-rw- 1 root root 222392 Jul 11 12:45 stats.db_345600_4522-journal
Why this directory is unassigned while there still are recent entries in it? Is there anything to do?
Unassociated doesn't mean unused - it only means that the Object is not associated with a VM currently registered in inventory, which of course a number of things are not e.g. stats Objects, vSAN iSCSI Objects, Content Library Objects etc. .