Created attachment 1242218 [details]
NFS.log

Description of problem:

I have project where we tried to use the latest Gluster 3.7.19 cluster for shared storage in our HPC environment. I have a directory structure under /mnt/gluster/ as follows: 

/mnt/gluster/test(umask750) 
/mnt/gluster/test/testcfg (umask750) 
/mnt/gluster/test/testcfg2 (umask750) 
/mnt/gluster/test/testcfg/testdir(umask550) /mnt/gluster/test/testcfg/testdir/subdir(umask550). 
In each location I have files as well. 

When I'm trying to copy testdir into testcfg2(umask750) with a normal user "who is the owner of the mountpoint and directories" with cp -a it fails after creating subdir.

This is quite important for us as the HPV cluster scripts are doing their copy tasks with preserving the ownership, links etc.

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

How reproducible:
OS: RHEL 7.2

Steps to Reproduce:
1.Install Gluster 3.7.19 
2.create a volume, enable nfs
3.munt volume remotely
4.
cd /mnt/gluster/test
mkdir testcfg
chmod 750 testcfg
cd testcfg/
 mkdir testdir
cd testdir/
 mkdir subdir
echo "eeee" > eee.txt
chmod 550 subdir/
cd ..
chmod 550 testdir/
cd ..
mkdir testcfg2
chmod 750 testcfg2
cd testcfg2/
cp -a ../testcfg/testdir/ .

Actual results:
cp: cannot create directory `./testdir/subdir': Remote I/O error
ls -all /mnt/gluster/test/testcfg2/testdir/
dr-xr-x---. 2 tibcodev algo 4096 Jan 18 16:13 .
drwxr-x---. 3 tibcodev algo 4096 Jan 18 16:13 ..
-rw-r--r--. 1 tibcodev algo    5 Jan 18 16:13 eee.txt

Expected results:

dr-xr-x---. 3 tibcodev algo 4096 Jan 18 16:14 .
drwxr-x---. 3 tibcodev algo 4096 Jan 18 16:14 ..
-rw-r--r--. 1 tibcodev algo    5 Jan 18 16:14 eee.txt
dr-xr-x---. 2 tibcodev algo 4096 Jan 18 16:14 subdir


Additional info:
I have tested it with glusterfs mounts, the problem does not appeared. Also tested with locally mounted gluster volumes on the gluster host and linux nfs server, the error appears.
Did a test on a normal nfs share, the problem does not appears.
I have reverted back to Gluster version 3.7.11 what I was using during the PoC phase of the project in May 2016. There is no issue like this with that version. 

I was not able to choose 3.7.19 in the list of versions during the bug report.