On Mon, Jan 02, 2012 at 01:31:56PM +0200, Sami Liedes wrote: > error: Error -3 while decompressing data: incorrect data check
My best guess for this is that Obnam managed to write a partial file to the repository when you interrupted it. This should no longer happen in the current version. > Interestingly, 'obnam verify /home/sliedes/Maildir/.old.nilfs/' > reports "Verify did not find problems.". Hence I'm not sure if this is > actual data loss. This would indicate that at least some of the repository didn't get corrupted. Indeed, it's probably just one or a few files. > One thing that might be indicative that something else is wrong: > Should the uploaded counter of 'obnam backup' stay at 0 on an > incremental backup when nothing has changed in the directory tree? It > doesn't, instead it increases rather quickly to the gigabytes range > when running it on a 14 gigabyte directory tree, which seems excessive > for an incremental backup where there is nothing to do. The upload counter should show only data that's actually been uploaded. I guess that the incremental backup caused more data to be uploaded because of the way the repository got corrupted. I hate to ask you to do this, but: if you try to do this again, does it still happen? -- All my predictions will turn out to be false
signature.asc
Description: Digital signature
