I/O errors on file restore
-
@olivierlambert said in I/O errors on file restore:
Hi,
If you have a support subscription (you said XOA Premium, right?), it's better to create a ticket
Yes I do. I could open the ticket there instead. It was not "urgent" so I thought the advise from the community instead.
-
At least it means that the file or the support of the file (the BR/remote under it) got issues to be read
-
@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?
-
I don't see why it could cause that. I'm more thinking about the BR itself.
-
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.
-
I/O error on a sector is usually due to something between your XOA and the BR. It could be many things though.
-
@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.
-
@Forza Did you ever get to the bottom of this? I am experiencing the same issue currently.
-
@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.
-
@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?
-
@chr1st0ph9 Hi, I have not so far. However, I didn't test this again recently.
-
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?
