Re: NFS client names not mapping

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 1/29/22 8:25 PM, Gordon Messmer wrote:
On 1/29/22 17:20, Ed Greshko wrote:

In the initial posting by Robert he wrote:
"I have no nfs-idmapd service running"


Right, but on recent kernels, the client doesn't use rpc.idmapd, it uses "nfsidmap".  The fact that rpc.idmapd isn't running doesn't really tell us anything.


"all users and groups in an NFS mounted filesystem are mapped to "nobody" even though the names and
numeric IDs are the same on the server and client"

So, I don't know why we're going down this path.

Jan 28 21:19:14 fedora.local nfsidmap[2461]: nss_getpwnam: name 'root@local' does not map into domain 'localdomain'


Right, that log entry indicates that idmap is being used on his system. That might mean that the server doesn't support NFSv4 without idmap.  Or it might mean the client was configured to enable idmapping.

Without knowing which, we don't really know the right thing to do, except to set the client's domain to match the servers, so that idmapping works as expected.

If I could find any way to set the client's domain name, I would. Nothing I try has any effect on the domain name.
When I try to set a FQDN with hostnamectl, then "hostnamectl" (with no arguments) shows that FQDN as the static hostname, but "hostname --fqdn" responds with "hostname: Name or service not known", and "mount -t nfs ..." causes the various "... does not map into domain 'localdomain'" messages to be logged.

With a test system following those first two statement, I've go no problems.


I would imagine that idmapping is disabled on your client (and supported by your server).

Check the value of /sys/module/nfsd/parameters/nfs4_disable_idmapping on your NFS server, if it's Linux.  And check the value of /sys/module/nfs/parameters/nfs4_disable_idmapping on the client.

On the server:
[plugh-3g ~]# cat /sys/module/nfsd/parameters/nfs4_disable_idmapping
N

--
Bob Nichols     "NOSPAM" is really part of my email address.
                Do NOT delete it.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux