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

    Internal error: Not_found after Vinchin backup

    Scheduled Pinned Locked Moved XCP-ng
    54 Posts 4 Posters 298 Views 2 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.
    • R Offline
      rustylh @olivierlambert
      last edited by

      @olivierlambert I did that on one and noticed a task API call: sr.scan I opened the raw log and seeing errors. AttachedSR Scan Errors.txt

      R 1 Reply Last reply Reply Quote 0
      • R Offline
        rustylh @rustylh
        last edited by

        Is that due to the Master being disconnected from the SR. That is the one I was referring to in my previous Topic post "Pool Master".

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          rustylh @rustylh
          last edited by

          Just keeps bouncing over and over
          a5852bb7-c205-44b7-abc0-1a4094a40f16-image.png

          R 1 Reply Last reply Reply Quote 0
          • R Offline
            rustylh @rustylh
            last edited by

            So even taking Vinchin out of the picture for now, I am still worried that xcp-ng will run the Garbage Collection and disconnect the ST, brining the VM down again.

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

              Ignore the XO tasks panel, it's not important. About the rest, please use it and report if you continue to have issues.

              1 Reply Last reply Reply Quote 0
              • R Offline
                rustylh
                last edited by

                I deleted the snapshot from this one vm.
                ef2e8d88-d35e-4014-9db4-91032fbb9551-image.png

                However, that one remains in the list on here:
                f469155b-9463-4b24-8d75-2dc4d1b72356-image.png

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

                  You can check if coalesce is running if you see that garbage collection is planned on XO/SR view.

                  1 Reply Last reply Reply Quote 0
                  • R Offline
                    rustylh @rustylh
                    last edited by

                    What does this mean exactly? When will this happen? I'm sorry I am very nervous.
                    ba8a70e2-c692-417c-9266-4dbba0aa8799-image.png

                    1 Reply Last reply Reply Quote 0
                    • R Offline
                      rustylh
                      last edited by olivierlambert

                      I don't know if this helps from the SMlog

                      [15:18 iahost-xcpng-server2 ~]# grep -i "coalesce" /var/log/SMlog
