{"action":"closed","issue":{"url":"https://api.github.com/repos/zfsonlinux/zfs/issues/3224","labels_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/3224/labels{/name}","comments_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/3224/comments","events_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/3224/events","html_url":"https://github.com/zfsonlinux/zfs/issues/3224","id":64216720,"number":3224,"title":"bad error : disappearing / reappearing file visibility ","user":{"login":"tom71","id":11644512,"avatar_url":"https://avatars.githubusercontent.com/u/11644512?v=3","gravatar_id":"","url":"https://api.github.com/users/tom71","html_url":"https://github.com/tom71","followers_url":"https://api.github.com/users/tom71/followers","following_url":"https://api.github.com/users/tom71/following{/other_user}","gists_url":"https://api.github.com/users/tom71/gists{/gist_id}","starred_url":"https://api.github.com/users/tom71/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tom71/subscriptions","organizations_url":"https://api.github.com/users/tom71/orgs","repos_url":"https://api.github.com/users/tom71/repos","events_url":"https://api.github.com/users/tom71/events{/privacy}","received_events_url":"https://api.github.com/users/tom71/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/zfsonlinux/zfs/labels/Bug%20-%20Minor","name":"Bug - Minor","color":"e11d21"},{"url":"https://api.github.com/repos/zfsonlinux/zfs/labels/Difficulty%20-%20Medium","name":"Difficulty - Medium","color":"207de5"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-03-25T08:47:30Z","updated_at":"2015-05-14T18:19:34Z","closed_at":"2015-05-14T18:19:34Z","body":"We have the problem, that files are shown as \"No such file or directory\", when we try to access them. After a few access tries, they are accessible again. This error is shown locally and via nfs. The error happens after about 10 hours of run time of our software. As we have lots of data, we cannot provide a reproducer script on its own. But we have created a test zfs pool now and try to shorten the time til the errror occurs to a range of minutes. We try to accomplish this by raising the work load by a factor of 10. We will also run zdb -ddddd on the test pool before and after the error. \r\nWe can provide a login to our machines, so developpers can gather more information."}}