{"action":"created","issue":{"url":"https://api.github.com/repos/lizardfs/lizardfs/issues/672","repository_url":"https://api.github.com/repos/lizardfs/lizardfs","labels_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/672/labels{/name}","comments_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/672/comments","events_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/672/events","html_url":"https://github.com/lizardfs/lizardfs/issues/672","id":304043035,"number":672,"title":"3.12.0: suspected data corruption","user":{"login":"onlyjob","id":1061236,"avatar_url":"https://avatars0.githubusercontent.com/u/1061236?v=4","gravatar_id":"","url":"https://api.github.com/users/onlyjob","html_url":"https://github.com/onlyjob","followers_url":"https://api.github.com/users/onlyjob/followers","following_url":"https://api.github.com/users/onlyjob/following{/other_user}","gists_url":"https://api.github.com/users/onlyjob/gists{/gist_id}","starred_url":"https://api.github.com/users/onlyjob/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/onlyjob/subscriptions","organizations_url":"https://api.github.com/users/onlyjob/orgs","repos_url":"https://api.github.com/users/onlyjob/repos","events_url":"https://api.github.com/users/onlyjob/events{/privacy}","received_events_url":"https://api.github.com/users/onlyjob/received_events","type":"User","site_admin":false},"labels":[{"id":38090254,"url":"https://api.github.com/repos/lizardfs/lizardfs/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-03-10T05:10:47Z","updated_at":"2018-03-28T22:14:07Z","closed_at":null,"author_association":"MEMBER","body":"Ever since upgrade to 3.12.0 my apt-cacher-ng is malfunctioning: installing or upgrading packages is no longer possible because downloaded (.deb) files fail integrity check. Changing cache location from LizardFS mount to local file system fixed the problem. 3.11.3 (and all previous releases back to 2.6) never had this problem.\r\n\r\nI don't have synthetic reproducer for this problem yet and I am very worried about integrity of the data. I've tested integrity of some old files and found no problems so corruption must be happening on write.\r\n\r\nPlease investigate this as a highest priority."},"comment":{"url":"https://api.github.com/repos/lizardfs/lizardfs/issues/comments/377055475","html_url":"https://github.com/lizardfs/lizardfs/issues/672#issuecomment-377055475","issue_url":"https://api.github.com/repos/lizardfs/lizardfs/issues/672","id":377055475,"user":{"login":"onlyjob","id":1061236,"avatar_url":"https://avatars0.githubusercontent.com/u/1061236?v=4","gravatar_id":"","url":"https://api.github.com/users/onlyjob","html_url":"https://github.com/onlyjob","followers_url":"https://api.github.com/users/onlyjob/followers","following_url":"https://api.github.com/users/onlyjob/following{/other_user}","gists_url":"https://api.github.com/users/onlyjob/gists{/gist_id}","starred_url":"https://api.github.com/users/onlyjob/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/onlyjob/subscriptions","organizations_url":"https://api.github.com/users/onlyjob/orgs","repos_url":"https://api.github.com/users/onlyjob/repos","events_url":"https://api.github.com/users/onlyjob/events{/privacy}","received_events_url":"https://api.github.com/users/onlyjob/received_events","type":"User","site_admin":false},"created_at":"2018-03-28T22:14:07Z","updated_at":"2018-03-28T22:14:07Z","author_association":"MEMBER","body":"I'm afraid I have no capacity to isolate (bisect) the problem... I've inspected freshly downloaded .deb files in `apt-cacher-ng/cache` and found garbage in some of them...\r\nServer where it is happening have ECC RAM and no hardware error were reported..."}}
{"actor":{"display_login":"onlyjob"}}