8 Replies Latest reply on May 6, 2019 12:26 PM by TheBobkin

    Incorrectly sized disk in vm

    bbsawhy Lurker

      I have a vm with 4TB allocated on a secondary disk for a file server. But when I open the VMWare summary, it says that it is occupying 8TB. Here are some examples to illustrate the problem ...

       

      Any solutions?

      vmware.pngvmware2.png

        • 1. Re: Incorrectly sized disk in vm
          Sureshkumar M Expert
          vExpert

          That is because you are using VSAN and Storage policy with  FTT1 (RAID 1, mirrored volume). Since the vmdk is mirrored the actual usage of the disk shows twice than actual size which is expected.

          • 2. Re: Incorrectly sized disk in vm
            bbsawhy Lurker

            I thought about it too, and yes, it's logical. But this situation happens only with this VM. Is it possible that this policy applies only to this VM?

            • 3. Re: Incorrectly sized disk in vm
              bbsawhy Lurker

              I checked the storage policies of this vm and it has the same ones as the others

              • 4. Re: Incorrectly sized disk in vm
                Sureshkumar M Expert
                vExpert

                Other VMs doesnt show double size ? Can you compare this vm with other vm at settings level , there should be some difference .. can you please post the screenshots of storage policy and the VM which was tagged to it not occupying double size. Lets compare and see..

                • 5. Re: Incorrectly sized disk in vm
                  bbsawhy Lurker

                  Screenshots from another VM on the same host, with the same configuration

                  vmware3.pngvmware4.pngvmware5.png

                  • 6. Re: Incorrectly sized disk in vm
                    a.p. Guru
                    vExpertCommunity WarriorsUser Moderators

                    Discussion moved from VMware Server 2 to VMware vSAN

                    • 7. Re: Incorrectly sized disk in vm
                      Sureshkumar M Expert
                      vExpert

                      Strange, adding TheBobkin - vsan expert.

                      • 8. Re: Incorrectly sized disk in vm
                        TheBobkin Virtuoso
                        VMware EmployeesvExpert

                        Hello bbsawhy

                         

                         

                        A hearty welcome to Communities.

                         

                        It's (likely) either:

                         

                        a) proportionalCapacity=100 on the vmdk Object and regardless of the storage policy having OSR=0 it is reserving the space, this is easily identified using RVC:

                        > vsan.vm_object_info <pathToVm>

                        e.g. from root directory (and assuming it is not in a DRS Resource Pool):

                        > vsan.vm_object_info ./localhost/DataCenterName/computers/ClusterName/resourcePools/vms/DMT003

                        or using the vmdk Object:

                        > vsan.object_info <ObjectUUID> ./localhost/DataCenterName/computers/ClusterName

                         

                        Or using objtool or vsan obj health script on any host.

                         

                        Or if using 6.5 U1 or later with esxcli from any host in the cluster:

                        # esxcli vsan debug object list -u <ObjectUUID>

                        or if you don't want to bother getting the vmdk Object UUID then just less the output of this or redirect to a file e.g.:

                        # esxcli vsan debug object list > /tmp/objlist.txt

                        If it is proportionalCapacity=100 then google "proportionalCapacity=100" "TheBobkin" and you will find 11 times on Communities I walked through it

                         

                        b) VM was migrated/created with Thick primitive on the vmdk.

                        There is a Health UI check notifying of this in later builds (think just 6.7 but likely 6.5 U3 also), not positive but the vmdk descriptor may also have thin-provisioned line flag set to 0 indicating this. Cloning from a Thick-provisioned template/VM is another way this can occur. If there is little data on the vmdk (and it can't be vMotioned off vsanDatastore and back) then consider just adding a second disk of same size (and thin ) ,copying the data over within Guest-OS and removing original.

                         

                        c) vmdk is full or was full at some point - vSAN doesn't auto-reclaim used, then freed space within the Guest-OS, TRIM/UNMAP is only available in 6.7 U1 and later - if you are not on 6.7 U1 then consider the options from b) to resolve this.

                         

                         

                        Bob