> vsan.obj_status_report ~vsan
2017-06-13 08:16:08 +0000: Querying all VMs on vSAN ...
2017-06-13 08:16:08 +0000: Querying all objects in the system from XXXXXXXXXXXXXX ...
2017-06-13 08:16:09 +0000: Querying all disks in the system from XXXXXXXXXXXXXX ...
2017-06-13 08:16:10 +0000: Querying all components in the system from XXXXXXXXXXXXXX ...
2017-06-13 08:16:10 +0000: Querying all object versions in the system ...
2017-06-13 08:16:14 +0000: Got all the info, computing table ...
Histogram of component health for non-orphaned objects
+-------------------------------------+------------------------------+
| Num Healthy Comps / Total Num Comps | Num objects with such status |
+-------------------------------------+------------------------------+
| 3/3 (OK) | 269 |
| 16/16 (OK) | 1 |
| 10/10 (OK) | 2 |
| 4/4 (OK) | 1 |
| 18/18 (OK) | 1 |
| 12/12 (OK) | 1 |
+-------------------------------------+------------------------------+
Total non-orphans: 275
Histogram of component health for possibly orphaned objects
+-------------------------------------+------------------------------+
| Num Healthy Comps / Total Num Comps | Num objects with such status |
+-------------------------------------+------------------------------+
+-------------------------------------+------------------------------+
Total orphans: 0
Total v1 objects: 0
Total v2 objects: 0
Total v2.5 objects: 0
Total v3 objects: 144
Total v5 objects: 131
Hello,
Unfortunately I don't think you can find this using vsan.obj_status_report
You could pull all the info for all Objects using vsan.vm_object_info <path to VMs>* (e.g. from the cluster-level ./resourcePool/vms/* this is assuming they are not in resource pools)
Then copy out all this info and trim/manipulate it so that it takes the following relevant data out:
- DOM Object UUID
- Object-version ( e.g. v3)
- Disk-Backing (e.g. [vsanDatastore] 2cfcc657-1234-5678-9123-1402db6a123/VMName.vmdk
I made you a small script to identify the UUIDs of all Objects of a specific version:
Find UUIDs of all v3 Objects:
#cmmds-tool find -f python | grep -A5 -B5 DOM_OBJECT | grep -A5 'objectVersion\\\": 3' | grep 'uuid' | awk -F\" '{print $4}'
Find UUIDs of all v5 Objects:
#cmmds-tool find -f python | grep -A5 -B5 DOM_OBJECT | grep -A5 'objectVersion\\\": 5' | grep 'uuid' | awk -F\" '{print $4}'
I have been attempting to combine this with a loop to run these UUIDs through objtool so that that it dispays the friendly-name of the Object ( e.g. while read i; do /usr/lib/vmware/osfs/bin/objtool getAttr --bypassDom -u $i; done ) but it is failing to parse the UUIDs so maybe some otherscript manipulation needs to be done which you could try.
Bob
-o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-
Hello,
Unfortunately I don't think you can find this using vsan.obj_status_report
You could pull all the info for all Objects using vsan.vm_object_info <path to VMs>* (e.g. from the cluster-level ./resourcePool/vms/* this is assuming they are not in resource pools)
Then copy out all this info and trim/manipulate it so that it takes the following relevant data out:
- DOM Object UUID
- Object-version ( e.g. v3)
- Disk-Backing (e.g. [vsanDatastore] 2cfcc657-1234-5678-9123-1402db6a123/VMName.vmdk
I made you a small script to identify the UUIDs of all Objects of a specific version:
Find UUIDs of all v3 Objects:
#cmmds-tool find -f python | grep -A5 -B5 DOM_OBJECT | grep -A5 'objectVersion\\\": 3' | grep 'uuid' | awk -F\" '{print $4}'
Find UUIDs of all v5 Objects:
#cmmds-tool find -f python | grep -A5 -B5 DOM_OBJECT | grep -A5 'objectVersion\\\": 5' | grep 'uuid' | awk -F\" '{print $4}'
I have been attempting to combine this with a loop to run these UUIDs through objtool so that that it dispays the friendly-name of the Object ( e.g. while read i; do /usr/lib/vmware/osfs/bin/objtool getAttr --bypassDom -u $i; done ) but it is failing to parse the UUIDs so maybe some otherscript manipulation needs to be done which you could try.
Bob
-o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-
Hi, Bob!
Thank you!
I was surprised to find that there are no objects of version 3, and objects are version 4! How could this happen?
{
"uuid": "a0175344-bfd2-47ff-c8ac-70e2840d9e88",
"owner": "5745b6b9-d5d2-73d7-2bfd-70e2840da18a",
"health": "Healthy",
"revision": "12",
"type": "DOM_OBJECT",
"flag": "2",
"minHostVersion": "3",
"md5sum": "5a5d9c3d304d3540e402e3cfd40487a9",
"valueLen": "1656",
"content": "{\"type\": \"Configuration\", \"attributes\": {\"CSN\": 232, \"SCSN\": 237, \"addressSpace\": 273804165120, \"scrubStartTime\": 1146296224824125, \"objectVersion\": 4, \"highestDiskVersion\": 5, \"muxGroup\": 1278324228022896, \"groupUuid\": \"a0175344-bfd2-47ff-c8ac-70e2840d9e88\", \"compositeUuid\": \"a0175344-bfd2-47ff-c8ac-70e2840d9e88\", \"objClass\": 2}, \"child-1\": {\"type\": \"RAID_1\", \"attributes\": {\"scope\": 3}, \"child-1\": {\"type\": \"Component\", \"attributes\": {\"capacity\": [0, 273804165120], \"addressSpace\": 273804165120, \"componentState\": 5, \"componentStateTS\": 1495773877, \"faultDomainId\": \"574da762-529d-0413-2107-70e2840d9e04\", \"lastScrubbedOffset\": 346357760, \"subFaultDomainId\": \"574da762-529d-0413-2107-70e2840d9e04\", \"objClass\": 2}, \"componentUuid\": \"f841e358-f2bf-437e-e031-70e2840e0f20\", \"diskUuid\": \"526718d1-5405-d3e5-28de-b22c46952c14\"}, \"child-2\": {\"type\": \"Component\", \"attributes\": {\"capacity\": [0, 273804165120], \"addressSpace\": 273804165120, \"componentState\": 5, \"componentStateTS\": 1495774062, \"faultDomainId\": \"57d04aff-5c84-aa0e-6548-70e2840e0f20\", \"lastScrubbedOffset\": 346357760, \"subFaultDomainId\": \"57d04aff-5c84-aa0e-6548-70e2840e0f20\", \"objClass\": 2}, \"componentUuid\": \"42c52259-30ef-b6ef-6916-70e2840d9e90\", \"diskUuid\": \"528b0962-c606-a2ca-c351-73c691265095\"}}, \"child-2\": {\"type\": \"Witness\", \"attributes\": {\"componentState\": 5, \"componentStateTS\": 1496989886, \"isWitness\": 1, \"faultDomainId\": \"57a76c06-0a38-c90c-85bf-70e2840d9cc6\", \"subFaultDomainId\": \"57a76c06-0a38-c90c-85bf-70e2840d9cc6\"}, \"componentUuid\": \"80c52259-bca0-3b2d-0afc-70e2840d9e90\", \"diskUuid\": \"52cd2542-094e-6fd0-d5d6-4c16815a3201\"}}",
Hello Emily,
Apologies for the confusion there, "objectVersion": 4 in cmmds-tool view of Object corresponds to what shows as "v3" Objects in RVC, so this is expected.
Are all of your disks/disk-groups on v5 on-disk format?
Was there some issue with the Object upgrade process and if so, can you try run this again and/or provide any error messages or alerts relating to why all Objects were not formatted to v5?
Do the v3 objects have anything in common such as are they all .vswp Objects and/or are they the only Objectsz that existed prior to on-disk upgrade?
Bob
-o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-
Yes, all disks/disk-groups on v5.
The update was interrupted by an error. The disks were updated and half of the objects were updated.
The refresh is interrupted by an error.
Objects of version 3 are as diverse as objects of version 5.