Jul  8 14:32:53 iahost-xcpng-server2 SM: [31275] Aborting GC/coalesce
Jul  8 14:33:00 iahost-xcpng-server2 SM: [31789] Entering doesFileHaveOpenHandles with file: /dev/mapper/VG_XenStorage--88d7607c--f807--3b06--6f70--2dcb319d97ea-coalesce_8241ba22--3125--4f45--b3b1--254792a525c7_1
Jul  8 14:33:00 iahost-xcpng-server2 SM: [31789] Entering findRunningProcessOrOpenFile with params: ['/dev/mapper/VG_XenStorage--88d7607c--f807--3b06--6f70--2dcb319d97ea-coalesce_8241ba22--3125--4f45--b3b1--254792a525c7_1', False]
Jul  8 14:33:00 iahost-xcpng-server2 SM: [31789] ['/sbin/dmsetup', 'remove', '/dev/mapper/VG_XenStorage--88d7607c--f807--3b06--6f70--2dcb319d97ea-coalesce_8241ba22--3125--4f45--b3b1--254792a525c7_1']
Jul  8 14:59:34 iahost-xcpng-server2 SMGC: [20458] Coalesced size = 316.035G
Jul  8 14:59:34 iahost-xcpng-server2 SMGC: [20458] Coalesce candidate: *8241ba22[VHD](600.000G//88.477G|n) (tree height 5)
Jul  8 14:59:35 iahost-xcpng-server2 SMGC: [20458] Coalesced size = 316.035G
Jul  8 14:59:35 iahost-xcpng-server2 SMGC: [20458] Coalesce candidate: *8241ba22[VHD](600.000G//88.477G|a) (tree height 5)
Jul  8 14:59:35 iahost-xcpng-server2 SM: [20458] ['/sbin/lvremove', '-f', '/dev/VG_XenStorage-88d7607c-f807-3b06-6f70-2dcb319d97ea/coalesce_8241ba22-3125-4f45-b3b1-254792a525c7_1']
Jul  8 14:59:35 iahost-xcpng-server2 SM: [20458] ['/sbin/dmsetup', 'status', 'VG_XenStorage--88d7607c--f807--3b06--6f70--2dcb319d97ea-coalesce_8241ba22--3125--4f45--b3b1--254792a525c7_1']
Jul  8 14:59:36 iahost-xcpng-server2 SMGC: [20458] Coalesced size = 316.035G
Jul  8 14:59:36 iahost-xcpng-server2 SMGC: [20458] Coalesce candidate: *8241ba22[VHD](600.000G//88.477G|a) (tree height 5)
Jul  8 14:59:36 iahost-xcpng-server2 SM: [20458] ['/sbin/lvcreate', '-n', 'coalesce_8241ba22-3125-4f45-b3b1-254792a525c7_1', '-L', '4', 'VG_XenStorage-88d7607c-f807-3b06-6f70-2dcb319d97ea', '--addtag', 'journaler', '-W', 'n']
Jul  8 15:01:41 iahost-xcpng-server2 SMGC: [20458] Coalesced size = 316.035G
Jul  8 15:02:11 iahost-xcpng-server2 SMGC: [20458]   Running VHD coalesce on *8241ba22[VHD](600.000G//88.477G|a)
Jul  8 15:02:11 iahost-xcpng-server2 SM: [22617] ['/usr/bin/vhd-util', 'coalesce', '--debug', '-n', '/dev/VG_XenStorage-88d7607c-f807-3b06-6f70-2dcb319d97ea/VHD-8241ba22-3125-4f45-b3b1-254792a525c7']
                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        You shouldn't be nervous for a home lab 🙂 You have backups right?

                        It means there's 34 VDIs that will be coalesced in the future. You can check if coalesce is working by looking at that number 34 and checks if it goes down.

                        If it doesn't, check the SM log to understand what's going on. Also, does a SR scan works?

                        R 1 Reply Last reply Reply Quote 0
                        • R Offline
                          rustylh @olivierlambert
                          last edited by

                          @olivierlambert So the count has gone down to 25. The host that all of these servers were on of course disconnected from the SR again. Is there a way to run the Garbage Collection and/or Coalesce on one host only? I was thinking if I move the VMs one at a time over to a host that has nothing else on it I could run that against a powered off VM to clean it up. Then move it to another host and power it back on. Then to the next and next until it's all cleaned up. Does that make sense?

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

                            The number is going down: excellent news! Just be patient now 🙂

                            I would advise just to let it run, trying to outsmart the storage stack almost never works 😄

                            R 2 Replies Last reply Reply Quote 0
                            • R Offline
                              rustylh @olivierlambert
                              last edited by

                              @olivierlambert What entry would I look for to see a successful and/or failed Coalesce? I'm looking at the SMlog.

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

                                Usually "grep -i exception" on /var/log/SMlog will report failures. But as long you see the number going down, it's OK.

                                R 1 Reply Last reply Reply Quote 0
                                • R Offline
                                  rustylh @olivierlambert
                                  last edited by

                                  @olivierlambert Thank you. It's just that the host that some of these VMs are on is disconnecting the SR from the host. So I have been shutting them down and moving them to another host and powering back on. I was just hoping I could finish the coalesce for them manually to prevent unknown downtimes.

                                  1 Reply Last reply Reply Quote 0
                                  • R Offline
                                    rustylh @olivierlambert
                                    last edited by

                                    @olivierlambert Should I not worry about deleting any more of the extra 0B disk listed on the SR page Disks tab and just watch the number on this page?

                                    f26e57d4-d603-466c-9020-968ecb1e13fb-image.png

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

                                      You have a rather long chain now, but it should coalesce anyway 🙂

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