How can see correct space usage with RVC

[baber]

I have created a policy with FTT=1 and object space reservation = 50%
now I created a vm with 90G disk and 4G memory I just want see really object reservation reserve space or not . So I connect with rvc and run follow command but usage for vmdk and swap is 0 why ? I thought usage for vmdk have to show 45G and for swap 2G . what happend?  "This is just a vm without os and data"

/lvcsa/LDatacenter/computers/Standard Cluster> vsan.vm_object_info hosts/lhost6.opr.dsa/vms/thin/.
VM thin:
  Disk backing:
    [vsanDatastore (1)] 80219660-557a-9b7f-06d5-005056aecea2/thin.vmdk

  [vsanDatastore (1)] 80219660-557a-9b7f-06d5-005056aecea2/thin.vmx
    DOM Object: 80219660-557a-9b7f-06d5-005056aecea2 (v14, owner: lhost6.opr.dsa, proxy owner: None, policy: stripeWidth = 1, cacheReservation = 0, proportionalCapacity = [0, 100], hostFailuresToTolerate = 1, forceProvisioning = 0, spbmProfileId = fdfbe7b4-e3e2-452f-9e31-d8f7f8583370, spbmProfileGenerationNumber = 1, replicaPreference = Performance, iopsLimit = 0, checksumDisabled = 0, CSN = 3, spbmProfileName = Ftt=1 - thin)
      RAID_1
        Component: 80219660-90bd-8a80-b9af-005056aecea2 (state: ACTIVE (5), host: lhost6.opr.dsa, capacity: mpx.vmhba1:C0:T4:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                         votes: 1, usage: 0.1 GB, proxy component: false)
        Component: 80219660-3e91-8e80-5cad-005056aecea2 (state: ACTIVE (5), host: lhost5.opr.dsa, capacity: mpx.vmhba1:C0:T2:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                         votes: 1, usage: 0.1 GB, proxy component: false)
      Witness: 80219660-4fdf-9180-42a0-005056aecea2 (state: ACTIVE (5), host: lhost3.opr.dsa, capacity: mpx.vmhba1:C0:T2:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                     votes: 1, usage: 0.0 GB, proxy component: false)

  [vsanDatastore (1)] 80219660-557a-9b7f-06d5-005056aecea2/thin.vmdk
    DOM Object: 80219660-5985-770c-584f-005056aecea2 (v14, owner: lhost6.opr.dsa, proxy owner: None, policy: stripeWidth = 1, cacheReservation = 0, proportionalCapacity = 50, hostFailuresToTolerate = 1, forceProvisioning = 0, spbmProfileId = fdfbe7b4-e3e2-452f-9e31-d8f7f8583370, spbmProfileGenerationNumber = 1, replicaPreference = Performance, iopsLimit = 0, checksumDisabled = 0, CSN = 4, spbmProfileName = Ftt=1 - thin)
      RAID_1
        Component: 80219660-a857-1e0d-b921-005056aecea2 (state: ACTIVE (5), host: lhost5.opr.dsa, capacity: mpx.vmhba1:C0:T4:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                         votes: 1, usage: 0.0 GB, proxy component: false)
        Component: 80219660-06fd-210d-890c-005056aecea2 (state: ACTIVE (5), host: lhost4.opr.dsa, capacity: mpx.vmhba1:C0:T3:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                         votes: 1, usage: 0.0 GB, proxy component: false)
      Witness: 80219660-c12a-250d-0716-005056aecea2 (state: ACTIVE (5), host: lhost3.opr.dsa, capacity: mpx.vmhba1:C0:T2:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                     votes: 1, usage: 0.0 GB, proxy component: false)

  [vsanDatastore (1)] 80219660-557a-9b7f-06d5-005056aecea2/thin-196511e7.vswp
    DOM Object: b4219660-81ed-8fa0-7f48-005056aedd34 (v14, owner: lhost6.opr.dsa, proxy owner: None, policy: stripeWidth = 1, cacheReservation = 0, proportionalCapacity = 50, hostFailuresToTolerate = 1, forceProvisioning = 1, spbmProfileId = fdfbe7b4-e3e2-452f-9e31-d8f7f8583370, spbmProfileGenerationNumber = 1, replicaPreference = Performance, iopsLimit = 0, checksumDisabled = 0, CSN = 2, spbmProfileName = Ftt=1 - thin)
      RAID_1
        Component: b4219660-d29c-89a1-829e-005056aedd34 (state: ACTIVE (5), host: lhost3.opr.dsa, capacity: mpx.vmhba1:C0:T2:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                         votes: 1, usage: 0.0 GB, proxy component: false)
        Component: b4219660-9f1d-8fa1-047a-005056aedd34 (state: ACTIVE (5), host: lhost5.opr.dsa, capacity: mpx.vmhba1:C0:T3:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                         votes: 1, usage: 0.0 GB, proxy component: false)
      Witness: b4219660-0833-91a1-c3cb-005056aedd34 (state: ACTIVE (5), host: lhost4.opr.dsa, capacity: mpx.vmhba1:C0:T4:L0, cache: mpx.vmhba1:C0:T1:L0,
                                                     votes: 1, usage: 0.0 GB, proxy component: false)

[TheBobkin]

@baber, Firstly, there isn't really much point in using anything other than 0% or 100% OSR.

My guess is that you haven't properly applied the Storage Policy (SP) to that Object or that it isn't being applied - can you try with an OSR=100 SP? Looks fine when checked just now:

You can also see the % Reserved by all Thick data via vsan.disks_stats <pathToCluster>:

But IMO the best way of viewing this is via 'esxcli vsan debug object list' (either using the --vm-name=Test123 or -u and the vmdk Object UUID) as this shows a nice layout for comparison of the reserved space per component (Capacity Used) vs how much of that it has actually physically written (Physical Capacity Used):