No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-How to recognize UGO-permission of NFS share on CIFS client

Publication Date:  2017-11-08 Views:  109 Downloads:  0
Issue Description

Version information: OceanStor 5500V3  V300R003C20SPC200


Customer set permission of NFS share by chmod command on NFS client(Linux). For example, create a directory (quota tree) TEST0000 with owner root, group staff. UGO-permission 750. In addition, a directory TEST0001 with owner root, group root, UGO-permission 750.

 drwxr-x--- 2 root staff 14 Oct  1 22:38 TEST0000

 drwxr-x--- 2 root root   2 Oct  1 22:34 TEST0001

 And the customer account Nils is a member of staff group on Unix NIS server, also a member of group staff on Windows AD server.

When customer looking at file permission on CIFS share, he find the following permission setting:

How to recognize these permission?



On CIFS share, the storage  “translate” UGO permission of NFS share to separate rules, plus current user’s permission rule.

As the first screenshot, the first rule is for owner(root account),  Since the CIFS client can only "translate" read, write, execute permissions, the permission 7 and 0 on NFS share is translated Special Access.

The second rule is for group user, S-1-6-88-2XXX5648 is the group ID and permission is shown as Read & execute.

The third rule is for other users(everyone).

And the last rule is for current user. Since current user(Nils) is belong to staff group, the permission is the same as the second rule.

Also, we can recognize the rules on the second screenshot.