ddb.deletable = "false"

[LordofVxRail]

Hello all,

VMware Cloud Director version:

10.3.3.19610595

Is anyone familiar with why or how ddb.deletable = "false" is introduced into vmdk descriptors?

I don't use any backup solutions for my cloud catalog content. This is causing my component use to increase uncontrollably.

[LordofVxRail]

example:

[root@zzzzzzz-01:/vmfs/volumes/vsan:5240c67eca860c22-d23ff1c5d9cda315/37aa7464-4c65-c603-12d6-000af7f6c670] ls -l
total 0
-rw------- 1 root root 611 Jun 3 2023 000_vyos_1677766023-KroT_2-000002.vmdk
-rw------- 1 root root 611 Jan 20 16:41 000_vyos_1677766023-KroT_2-000003.vmdk
-rw------- 1 root root 610 Sep 27 14:08 000_vyos_1677766023-KroT_2-000004.vmdk
-rw------- 1 root root 611 Dec 20 01:58 000_vyos_1677766023-KroT_2-000008.vmdk
[root@zzzzzzz:/vmfs/volumes/vsan:5240c67eca860c22-d23ff1c5d9cda315/37aa7464-4c65-c603-12d6-000af7f6c670] cat 000_vyos_1677766023-KroT_2-000002.vmdk
# Disk DescriptorFile
version=4
encoding="UTF-8"
CID=1fd5a26b
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 33554432 VMFS "vsan://5240c67eca860c22-d23ff1c5d9cda315/c9217664-bedb-200b-bd49-000af7f6c670"

# The Disk Data Base
#DDB

ddb.adapterType = "buslogic"
ddb.deletable = "false"
ddb.geometry.cylinders = "2088"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "801b3620fd266f07291dbe501fd5a26b"
ddb.thinProvisioned = "1"
ddb.toolsInstallType = "4"
ddb.toolsVersion = "11333"
ddb.uuid = "60 00 C2 90 e4 81 34 59-37 f2 98 8a 7a e4 42 85"
ddb.virtualHWVersion = "14"
[root@zzzzzzz:/vmfs/volumes/vsan:5240c67eca860c22-d23ff1c5d9cda315/37aa7464-4c65-c603-12d6-000af7f6c670]

root@zzzzzzzz:/vmfs/volumes/vsan:5240c67eca860c22-d23ff1c5d9cda315/37aa7464-4c65-c603-12d6-000af7f6c670] ls -l
total 0
-rw------- 1 root root 611 Jun 3 2023 000_vyos_1677766023-KroT_2-000002.vmdk
-rw------- 1 root root 611 Jan 20 16:41 000_vyos_1677766023-KroT_2-000003.vmdk
-rw------- 1 root root 610 Sep 27 14:08 000_vyos_1677766023-KroT_2-000004.vmdk
-rw------- 1 root root 611 Dec 20 01:58 000_vyos_1677766023-KroT_2-000008.vmdk
[root@zzzzzzz:/vmfs/volumes/vsan:5240c67eca860c22-d23ff1c5d9cda315/37aa7464-4c65-c603-12d6-000af7f6c670] grep ddb.deletable *
000_vyos_1677766023-KroT_2-000002.vmdk:ddb.deletable = "false"
000_vyos_1677766023-KroT_2-000003.vmdk:ddb.deletable = "false"
000_vyos_1677766023-KroT_2-000004.vmdk:ddb.deletable = "true"
000_vyos_1677766023-KroT_2-000008.vmdk:ddb.deletable = "false"
[root@zzzzzzzz/vmfs/volumes/vsan:5240c67eca860c22-d23ff1c5d9cda315/37aa7464-4c65-c603-12d6-000af7f6c670]

I have literally thousands of these on my vSAN. 

The VM itself "000_vyos_1677766023-KroT" does not exist in the inventory; was deleted long ago.

[LordofVxRail]

Histogram of component health for non-orphaned objects

+-------------------------------------+------------------------------+
| Num Healthy Comps / Total Num Comps | Num objects with such status |
+-------------------------------------+------------------------------+
| 1/1 (OK) | 2455 |
| 3/3 (OK) | 9091 |
| 5/5 (OK) | 1474 |
| 2/2 (OK) | 876 |
| 4/4 (OK) | 4359 |
| 7/7 (OK) | 435 |
| 8/8 (OK) | 417 |
| 9/9 (OK) | 309 |
| 6/6 (OK) | 575 |
| 10/10 (OK) | 266 |
| 11/11 (OK) | 157 |
| 12/12 (OK) | 94 |
| 14/14 (OK) | 8 |
| 13/13 (OK) | 21 |
| 58/58 (OK) | 1 |
| 76/76 (OK) | 1 |
+-------------------------------------+------------------------------+
Total non-orphans: 20539

Histogram of component health for possibly orphaned objects

+-------------------------------------+------------------------------+
| Num Healthy Comps / Total Num Comps | Num objects with such status |
+-------------------------------------+------------------------------+
+-------------------------------------+------------------------------+
Total orphans: 0

Total v15 objects: 20534
/localhost/DC02/computers>

[LordofVxRail]

I have 2103 VMs registered in the inventory.