-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
permission denied issue on glusterfs 6.4 #711
Comments
Patch to backport the same in the release-6 |
Noticed that this was not merged as it was blocked on regression. @woodlgz thanks for reporting. Will make sure this is merged into next release. |
The patch has been merged into release-6. It should be a part of 6.6 which is supposed to be released on 30th Oct. The tracker ug for 6.6: https://bugzilla.redhat.com/show_bug.cgi?id=1762237 |
FYI this affects 5.10 as well. My users and I have been noticing sporadic "permission denied" errors for a few months on release-5. For what it's worth, the one-line reproducer in the bug report works very well to illustrate the issue. If I mount the Gluster volume with |
This works around sporadic "permission denied" errors. The issue is fixed in GlusterFS master and 6.5, but not 5.x yet. See: gluster/glusterfs#711 See: https://bugzilla.redhat.com/show_bug.cgi?id=1668286
Update: after a suggestion on the gluster-users mailing list I cherry-picked this fix from master and submitted it to Gerrit for inclusion in the next 5.x release. |
Hi Alan, I have cloned the bug for release-5 the bug id is 1767305. Please do update, so we can take it in. |
I also encountered permission problems in version 6.4. During the process of copying files, I tracked the code and found that when frame->root->uid =0, he can succeed, Debug:frame_is_user uid=0 fuid=0 |
https://review.gluster.org/#/c/glusterfs/+/23233/ has the RC and fix |
I am running glusterfs 6.4 in my environment.
For every first time users enter a glusterfs directory and 'ls -la' the files ,after which trying to access any of them, a permission denied error is prompt.
The phenonmenon looks exactly alike to what was described in https://bugzilla.redhat.com/show_bug.cgi?id=1668286。
And I noticed that this issue was fixed at master branch with commit 6bf9637。
I worked around this problem by temporarily turning off readdirp. Permission denied problem is gone.
I suggest there should be a fix at branch release 6.0 as well.
The text was updated successfully, but these errors were encountered: