{"action":"created","issue":{"url":"https://api.github.com/repos/restic/restic/issues/358","labels_url":"https://api.github.com/repos/restic/restic/issues/358/labels{/name}","comments_url":"https://api.github.com/repos/restic/restic/issues/358/comments","events_url":"https://api.github.com/repos/restic/restic/issues/358/events","html_url":"https://github.com/restic/restic/issues/358","id":118544299,"number":358,"title":"Regression: local backup of large data set - pack not referenced in any index","user":{"login":"episource","id":3219567,"avatar_url":"https://avatars.githubusercontent.com/u/3219567?v=3","gravatar_id":"","url":"https://api.github.com/users/episource","html_url":"https://github.com/episource","followers_url":"https://api.github.com/users/episource/followers","following_url":"https://api.github.com/users/episource/following{/other_user}","gists_url":"https://api.github.com/users/episource/gists{/gist_id}","starred_url":"https://api.github.com/users/episource/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/episource/subscriptions","organizations_url":"https://api.github.com/users/episource/orgs","repos_url":"https://api.github.com/users/episource/repos","events_url":"https://api.github.com/users/episource/events{/privacy}","received_events_url":"https://api.github.com/users/episource/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-11-24T06:53:52Z","updated_at":"2015-11-26T08:58:45Z","closed_at":null,"body":"Possible regression: The issue in #292 is back again! #292 was finally solved in cc7acba, but that was some while ago and lot changed in the meanwhile.  Sadly I can't tell at which commit after cc7acba the issue reappeared. Due to the non-deterministic nature of this issue it's hard to tell. \r\n\r\n**Restic version:** restic 0.1.0 (v0.1.0-147-g867fc5b), compiled at 2015-11-21 09:32:12 with go1.5.1\r\n\r\n**Expected behavior:** restic check passes successfuly and hashdeep confirms file integrity.\r\n\r\n**Observed behavior:** pack not referenced in any index, chance of observing this errors seems to increase with backup set size and data duplication; see also #292.\r\n\r\nBackup can be restored without errors. This has been verified using a hashdeep md5 audit file.\r\n\r\n```\r\nrestic -r /media/backup-intern/restic/limucs-main.repo --cache-dir=/root/.cache/restic check\r\nCreate exclusive lock for repository\r\nLoad indexes\r\nCheck all packs\r\npack a2de8d66e12c28b36c63827a0a8e75583cc8f4186e7004fc68e2e7d6c328a5d8: not referenced in any index\r\nCheck snapshots, trees and blobs\r\nrepository contains errors\r\n```\r\n\r\n**Steps to reproduce:** Backup a large data set (mine is ~500G) with duplication. I will repeat my analysis from #292 as soon as possible, but can't provide a timeline."},"comment":{"url":"https://api.github.com/repos/restic/restic/issues/comments/159851559","html_url":"https://github.com/restic/restic/issues/358#issuecomment-159851559","issue_url":"https://api.github.com/repos/restic/restic/issues/358","id":159851559,"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":"2015-11-26T08:58:45Z","updated_at":"2015-11-26T08:58:45Z","body":"Thank you very much for reporting the bug and the detailed analysis! I'll have a look this evening, but I suspect that locking both indexes can possibly lead to a deadlock situation. In addition, I'm currently reworking the `Repository` struct (which is way too complex)."}}