-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Backup: Invalid HMAC on verification #1471
Comments
This is possibly related to #1124. |
I think the problem occurs when there is insufficient disk space (on the disk on which How much empty space is required, at minimum, for successful verification? (Just enough to hold the largest VM in the backup? More than that?) |
OK, clearly a lot more space is being used than just the largest VM. Large backup-restore test failed with:
@marmarek, is there any way to specify a location for If not, is there a recommended Linux way to "move" |
Generally it may need as much disk space as the whole backup... But in practice should be much smaller (about 200-300MB). If not, it's a bug. It works this way:
Parts are at most 100MB. So having that parallel extraction, the second one should be quite fast ( Currently there is no way to specify alternative path. You can mount something there (just put it in |
Thanks for that explanation, @marmarek. I did another test, and the results were inconsistent with what I previously reported (same test as before, just excluded a couple of normal-size VMs, and verification succeeded this time even though the same amount of free space was available as before). So, it may be that the issue doesn't actually have anything to do with insufficient disk space. I think it was failing before because the backup was somehow corrupted upon creation, even though I created the backup twice in a row without changing any data. (I remember you saying before that sometimes particularly large backups can have "holes" due to some tar bug...) |
Excluded VMs aren't extracted (also during verification), so it still may be about disk space. |
Sorry, I meant that I excluded them during backup creation (i.e., didn't back them up). |
I just experienced the opposite issue. Verification first succeeded, then failed (and continued failing after many attempts). This is much more serious. Reported as issue #1577. |
Still happens on R3.2, but observed only when creating a large (80+ GB) backup and using compression. After backing up the exact same VMs without compression, verification succeeds. |
This issue is being closed because:
If anyone believes that this issue should be reopened, please let us know in a comment here. |
Since upgrading to R3.0, backup verification occasionally fails with the error message below, but immediately doing a host reboot and reattempting the verification on the same backup file then succeeds.
The text was updated successfully, but these errors were encountered: