UNSOLVED

bdiuser

updated

16 years ago

B

bdiuser

11 Posts

0

12999

January 20th, 2011 08:00

setup proper default permissions for nfs share

hi,

I have a Celerra nx4 with an nfsv4 share and am having trouble setting up default permissions for clients.  When I create a file on the share another user in my environment cannot change the permissions on the FSO.  We're a linux/unix environment and do not want ldap, nis, ad, or any directory server involved.  I was looking into usermapping, but someone from support told me this is only a feature of CIFS shares.  Can someone help me in setting up my nx4 so that ownership and groupship is squashed on my share so that everyone who accesses it can make changes to it?  I saw that I can create a local usermap file, and am also wondering if that will be global to my nfs file system, seems like it effects the data mover more than anything...and if so, can someone give me documentation on the syntax of how to generate this file?  Thanks.  Here's a snippet of what I'm talking about...  I also tried changing the root host and rw hosts in the properties for my export but that doesn't seem to do what I want either.

ws19:test dennishuynh$ pwd
/Volumes/nx4/test
ws19:test dennishuynh$ ls
ws19:test dennishuynh$ whoami
dennishuynh
ws19:test dennishuynh$ touch test
ws19:test dennishuynh$ ls
test
ws19:test dennishuynh$ ls -al
total 3
drwxrwxrwx  2 dennishuynh  wheel    80 Jan 20 11:12 .
drwxrwxrwx  5 root         wheel  1024 Jan 20 11:12 ..
-rw-rw-rw-  1 dennishuynh  wheel     0 Jan 20 11:12 test
ws19:test dennishuynh$ su jun
Password:
OsX
ws19:test jun$ ls
test
ws19:test jun$ chmod 755 test
chmod: Unable to change file mode on test: Operation not permitted
ws19:test jun$

  • bdiuser

    11 Posts

    2228

    0

    Posted January 20th, 2011 08:00

    that is already done.  the problem isn't being able to write to the share, the problem is when i create a file or directory on the share, another user cannot change permission on it.  i want the quickest and easiest way to resolve this problem on an nfs share.  doesn't seem like its possible without the use of usermapping.  can anyone instruct me on how to do this with nfs?  i want a local usermap file where all users are mapped to one user...  thanks.

  • sebbyr

    99 Posts

    2228

    0

    Posted January 20th, 2011 08:00

    Don't share out the root of the filesystem.  Create a folder in there, and share this folder out.

    Let me know if this helps.

    Sebby Robles

    EMC Celerra Support

  • Rainer_EMC

    6 Operator

    8645 Posts

    2228

    1

    Posted January 20th, 2011 09:00

    NFSv3 or NFSv4 ? mixed or native access policy?

    With NFSv3 and NATIVE its just a question of either having rights through the groups or other permissions as normal in Unix

    Rainer

  • bdiuser

    11 Posts

    1695

    0

    Posted January 20th, 2011 09:00

    Sorry, its what our current ililon has and already what we invested in.  It's not too late tho, how would I go about setting this up with nfsv3?  So there is no way to map users without the use of Kerberos and ACLs using nfsv4, Are you certain about this? and nfsv3 doesn't require Kerberos and ACLs to map users?  And I was just reading that I may have proplems communicating with already existing nfsv4 shares with an nfsv3?  how will this be effected.  Thanks.

  • bdiuser

    11 Posts

    2228

    0

    Posted January 20th, 2011 09:00

    here's my environment.  i have the nx4 celerra and about 20 machines that need to access it.  we're on macs and linux machines mainly.  with no directory service involved, except for the one the os provides, we need all the clients to have access to this share.  if one client creates a file on the share, another client can easily go in and change permissions on this file without the use of the original person who created it.  on our ililon, basically all ther ownership and groupship is squashed in order for this to happen.  if i create a file on my isilon as 'dennis' on my machine, its seen as owned by 'owner' and group 'group'.  if this isn't possible to have done with nfsv4 and nfsv3 is my only option, please let confirm this and i'll roll back to nfsv3 and please provide me with instructions on how to set this up with the given environment.  (this seems so simple, i actually don't need my nx4 to  behave the way my isilon does, but there has to be some way to make this possible between users without overcomplicating it with kerberos and acls)  I think your latter suggestion answeres this, but I'm unsure because this a still new to me.  Thanks.

  • Rainer_EMC

    6 Operator

    8645 Posts

    1695

    0

    Posted January 20th, 2011 09:00

    Is there a specific reason you want to use NFSv4 ?

    It does make things more complicated with requiring Kerberos and ACLs compared to good old NFSv3

  • bdiuser

    11 Posts

    1257

    0

    Posted January 20th, 2011 11:00

    yes that's what i want, i want user1 on host ux1 to have the same uid as user2 on host ux2.

    no, we do not have an NIS or ldap database for name to uid/gid mapping, correct.

  • bdiuser

    11 Posts

    2230

    0

    Posted January 20th, 2011 11:00

    yes that's what i want, i want user1 on host ux1 to have the same uid as user2 on host ux2.

    no, we do not have an NIS or ldap database for name to uid/gid mapping, correct.

  • bergec

    275 Posts

    1257

    0

    Posted January 20th, 2011 11:00

    Are you saying that user1 on host UX1 can have the same UID as user2 on host UX2?

    You do not have any NIS or Ldap database for name to UID/GID mapping, correct?

    Claude

  • bergec

    275 Posts

    2228

    0

    Posted January 20th, 2011 11:00

    Are you saying that user1 on host UX1 can have the same UID as user2 on host UX2?

    You do not have any NIS or Ldap database for name to UID/GID mapping, correct?

    Claude