Bug 1403612 - With NFS root-squash the other x-bit has to be set to make dirs
Summary: With NFS root-squash the other x-bit has to be set to make dirs
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: nfs
Version: 3.7.17
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Niels de Vos
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-11 22:27 UTC by Hans Henrik Happe
Modified: 2017-03-08 10:58 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-08 10:58:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Hans Henrik Happe 2016-12-11 22:27:29 UTC
Description of problem:

Using NFS client and server.root-squash=on, directory creation is not allowed unless the others x-bit is set (chmod o+x). With the FUSE client it works as expected.  

Version-Release number of selected component (if applicable):

CentOS 6.8 (client and server).
GlusterFS from SIG.
3.7.13 did not have this problem.

How reproducible:

Every time.

Steps to Reproduce:
1. Set server.root-squash to on.
2. Mount with NFS client. 
3. Create dir without other x-bit (chmod o-x).
4. Try to create another dir in the dir => Not permitted.

Actual results:

[hhh@client foo]$ ls -la
total 8
drwxr-x--- 2 hhh others 4096 Dec 11 23:00 .
drwxrwx--x 3 hhh others 4096 Dec 11 22:56 ..
[hhh@client foo]$ mkdir bar
mkdir: cannot create directory `bar': Permission denied

Expected results:

[hhh@client foo]$ mkdir bar
[hhh@client foo]$ ls -l
total 4
drwxr-xr-x 2 hhh others 4096 Dec 11 23:22 bar


Additional info:

It is possible to create files.
When server.root-squash is off it works.
FUSE client works.

Comment 1 Kaushal 2017-03-08 10:58:00 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.