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

    VDI_IO_ERROR(Device I/O errors) after resizing a VM's disk

    Scheduled Pinned Locked Moved Backup
    6 Posts 3 Posters 155 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.
    • J Offline
      john205
      last edited by

      Hi,
      I have a CR job that backups a VM. The VM was running low in disk so I resized it up to 100GB from 50GB. Following this resize the backup job for this VM has been failing with Error: VDI_IO_ERROR(Device I/O errors).

      Is this a known or expected issue following a resize? Do I need to setup a new backup replication job for this?

      Thanks,

      John

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

        Hi,

        I think we handled that in regular backup, but maybe this cause an issue with replication. Can you let us know what happens in the next run? Adding @florent in the thread too.

        1 Reply Last reply Reply Quote 0
        • J Offline
          john205
          last edited by

          Woohoo it worked! I updated to latest commit and the backup completed this time. Thanks, and apologies for the noise!

          D 1 Reply Last reply Reply Quote 0
          • D Offline
            DwightHat @john205
            last edited by

            @john205 I am having this issue now as well after this same scenario. I have not been able to fix it. What did you do exactly? @olivierlambert is this a known issue?

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

              I'm not aware of that issue still being… an issue.

              1 Reply Last reply Reply Quote 0
              • J Offline
                john205 @DwightHat
                last edited by

                @DwightHat I am using xoa from sources and i updated it to the latest commit which seemed to fix it for me..

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