Unsolved
This post is more than 5 years old
17 Posts
0
690
February 26th, 2011 16:00
Can a filesystem be shared out as both CIFS and NFS?
We want to create a filesystem that can be accessed by Linux hosts and WIndows hosts. I created a filesystem /test in default mode and was able to share it as CIFS and NFS. Later on we may want to set permissions on the shares. I'm not sure if default mode is OK. Please shed some light.
No Events found!
gbarretoxx1
2 Intern
•
366 Posts
0
February 27th, 2011 06:00
Hi,
All objects ( files and directories ) have their own permissions on each side ( Windows ACL's and UNIX permissions ). This is the default behavior.
If you have any kind of syncronization between the two worlds ( such as NIS ), you must set up some parameters and mount the file system using access policy MIXED or MIXED_COMPAT.
See "Managing Celerra for a Multiprotocol Environment" on powerlink for more details.
Gustavo Barreto.
jimkunysz
2 Intern
•
259 Posts
0
February 28th, 2011 04:00
ownership of files can be a challenge to manage.
I typically set the cifs export with a umask=002 if both nfs and cifs are going to require R/W access.
carwynedwards
38 Posts
0
March 1st, 2011 08:00
We have this working. Be aware of the access control models that you need to pick between. For NFSv3 you can use NTFS-like permissions for CIFS and POSIX for NFS with various modes of resolving the access permissions. Read the Celerra docs about using the Celerra in multiprotocol environments, the CIFS docs and the NFS docs. You will also need to understand the usernamming and name services setup. Only in very recent versions of DART have some of the core issues relating to this really been ironed out, especially when using NFSv4 with Kerberos on one side and CIFS on the other all talking to Active Directory for usermapping.
For NFSv4 you need MIXED or MIXED_COMPAT mounts and I'd highly recommend using the Active Directory IdMU style of usermapping.