-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed snapshot due to interrupted system call
#702
Comments
The root cause seems to be the same as in restic/restic#2659 |
It appears that the fix is in Go 1.16. Other than waiting for that, is there much we can do? |
Dunno, maybe adding wrappers in the mean time that we would undo once 1.16 is out. 1.16 is ~2.5 months out. |
Not sure, but this issue may (or may not) also affect reading files from kopia snapshots mounted via FUSE. Needs investigation. |
Go 1.16 beta1 is coming out soon. It may be a good idea to test whether this particular issue is resolved with a custom build of kopia. |
This should be fixed with #842 |
Re-opening until it is fully verified. |
cc: @pavannd1 |
@julio-lopez can this be closed now? |
Backing up a directory in an Azure Files volume (mounted via SMB/CIFS) fails due to
interrupted system cal
Currently trying to narrow down which specific sys call.
cc: @bathina2
The text was updated successfully, but these errors were encountered: