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

    Unhealthy VDI's

    Scheduled Pinned Locked Moved Backup
    5 Posts 3 Posters 288 Views 3 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.
    • D Offline
      Dude417
      last edited by

      I don't know if this is related to the "Snapshots not being removed after successful backup" issue that I posted a couple weeks ago.... but it seems like maybe it is.

      I seem to be getting a bunch of "Unhealthy VDI's" ...and they are using up my storage space...
      Any safe easy way to clean these all out ???

      I can remove the leftover snapshots without issue....but I'm unsure how to proceed with cleaning up these VDI's ???

      f894f610-ac3f-4eec-bcea-877c8b1c50e3-image.png

      1 Reply Last reply Reply Quote 0
      • D Offline
        Dude417
        last edited by

        Never mind.... seems to have been something "stuck".

        As soon as I deleted a couple of the VDI's..... everything took off and cleaned it self up.

        P 1 Reply Last reply Reply Quote 0
        • P Offline
          probain @Dude417
          last edited by

          Unless you have thin provisioning. The garbage collection won't happen automatically. Or at least, not nearly often enough (imho). Instead it is only triggered when snapshots/VDIs are deleted.

          IMHO, automatic scanning and garbage collection should happen regardless if the proviosioning is thin or thick. But that is only my two cents.

          1 Reply Last reply Reply Quote 0
          • D Offline
            Dude417
            last edited by

            I have 2 other standalone XCP hosts...that do not exhibit the same symptoms.
            Both are running older versions of XO.
            The oldest has zero cleanup problems at all.
            It's running commit 902f0

            the 2nd is running commit 992d6 and seems to leave some snapshots behind.... but doesn't exhibit the VDI issue.

            commit 290f5 looks like it may be the issue.

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

              You shouldn't run anything other than the last commit as possible (which is de934ec609b1bfb48cd598de8b096a6b4cf1f963 now).

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