Description of problem: If requests are coming from the clients which are mounted in the trusted storage pool, (that too using the same glusterd's ip/hostname where it is mounted), then disable root-squashing on for those clients. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#1) for review on master by Raghavendra Bhat (raghavendra)
http://review.gluster.org/#/c/4863/ has been submitted for review.
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#2) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#3) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#4) for review on master by Raghavendra Bhat (raghavendra)
*** Bug 960913 has been marked as a duplicate of this bug. ***
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#5) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#6) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#7) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#8) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#9) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#10) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#11) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#12) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#13) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#14) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#15) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#16) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#17) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#18) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/4863 (protocol/server: do not do root-squashing for trusted clients) posted (#19) for review on master by Raghavendra Bhat (raghavendra)
COMMIT: http://review.gluster.org/4863 committed in master by Vijay Bellur (vbellur) ------ commit 28209283a67f13802cc0c1d3df07c676926810a2 Author: Raghavendra Bhat <raghavendra> Date: Fri Apr 19 12:27:03 2013 +0530 protocol/server: do not do root-squashing for trusted clients * As of now clients mounting within the storage pool using that machine's ip/hostname are trusted clients (i.e clients local to the glusterd). * Be careful when the request itself comes in as nfsnobody (ex: posix tests). So move the squashing part to protocol/server when it creates a new frame for the request, instead of auth part of rpc layer. * For nfs servers do root-squashing without checking if it is trusted client, as all the nfs servers would be running within the storage pool, hence will be trusted clients for the bricks. * Provide one more option for mounting which actually says root-squash should/should not happen. This value is given priority only for the trusted clients. For non trusted clients, the volume option takes the priority. But for trusted clients if root-squash should not happen, then they have to be mounted with root-squash=no option. (This is done because by default blocking root-squashing for the trusted clients will cause problems for smb and UFO clients for which the requests have to be squashed if the option is enabled). * For geo-replication and defrag clients do not do root-squashing. * Introduce a new option in open-behind for doing read after successful open. Change-Id: I8a8359840313dffc34824f3ea80a9c48375067f0 BUG: 954057 Signed-off-by: Raghavendra Bhat <raghavendra> Reviewed-on: http://review.gluster.org/4863 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/6975 (mount.glusterfs: backward compatible option for root-squashing) posted (#1) for review on master by Raghavendra Bhat (raghavendra)
COMMIT: http://review.gluster.org/6975 committed in master by Vijay Bellur (vbellur) ------ commit 2e093c728c856a41399ffdcf33c91d21c3a2f0f2 Author: Raghavendra Bhat <raghavendra> Date: Tue Feb 11 13:16:38 2014 +0530 mount.glusterfs: backward compatible option for root-squashing Change-Id: I74fa6686cff84cfad4a2587a0061e6bb2beea081 BUG: 954057 Signed-off-by: Raghavendra Bhat <raghavendra> Reviewed-on: http://review.gluster.org/6975 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users