Description of problem: When i mount a NFS share via gluster , there are times when i get permission denied error.Here is the followings logs. [2015-05-03 09:37:42.060945] W [client-rpc-fops.c:2766:client3_3_lookup_cbk] 0-umShare-client-0: remote operation failed: Permission denied. Path: /LoanApplication (66b435a6-92e1-4b8b-b07d-eae4ad894248) [2015-05-03 09:37:42.062188] W [client-rpc-fops.c:2766:client3_3_lookup_cbk] 0-umShare-client-0: remote operation failed: Permission denied. Path: (null) (00000000-0000-0000-0000-000000000000) [2015-05-03 09:38:21.086989] W [client-rpc-fops.c:2766:client3_3_lookup_cbk] 0-umShare-client-0: remote operation failed: Permission denied. Path: /LoanApplication (66b435a6-92e1-4b8b-b07d-eae4ad894248) [2015-05-03 09:38:21.088703] W [client-rpc-fops.c:2766:client3_3_lookup_cbk] 0-umShare-client-0: remote operation failed: Permission denied. Path: (null) (00000000-0000-0000-0000-000000000000) This only occur to my non-root user account.For root user account , there is no permission denied error. Version-Release number of selected component (if applicable): How reproducible: Cant reproduce as happen intermittently. Expected results: Does not get permission denied error. Additional info: Here is my gluster setting Volume Name: umShare Type: Replicate Volume ID: c26b7eb5-1385-4143-8f6f-f3b378c1b4b0 Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: SHTWPAPDD01:/home/umShare Brick2: SHTWPAPDD02:/home/umShare Options Reconfigured: features.quota: on performance.cache-max-file-size: 2MB performance.cache-refresh-timeout: 4 performance.io-thread-count: 32 performance.write-behind-window-size: 4MB performance.cache-size: 256MB Here is the path ACL setting # file: umShare/ # owner: jboss # group: jboss user::rwx group::rwx other::rwx For testing , i put 777 permission whether it will solve the error.But still happen even in this acl setting
Hi, are you using Gluster3.7 version? Also could paste the exact steps you have tried and the output you got? Thanks!
I think this has been reported on the mailinglist as a test case failure that hit once: http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10710 http://review.gluster.org/10600 should solve that problem for the master branch, and http://review.gluster.org/10655 for 3.7. The yesterday released 3.7.0 version has the fix, so it would be very good to know if you hit this problem with 3.7.0 too.
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days