XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Storage Bar Graph Misinformation

    Scheduled Pinned Locked Moved Unsolved Xen Orchestra
    9 Posts 4 Posters 413 Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T Offline
      tony
      last edited by tony

      Hello, anyone have this problem or is it just my configuration?

      0ead63ab-7fe2-4829-ad23-4182d010906e-image.png

      The number says 200 GiB free, which should be around 20% free, but the graph clearly shows more than 50% free.

      P P 2 Replies Last reply Reply Quote 0
      • P Offline
        ph7 @tony
        last edited by

        @tony
        I have somewhat same issue in XCP-ng and XO.
        https://xcp-ng.org/forum/topic/9695/weird-storage-size-reporting
        But no response in the forum.

        1 Reply Last reply Reply Quote 0
        • P Offline
          peder @tony
          last edited by peder

          @tony Is your storage thick or thin provisioned, if you click on the Advanced tab?
          If it's a thin storage it could be that the amount "used" is the disk size you've specified when creating the VMs and the bar represents the actual number of GBs used right now.

          T 1 Reply Last reply Reply Quote 0
          • T Offline
            tony @peder
            last edited by

            @peder The bar is correct I think, after adding all the disk allocated I get 450 GiB, but the number 715.95 GiB used is incorrect. I can't figure out where does this number come from, may be it also counts backups? But I don't store backups on this nfs share.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              The 715GiB used measure the total space used on the NFS share. You should have a similar number in the Dom0 if you enter df -h.

              T 1 Reply Last reply Reply Quote 0
              • T Offline
                tony @olivierlambert
                last edited by

                @olivierlambert Thank you for replying, it is indeed what the NFS share reports as free, but why there is such a discrepancy in NFS file size and actual VM disk size? Is it to do with VDI coalescing?

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by olivierlambert

                  It's because you have other stuff in that NFS share, "outside" the SR itself. The SR is a folder on an existing share, and that NFS share is presenting the total size, which is not related to only what's inside the SR but the whole size.

                  T 1 Reply Last reply Reply Quote 1
                  • T Offline
                    tony @olivierlambert
                    last edited by

                    @olivierlambert But for my case, I have nothing else in that NFS share except XCP-ng VHDs (single SR folder with nothing outside it). For my case (currently) I checked du -h on my NFS share and I get 572G and df -h shows about the same usage 572.1G. If I add total allocated disk space from all VMs using this NFS share, it is only 450G, so this means there are 100G+ of file system usage (from snapshots?).

                    I can now understand what the numbers represents (the actual physical disk usage not VM disk usage) but the bar graph still doesn't show the same thing. So just to clarify, does the bar graph actually show VM disk usage and not physical disk usage?

                    1 Reply Last reply Reply Quote 0
                    • T Offline
                      tony
                      last edited by

                      I have another weird one. The numeric representative is correct, but the bar graph is unintuitive.

                      aa347240-cb22-4cde-acb0-ac741e44151a-image.png

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post