Data Infrastructure Management Software Discussions
I'm trying to find out why a particular export of a qtree does not allow root to write while other export of the same kind does.
Both qtrees shown bellow have NTFS security because they are mostly accessed by CIFS customer but there is also the need of some NFS clients to access them too.
SANFILER01*> qtree security /vol/vl_rp_ftp_apl_01/sirius_citrix
/vol/vl_rp_ftp_apl_01/sirius_citrix has ntfs security style and oplocks are enabled.
SANFILER01*> qtree security /vol/vl_rp_ftp_apl_04/ftp_external
/vol/vl_rp_ftp_apl_04/ftp_external has ntfs security style and oplocks are enabled.
From a linux box (172.24.121.18) I can mount /vol/vl_rp_ftp_apl_01/sirius_citrix and write to it but, on other hand I can only mount /vol/vl_rp_ftp_apl_04/ftp_external but I have no write pemission.
If I change the export to the volume instead of the qtree /vol/vl_rp_ftp_apl_04, I can mount it, write on it but, If I cd into ftp_external, I no longer can write.
Can someone help me with this?
See The Solution
What is the security style of both volumes ?
What NFS client version do you use ( nfsv3 or nfsv4) ?
What about usermap configuration ?
Could you export both volume /vol/vl_rp_ftp_apl_04 and qtree /vol/vl_rp_ftp_apl_04/ftp_external in the same time and test.
The cause was already found. The customer forgot to add the windows user set on usermap.cfg to the permissions of this particular share on the windows side.
Thanks for your feedback any way.
View solution in original post