Panic after 2 days into backup #710
Comments
|
Huh, thanks for reporting this. It seems to be indeed a duplicate of #367, and I haven't found the underlying bug yet. What happens is that restic regularly uploads partial indexes which contain the IDs of uploaded blobs (parts of files). The bug is that somehow restic tries to add a blob ID to an index which is already in the process of uploading (=finalized). You can just restart your backup, restic will find most already uploaded data blobs, so it should be much faster. I'm going to close this as a duplicate of #367 for now. |
|
No problem, I guess next I'll see how robust restic's backup restart capabilities are. :) I know you've got a lot on your plate. (As a fellow Go OSS dev, I do too, I get it.) I wish I could just dive in and fix it right now. What are your near-term priorities for the project? Is fixing this one of them? Right now I'm realllly trying to avoid installing Duplicity because dependencies are a pain and lack of dedup is a little rough. I figure I can get away with a |
|
Yes, fixing this is one of my near-term goals. But I won't give any estimates. I'll have more time in January and February. |
Output of
restic versionrestic 0.3.2 (v0.3.2-4-gb0997d0)
compiled with go1.7.4 on linux/arm
Expected behavior
No panic.
Actual behavior
Steps to reproduce the behavior
No idea, sorry. Backup was about 2 days in and this morning it had panicked.
Dang, I was really hoping to switch from Duplicity, because installing Duplicity is a pain. The static builds are really appealing. And actually, I'm loving this program a lot, the deduplication is wonderful.
For what it's worth, the command was:
I was just backing up from one local hard drive to another one plugged into the same machine.
The output of
dmesgdoesn't have much to say; there are a few of these at the end:but IIRC they were there before the panic -- yes in fact now I'm sure they were -- so I'm not sure if it's related. Let me know what you need that might be helpful.
This was the whole output, unfortunately, although repository/index.go:104 seems to be about trying to add a file to an index that's already finalized?
Here's the output of
restic check:I should also ask about my options here. It says I can use
rebuild-indexto fix some of the errors, then can I also runrestic backupto continue/fix the backup and see if it will resume?(Edit: I just found #367 which this might be the same bug.)
The text was updated successfully, but these errors were encountered: