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

    I/O errors on file restore

    Scheduled Pinned Locked Moved Backup
    14 Posts 4 Posters 611 Views 5 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      At least it means that the file or the support of the file (the BR/remote under it) got issues to be read 😕

      ForzaF 1 Reply Last reply Reply Quote 0
      • ForzaF Online
        Forza @olivierlambert
        last edited by

        @olivierlambert Ticket created. 🙂

        It could be a problem of the backup file. I am attempting a normal restore now to see if the full disk can be restored. Could the issue be related to NBD and multiple blocks transfer?

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

          I don't see why it could cause that. I'm more thinking about the BR itself.

          ForzaF 1 Reply Last reply Reply Quote 0
          • ForzaF Online
            Forza @olivierlambert
            last edited by

            You mean errors on the backup server? I have no error there and have been able to read all files (cat >/dev/null) without issue. The server is using Btrfs with RAID1c3 so it verifies checksums on all reads.

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

              I/O error on a sector is usually due to something between your XOA and the BR. It could be many things though.

              ForzaF 1 Reply Last reply Reply Quote 0
              • ForzaF Online
                Forza @olivierlambert
                last edited by Forza

                @olivierlambert said in I/O errors on file restore:

                I/O error on a sector is usually due to something between your XOA and the BR. It could be many things though.

                I did further testing and found that I can reproduce the issue. While the file-restore dialogue is open, it is possible to access the files via XOA console in /tmp/<xxxx mountpoint>/, but as soon as you press "OK" the access to the disk disappears and all processes trying the mount point freeze. I reported the exact details in the ticket.

                F 1 Reply Last reply Reply Quote 0
                • F Offline
                  flakpyro @Forza
                  last edited by

                  @Forza Did you ever get to the bottom of this? I am experiencing the same issue currently.

                  ForzaF 1 Reply Last reply Reply Quote 0
                  • ForzaF Online
                    Forza @flakpyro
                    last edited by

                    @flakpyro said in I/O errors on file restore:

                    @Forza Did you ever get to the bottom of this? I am experiencing the same issue currently.

                    No. I still have an open support ticket on this.

                    C 1 Reply Last reply Reply Quote 0
                    • C Offline
                      chr1st0ph9 @Forza
                      last edited by

                      @Forza I'm also experiencing the same problem (when trying to restore a file, the machine freezes). To get out of it, I have to restart the XOA service. I'm a bit embarrassed, but did you finally get a solution from support?

                      ForzaF 1 Reply Last reply Reply Quote 0
                      • ForzaF Online
                        Forza @chr1st0ph9
                        last edited by

                        @chr1st0ph9 Hi, I have not so far. However, I didn't test this again recently.

                        1 Reply Last reply Reply Quote 0
                        • ForzaF Online
                          Forza
                          last edited by

                          I re-checked again but the issue is unfortunately not resolved. It does not happen on all VMs and files, so maybe there is something wrong somehow in the VDI?

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