<html><body><p><font face="Arial">Please make sure NFSv4 ID Mapping value matches on client and server</font><br><font face="Arial">(e.g. test.com; may vary on your setup).</font><br><font face="Arial"><br>server:</font><br><font face="Arial"> mmnfs config change IDMAPD_DOMAIN=test.com</font><br><font face="Arial"><br>client:</font><br><font face="Arial"> e.g. RHEL NFS client; set Domain attribute in /etc/idmapd.conf file and restart idmap service.</font><br> <font face="Arial"># egrep ^Domain /etc/idmapd.conf<br> Domain = test.com<br> # service nfs-idmap restart</font><br><font face="Arial"><br>reference Link:</font><u><font color="#0000FF"><br> </font></u><a href="https://www.ibm.com/support/knowledgecenter/en/STXKQY_5.0.0/com.ibm.spectrum.scale.v5r00.doc/b1ladm_authconsidfornfsv4access.htm"><u><font color="#0000FF" face="Arial">https://www.ibm.com/support/knowledgecenter/en/STXKQY_5.0.0/com.ibm.spectrum.scale.v5r00.doc/b1ladm_authconsidfornfsv4access.htm</font></u></a><br><font face="Arial"><br>Thanks,<br>Chetan.</font><br><br><img width="16" height="16" src="cid:1__=EABB0823DFCAB9AF8f9e8a93df938690918cEAB@" border="0" alt="Inactive hide details for "Wilson, Neil" ---06/18/2018 09:35:55 PM---I think it’s caused by the ID mapping not being configure"><font size="2" color="#424282">"Wilson, Neil" ---06/18/2018 09:35:55 PM---I think it’s caused by the ID mapping not being configured properly. Found this on the redhat knowle</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Wilson, Neil" <neil.wilson@metoffice.gov.uk></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">gpfsug main discussion list <gpfsug-discuss@spectrumscale.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">06/18/2018 09:35 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [gpfsug-discuss] CES-NFS: UID and GID resolution</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font color="#1F497D" face="Calibri">I think it’s caused by the ID mapping not being configured properly.</font><br><font color="#1F497D" face="Calibri">Found this on the redhat knowledge base.</font><br><font color="#1F497D" face="Calibri"> </font><p><b><font size="5" face="Times New Roman">Environment</font></b><ul><ul type="disc"><li><font face="Calibri">Red Hat Enterprise Linux 5</font><li><font face="Calibri">Red Hat Enterprise Linux 6 </font><li><font face="Calibri">Red Hat Enterprise Linux 7 </font><li><font face="Calibri">NFSv4 share being exported from an NFSv4 capable NFS server</font></ul></ul><b><font size="5" face="Times New Roman">Issue</font></b><ul><ul type="disc"><li><font face="Calibri">From the client, the mounted NFSv4 share has ownership for all files and directories listed as </font><font size="2" face="Courier New">nobody:nobody</font><font face="Calibri"> instead of the actual user that owns them on the NFSv4 server, or who created the new file and directory. </font><li><font face="Calibri">Seeing nobody:nobody permissions on nfsv4 shares on the nfs client. Also seeing the following error in /var/log/messages:</font><li><font face="Calibri">How to configure Idmapping for NFSv4</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New">nss_getpwnam: name 'root@example.com' does not map into domain 'localdomain' </font><br><b><font size="5" face="Times New Roman">Resolution</font></b><ul><ul type="disc"><li><font face="Calibri">Modify the </font><font size="2" face="Courier New">/etc/idmapd.conf</font><font face="Calibri"> with the proper domain (FQDN), on both the client and server. In this example, the proper domain is "example.com" so the "Domain =" directive within </font><font size="2" face="Courier New">/etc/idmapd.conf</font><font face="Calibri"> should be modified to read:</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New">Domain = example.com</font><ul><ul type="disc"><li><font face="Calibri">Note: </font><ul><ul type="circle"><li><font face="Calibri">If using a NetApp Filer, the </font><font size="2" face="Courier New">NFS.V4.ID.DOMAIN</font><font face="Calibri"> parameter must be set to match the "Domain =" parameter on the client.</font><li><font face="Calibri">If using a Solaris machine as the NFS server, the </font><font size="2" face="Courier New">NFSMAPID_DOMAIN</font><font face="Calibri"> value in </font><font size="2" face="Courier New">/etc/default/nfs</font><font face="Calibri"> must match the RHEL clients Domain.</font></ul></ul>
<li><b><font face="Calibri">On Red Hat Enterprise Linux 6.2 and older</font></b><font face="Calibri">, to put the changes into effect restart the </font><font size="2" face="Courier New">rpcidmapd</font><font face="Calibri"> service and remount the NFSv4 filesystem : </font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New"># service rpcidmapd restart</font><br><font size="2" face="Courier New"># mount -o remount /nfs/mnt/point</font><p><font face="Times New Roman">NOTE: It is only necessary to restart rpc.idmapd service on systems where rpc.idmapd is actually performing the id mapping. On RHEL 6.3 and newer NFS CLIENTS, the maps are stored in the kernel keyring and the id mapping itself is performed by the /sbin/nfsidmap program. On older NFS CLIENTS (RHEL 6.2 and older) as well as on all NFS SERVERS running RHEL, the id mapping is performed by rpc.idmapd.</font><ul><ul type="disc"><li><font face="Calibri">Ensure the client and server have matching UID's and GID's. It is a common misconception that the UID's and GID's can differ when using NFSv4. The sole purpose of id mapping is to map an id to a name and vice-versa. ID mapping is not intended as some sort of replacement for managing id's.</font><li><b><font face="Calibri">On Red Hat Enterprise Linux 6.3 and higher</font></b><font face="Calibri">, if the above settings have been applied and UID/GID's are matched on server and client and users are still being mapped to </font><font size="2" face="Courier New">nobody:nobody</font><font face="Calibri"> than a clearing of the </font><font size="2" face="Courier New">idmapd</font><font face="Calibri"> cache may be required:</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New"> # nfsidmap -c </font><p><font face="Times New Roman">NOTE: The above command is only necessary on systems that use the keyring-based id mapper, i.e. NFS CLIENTS running RHEL 6.3 and higher. On RHEL 6.2 and older NFS CLIENTS as well as all NFS SERVERS running RHEL, the cache should be cleared out when rpc.idmapd is restarted.</font><ul><ul type="disc"><li><font face="Calibri">Another check, see if the passwd:, shadow: and group: settings are set correctly in the </font><font size="2" face="Courier New">/etc/nsswitch.conf</font><font face="Calibri"> file on both Server and Client.</font></ul></ul><b><font size="4" face="Times New Roman">Disabling idmapping</font></b><p><b><font face="Times New Roman">NOTE: In order to properly disable idmapping, it must be disabled on both the NFS client and NFS server.</font></b><font face="Times New Roman"><br>- By default, RHEL6.3 and newer NFS clients and servers disable idmapping when utilizing the AUTH_SYS/UNIX authentication flavor by enabling the following booleans:</font><br><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New">NFS client </font><br><font size="2" face="Courier New"> # echo 'Y' > /sys/module/nfs/parameters/nfs4_disable_idmapping </font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New">NFS server</font><br><font size="2" face="Courier New"> # echo 'Y' > /sys/module/nfsd/parameters/nfs4_disable_idmapping </font><ul><ul type="disc"><li><font face="Calibri">If using a NetApp filer, the </font><font size="2" face="Courier New">options nfs.v4.id.allow_numerics on</font><font face="Calibri"> command can be used to disable idmapping. More information can be found </font><a href="https://library.netapp.com/ecmdocs/ECMP1196993/html/GUID-24367A9F-E17B-4725-ADC1-02D86F56F78E.html"><u><font color="#0563C1" face="Calibri">here</font></u></a><font face="Calibri">.</font><li><font face="Calibri">With this boolean enabled, NFS clients will instead send numeric UID/GID numbers in outgoing attribute calls and NFS servers will send numeric UID/GID numbers in outgoing attribute replies.</font><p><font size="2" face="Symbol">· </font><font face="Times New Roman">If NFS clients sending numeric UID/GID values in a SETATTR call receive an NFS4ERR_BADOWNER reply from the NFS server clients will re-enable idmapping and send </font><font size="2" face="Courier New">user@domain</font><font face="Times New Roman"> strings for that specific mount from that point forward.</font><p><font size="2" face="Symbol">· </font><font face="Times New Roman">We can make the option </font><font size="2" face="Courier New">nfs4_disable_idmapping</font><font face="Times New Roman"> persistent across reboot.</font><p><font size="2" face="Symbol">· </font><font face="Times New Roman">After the above value has been changed, for the setting to take effect for any NFS server export mounted on the NFS client, you must unmount all NFS mount points for the given NFS server, and then re-mount them. If you have auto mounts stop all processes accessing the mounts and allow the automount daemon to unmount them. Once all NFS mount points are gone to the desired NFS server, remount the NFS mount points and the new setting should be in place. If this is too problematic, you may want to schedule a reboot of the NFS client.</font><p><font size="2" face="Symbol">· </font><font face="Times New Roman">To verify the setting has been changed properly, you can look inside the /proc/self/mountstats file 'caps' line, which contains a hex value of 2 bytes (16 bits). This is the line that shows the NFS server's "capabilities", and the most significant bit #15 is the one which represents whether idmapping is disabled or not (the </font><font size="2" face="Courier New">NFS_CAP_UIDGID_NOMAP</font><font face="Times New Roman"> bit - see the Root Cause section)</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New"># cat /sys/module/nfs/parameters/nfs4_disable_idmapping</font><br><font size="2" face="Courier New">Y</font><br><font size="2" face="Courier New"># umount /mnt</font><br><font size="2" face="Courier New"># mount rhel6u6-node2:/exports/nfs4 /mnt</font><br><font size="2" face="Courier New"># grep -A 5 rhel6u6-node2 /proc/self/mountstats | egrep '(rhel6u6-node2|caps:)'</font><br><font size="2" face="Courier New">device rhel6u6-node2:/exports/nfs4 mounted on /mnt with fstype nfs4 statvers=1.0</font><br><font size="2" face="Courier New"> caps: caps=0xffff,wtmult=512,dtsize=32768,bsize=0,namlen=255</font><br><font size="2" face="Courier New"> ^</font><ul><ul type="disc"><li><font face="Calibri">Example of nfs4_disable_idmapping = 'N'</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New">[root@rhel6u3-node1 ~]# echo N > /sys/module/nfs/parameters/nfs4_disable_idmapping</font><br><font size="2" face="Courier New">[root@rhel6u3-node1 ~]# umount /mnt</font><br><font size="2" face="Courier New">[root@rhel6u3-node1 ~]# mount rhel6u6-node2:/exports/nfs4 /mnt</font><br><font size="2" face="Courier New">[root@rhel6u3-node1 ~]# grep -A 5 rhel6u6-node2 /proc/self/mountstats | egrep '(rhel6u6-node2|caps:)'</font><br><font size="2" face="Courier New">device rhel6u6-node2:/exports/nfs4 mounted on /mnt with fstype nfs4 statvers=1.0</font><br><font size="2" face="Courier New"> caps: caps=0x7fff,wtmult=512,dtsize=32768,bsize=0,namlen=255</font><br><font size="2" face="Courier New"> ^</font><p><font face="Times New Roman">NOTE: To force ONLY numeric IDs to be used on the client, add </font><font size="2" face="Courier New">RPCIDMAPDARGS="-C"</font><font face="Times New Roman"> to the </font><font size="2" face="Courier New">etc/sysconfig/nfs</font><font face="Times New Roman"> file and restart the </font><font size="2" face="Courier New">rpcidmapd</font><font face="Times New Roman"> service. See man </font><font size="2" face="Courier New">rpc.idmapd</font><font face="Times New Roman"> for more information.</font><p><font face="Times New Roman">NOTE: This option can only be used with AUTH_SYS/UNIX authentication flavors, if you wish to use something like Kerberos, idmapping must be used.</font><p><b><font size="5" face="Times New Roman">Root Cause</font></b><ul><ul type="disc"><li><font face="Calibri">NFSv4 utilizes ID mapping to ensure permissions are set properly on exported shares, if the domains of the client and server do not match then the permissions are mapped to </font><font size="2" face="Courier New">nobody:nobody</font><font face="Calibri">. </font></ul></ul><font size="2" face="Courier New">NFS_CAP_UIDGID_NOMAP</font><font face="Times New Roman"> bit</font><ul><ul type="disc"><li><font face="Calibri">The nfs4_disable_idmapping is a module parameter which is read only one time, at the point at which the kernel sets up the data structure that represents an NFS server. Once it is read, a flag is set in the nfs_server structure NFS_CAP_UIDGID_NOMAP.</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New">#define NFS_CAP_UIDGID_NOMAP (1U << 15)</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New">static int nfs4_init_server(struct nfs_server *server,</font><br><font size="2" face="Courier New"> const struct nfs_parsed_mount_data *data)</font><br><font size="2" face="Courier New">{</font><br><font size="2" face="Courier New"> struct rpc_timeout timeparms;</font><br><font size="2" face="Courier New"> int error;</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> dprintk("--> nfs4_init_server()\n");</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> nfs_init_timeout_values(&timeparms, data->nfs_server.protocol,</font><br><font size="2" face="Courier New"> data->timeo, data->retrans);</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> /* Initialise the client representation from the mount data */</font><br><font size="2" face="Courier New"> server->flags = data->flags;</font><br><font size="2" face="Courier New"> server->caps |= NFS_CAP_ATOMIC_OPEN|NFS_CAP_CHANGE_ATTR|NFS_CAP_POSIX_LOCK;</font><br><font size="2" face="Courier New"> if (!(data->flags & NFS_MOUNT_NORDIRPLUS))</font><br><font size="2" face="Courier New"> server->caps |= NFS_CAP_READDIRPLUS;</font><br><font size="2" face="Courier New"> server->options = data->options;</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> /* Get a client record */</font><br><font size="2" face="Courier New"> error = nfs4_set_client(server,</font><br><font size="2" face="Courier New"> data->nfs_server.hostname,</font><br><font size="2" face="Courier New"> (const struct sockaddr *)&data->nfs_server.address,</font><br><font size="2" face="Courier New"> data->nfs_server.addrlen,</font><br><font size="2" face="Courier New"> data->client_address,</font><br><font size="2" face="Courier New"> data->auth_flavors[0],</font><br><font size="2" face="Courier New"> data->nfs_server.protocol,</font><br><font size="2" face="Courier New"> &timeparms,</font><br><font size="2" face="Courier New"> data->minorversion);</font><br><font size="2" face="Courier New"> if (error < 0)</font><br><font size="2" face="Courier New"> goto error;</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> /*</font><br><font size="2" face="Courier New"> * Don't use NFS uid/gid mapping if we're using AUTH_SYS or lower</font><br><font size="2" face="Courier New"> * authentication.</font><br><font size="2" face="Courier New"> */</font><br><font size="2" face="Courier New"> if (nfs4_disable_idmapping && data->auth_flavors[0] == RPC_AUTH_UNIX) <--- set a flag based on the module parameter</font><br><font size="2" face="Courier New"> server->caps |= NFS_CAP_UIDGID_NOMAP; <-------------------------- flag set</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> if (data->rsize)</font><br><font size="2" face="Courier New"> server->rsize = nfs_block_size(data->rsize, NULL);</font><br><font size="2" face="Courier New"> if (data->wsize)</font><br><font size="2" face="Courier New"> server->wsize = nfs_block_size(data->wsize, NULL);</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> server->acregmin = data->acregmin * HZ;</font><br><font size="2" face="Courier New"> server->acregmax = data->acregmax * HZ;</font><br><font size="2" face="Courier New"> server->acdirmin = data->acdirmin * HZ;</font><br><font size="2" face="Courier New"> server->acdirmax = data->acdirmax * HZ;</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> server->port = data->nfs_server.port;</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> error = nfs_init_server_rpcclient(server, &timeparms, data->auth_flavors[0]);</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New">error:</font><br><font size="2" face="Courier New"> /* Done */</font><br><font size="2" face="Courier New"> dprintk("<-- nfs4_init_server() = %d\n", error);</font><br><font size="2" face="Courier New"> return error;</font><br><font size="2" face="Courier New">}</font><ul><ul type="disc"><li><font face="Calibri">This flag is later checked when deciding whether to use numeric uid or gids or to use idmapping.</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New">int nfs_map_uid_to_name(const struct nfs_server *server, __u32 uid, char *buf, size_t buflen)</font><br><font size="2" face="Courier New">{</font><br><font size="2" face="Courier New"> struct idmap *idmap = server->nfs_client->cl_idmap;</font><br><font size="2" face="Courier New"> int ret = -EINVAL;</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> if (!(server->caps & NFS_CAP_UIDGID_NOMAP)) { <------------ CHECK FLAG, DECIDE whether to call idmapper</font><br><font size="2" face="Courier New"> ret = nfs_idmap_lookup_name(uid, "user", buf, buflen);</font><br><font size="2" face="Courier New"> if (ret < 0)</font><br><font size="2" face="Courier New"> ret = nfs_idmap_name(idmap, &idmap->idmap_user_hash, uid, buf);</font><br><font size="2" face="Courier New"> }</font><br><font size="2" face="Courier New"> if (ret < 0)</font><br><font size="2" face="Courier New"> ret = nfs_map_numeric_to_string(uid, buf, buflen);</font><br><font size="2" face="Courier New"> return ret;</font><br><font size="2" face="Courier New">}</font><br><font size="2" face="Courier New">int nfs_map_gid_to_group(const struct nfs_server *server, __u32 gid, char *buf, size_t buflen)</font><br><font size="2" face="Courier New">{</font><br><font size="2" face="Courier New"> struct idmap *idmap = server->nfs_client->cl_idmap;</font><br><font size="2" face="Courier New"> int ret = -EINVAL;</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> if (!(server->caps & NFS_CAP_UIDGID_NOMAP)) { <------------ CHECK FLAG, DECIDE whether to call idmapper</font><br><font size="2" face="Courier New"> ret = nfs_idmap_lookup_name(gid, "group", buf, buflen);</font><br><font size="2" face="Courier New"> if (ret < 0)</font><br><font size="2" face="Courier New"> ret = nfs_idmap_name(idmap, &idmap->idmap_group_hash, gid, buf);</font><br><font size="2" face="Courier New"> }</font><br><font size="2" face="Courier New"> if (ret < 0)</font><br><font size="2" face="Courier New"> ret = nfs_map_numeric_to_string(gid, buf, buflen);</font><br><font size="2" face="Courier New"> return ret;</font><br><font size="2" face="Courier New">}</font><br><font size="2" face="Courier New">"fs/nfs/idmap.c" 872L, 21804C</font><ul><ul type="disc"><li><font face="Calibri">For more information on NFSv4 ID mapping in Red Hat Enterprise Linux, see </font><a href="https://access.redhat.com/articles/2252881"><u><font color="#0563C1" face="Calibri">https://access.redhat.com/articles/2252881</font></u></a></ul></ul><b><font size="5" face="Times New Roman">Diagnostic Steps</font></b><ul><ul type="disc"><li><font face="Calibri">Debugging/verbosity can be enabled by editing </font><font size="2" face="Courier New">/etc/sysconfig/nfs</font><font face="Calibri">:</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New">RPCIDMAPDARGS="-vvv"</font><ul><ul type="disc"><li><font face="Calibri">The following output is shown in </font><font size="2" face="Courier New">/var/log/messages</font><font face="Calibri"> when the mount has been completed and the system shows </font><font size="2" face="Courier New">nobody:nobody</font><font face="Calibri"> as user and group permissions on directories and files:</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New">Jun 3 20:22:08 node1 rpc.idmapd[1874]: nss_getpwnam: name 'root@example.com' does not map into domain 'localdomain' </font><br><font size="2" face="Courier New">Jun 3 20:25:44 node1 rpc.idmapd[1874]: nss_getpwnam: name 'root@example.com' does not map into domain 'localdomain'</font><ul><ul type="disc"><li><font face="Calibri">Collect a </font><font size="2" face="Courier New">tcpdump</font><font face="Calibri"> of the mount attempt:</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New"># tcpdump -s0 -i {INTERFACE} host {NFS.SERVER.IP} -w /tmp/{casenumber}-$(hostname)-$(date +"%Y-%m-%d-%H-%M-%S").pcap & </font><ul><ul type="disc"><li><font face="Calibri">If a TCP packet capture has been obtained, check for a </font><font size="2" face="Courier New">nfs.nfsstat4</font><font face="Calibri"> packet that has returned a non-zero response equivalent to 10039 (NFSV4ERR_BADOWNER). </font><li><font face="Calibri">From the NFSv4 RFC:</font></ul></ul><a href="https://access.redhat.com/solutions/33455"><u><font color="#0563C1" face="Calibri">Raw</font></u></a><br><font size="2" face="Courier New"> NFS4ERR_BADOWNER = 10039,/* owner translation bad */</font><br><font size="2" face="Courier New"> </font><br><font size="2" face="Courier New"> NFS4ERR_BADOWNER An owner, owner_group, or ACL attribute value</font><br><font size="2" face="Courier New"> can not be translated to local representation.</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">Hope this helps.</font><br><font color="#1F497D" face="Calibri"> </font><br><font size="2" color="#1F497D" face="Arial">Neil Wilson Senior IT Practitioner</font><br><font size="2" color="#1F497D" face="Arial">Storage, Virtualisation and Mainframe Team IT Services</font><br><b><font size="2" color="#1F497D" face="Arial">Met Office </font></b><font size="2" color="#1F497D" face="Arial">FitzRoy Road Exeter Devon EX1 3PB United Kingdom</font><br><font color="#1F497D" face="Calibri"> </font><br><b><font face="Calibri">From:</font></b><font face="Calibri"> gpfsug-discuss-bounces@spectrumscale.org <gpfsug-discuss-bounces@spectrumscale.org> </font><b><font face="Calibri">On Behalf Of </font></b><font face="Calibri">Oesterlin, Robert</font><b><font face="Calibri"><br>Sent:</font></b><font face="Calibri"> 18 June 2018 16:54</font><b><font face="Calibri"><br>To:</font></b><font face="Calibri"> gpfsug main discussion list <gpfsug-discuss@spectrumscale.org></font><b><font face="Calibri"><br>Subject:</font></b><font face="Calibri"> [gpfsug-discuss] CES-NFS: UID and GID resolution</font><br><font face="Calibri"> </font><br><font face="Calibri">Can anyone tell me why I’m not seeing the correct UID/GID resolution from CES? Configured with LDAP authentication, and this appears to work correctly.</font><br><font face="Calibri"> </font><br><font face="Calibri">On my CES cluster (V4):</font><br><font face="Calibri"> </font><br><font face="Courier">[robert_oesterlin@unv-oester robert_oesterlin]$ ls -l</font><br><font face="Courier">total 3</font><br><font face="Courier">-rw-r--r-- 1 nobody nobody 15 Jun 18 11:40 junk1</font><br><font face="Courier">-rw-r--r-- 1 nobody nobody 4 Oct 9 2016 junk.file</font><br><font face="Courier">-rw-r--r-- 1 nobody nobody 1 May 24 10:44 test1</font><br><font face="Courier"> </font><br><font face="Calibri">On my CNFS cluster (V3)</font><br><font face="Calibri"> </font><br><font face="Courier">[root@unv-oester2 robert_oesterlin]# ls -l</font><br><font face="Courier">total 0</font><br><font face="Courier">-rw-r--r-- 1 robert_oesterlin users 15 Jun 18 11:40 junk1</font><br><font face="Courier">-rw-r--r-- 1 robert_oesterlin users 4 Oct 9 2016 junk.file</font><br><font face="Courier">-rw-r--r-- 1 robert_oesterlin users 1 May 24 10:44 test1</font><br><font face="Courier"> </font><br><font face="Calibri"> </font><br><font face="Calibri">Bob Oesterlin</font><br><font face="Calibri">Sr Principal Storage Engineer, Nuance</font><br><font face="Calibri"> </font><tt><font size="2">_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"><br></font></tt><br><br><BR>
</body></html>