{"action":"created","issue":{"url":"https://api.github.com/repos/restic/restic/issues/604","repository_url":"https://api.github.com/repos/restic/restic","labels_url":"https://api.github.com/repos/restic/restic/issues/604/labels{/name}","comments_url":"https://api.github.com/repos/restic/restic/issues/604/comments","events_url":"https://api.github.com/repos/restic/restic/issues/604/events","html_url":"https://github.com/restic/restic/issues/604","id":174953620,"number":604,"title":"Nil blob list errors, zeroed files in backup","user":{"login":"zcalusic","id":12140851,"avatar_url":"https://avatars.githubusercontent.com/u/12140851?v=3","gravatar_id":"","url":"https://api.github.com/users/zcalusic","html_url":"https://github.com/zcalusic","followers_url":"https://api.github.com/users/zcalusic/followers","following_url":"https://api.github.com/users/zcalusic/following{/other_user}","gists_url":"https://api.github.com/users/zcalusic/gists{/gist_id}","starred_url":"https://api.github.com/users/zcalusic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zcalusic/subscriptions","organizations_url":"https://api.github.com/users/zcalusic/orgs","repos_url":"https://api.github.com/users/zcalusic/repos","events_url":"https://api.github.com/users/zcalusic/events{/privacy}","received_events_url":"https://api.github.com/users/zcalusic/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-04T15:14:40Z","updated_at":"2016-09-04T15:18:46Z","closed_at":null,"body":"restic 0.2.0 (v0.2.0-202-gfae65eb)\r\ncompiled at 2016-09-04 10:30:20 with go1.7\r\n\r\nWhen doing live backups of any system, some files will grow/change during the backup operation. Typical example are various log files that grow all the time. I see that restic already issues warnings for this case, which is perfectly fine. The operator **should** be warned of files whose backup copy is possibly incomplete or inconsistent.\r\n```\r\nerror for /var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal: file has changed\r\n```\r\nBut, when checking these incomplete files, they're actually **zeroed**, which is certainly unexpected. I'd expect to have at least **some** content there:\r\n```\r\nls -al */var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal\r\n-rw-r----- 1 root systemd-journal         0 Aug 29 09:51 2016-08-29T09:44:46+02:00/var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal\r\n-rw-r----- 1 root systemd-journal         0 Aug 30 04:08 2016-08-30T04:00:23+02:00/var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal\r\n-rw-r----- 1 root systemd-journal  50331648 Aug 31 04:08 2016-08-31T04:00:20+02:00/var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal\r\n-rw-r----- 1 root systemd-journal         0 Sep  1 04:06 2016-09-01T04:00:20+02:00/var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal\r\n-rw-r----- 1 root systemd-journal         0 Sep  2 04:07 2016-09-02T04:00:20+02:00/var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal\r\n-rw-r----- 1 root systemd-journal  58720256 Sep  3 04:11 2016-09-03T04:00:22+02:00/var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal\r\n-rw-r----- 1 root systemd-journal 100663296 Sep  4 04:07 2016-09-04T04:00:21+02:00/var/log/journal/0c458b75baf807396c69f0dd530cc822/system.journal\r\n```\r\nTo add to this, checking the repository spits out errors that can't be fixed even with rebuild-index:\r\n```\r\nerror for tree b68877d8:\r\n  tree b68877d8: file \"system.journal\" has nil blob list\r\nerror for tree e61601be:\r\n  tree e61601be: file \"system.journal\" has nil blob list\r\nerror for tree cd9904e3:\r\n  tree cd9904e3: file \"system.journal\" has nil blob list\r\nerror for tree 3c0ba72c:\r\n  tree 3c0ba72c: file \"system.journal\" has nil blob list\r\n```\r\nOn my system these errors happen in most cases to the above mentioned system.journal, pacct (accounting) file and rrd files. And I have \"nil blob list\" errors for all of them."},"comment":{"url":"https://api.github.com/repos/restic/restic/issues/comments/244609262","html_url":"https://github.com/restic/restic/issues/604#issuecomment-244609262","issue_url":"https://api.github.com/repos/restic/restic/issues/604","id":244609262,"user":{"login":"fd0","id":123276,"avatar_url":"https://avatars.githubusercontent.com/u/123276?v=3","gravatar_id":"","url":"https://api.github.com/users/fd0","html_url":"https://github.com/fd0","followers_url":"https://api.github.com/users/fd0/followers","following_url":"https://api.github.com/users/fd0/following{/other_user}","gists_url":"https://api.github.com/users/fd0/gists{/gist_id}","starred_url":"https://api.github.com/users/fd0/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fd0/subscriptions","organizations_url":"https://api.github.com/users/fd0/orgs","repos_url":"https://api.github.com/users/fd0/repos","events_url":"https://api.github.com/users/fd0/events{/privacy}","received_events_url":"https://api.github.com/users/fd0/received_events","type":"User","site_admin":false},"created_at":"2016-09-04T15:18:46Z","updated_at":"2016-09-04T15:18:46Z","body":"Thanks for the report, that clearly shouldn't happen and be handled the way you described it. I'll have a look."}}
{"actor":{"display_login":"fd0"}}