Hi all, I recently noticed a problem in my network. I use some desktop machines there, two with Linux kernel (Debian and Fedora, both using Kernel 3.5) and a FreeBSD 9.0 (p4) machine. Some days ago, I updated the Debian machine from Kernel 3.2 to Kernel 3.5 (from the experimental branch, 3.5-trunk-amd64; I hope you aren't bothered by the Linux-specific parts). Running 3.2, the FreeBSD machine was able to mount an NFSv4 share on the Debian/k3.2 system properly, with UIDs etc (using nfsuserd on FreeBSD, rpc.idmapd on GNU/Linux). Since I updated to Kernel 3.5, the FreeBSD machine only shows 32767 as UID/GID for all files. `chown` works (even though without any effect, but without error, so nfsuserd works). This behavior occurred also when using Linux Kernel 3.3 or 3.4 on the Debian (server) machine. With the Fedora 17 machine (also Kernel 3.5, and the same users in /etc/passwd, of course), the same operation works without this errors, showing the UIDs and GIDs I want it to. 1. Am I right on this list, or should I ask first on a Linux-oriented list/forum? 2. Has anyone else noticed this or similar behaviour? 3. Any ideas about fixes, workarounds, known bugs? -- norbert
Norbert Aschendorff wrote:> Hi all, > I recently noticed a problem in my network. I use some desktop > machines > there, two with Linux kernel (Debian and Fedora, both using Kernel > 3.5) > and a FreeBSD 9.0 (p4) machine. > Some days ago, I updated the Debian machine from Kernel 3.2 to Kernel > 3.5 (from the experimental branch, 3.5-trunk-amd64; I hope you aren't > bothered by the Linux-specific parts). > Running 3.2, the FreeBSD machine was able to mount an NFSv4 share on > the > Debian/k3.2 system properly, with UIDs etc (using nfsuserd on FreeBSD, > rpc.idmapd on GNU/Linux). Since I updated to Kernel 3.5, the FreeBSD > machine only shows 32767 as UID/GID for all files. `chown` works (even > though without any effect, but without error, so nfsuserd works). > This behavior occurred also when using Linux Kernel 3.3 or 3.4 on the > Debian (server) machine. With the Fedora 17 machine (also Kernel 3.5, > and the same users in /etc/passwd, of course), the same operation > works > without this errors, showing the UIDs and GIDs I want it to. > > 1. Am I right on this list, or should I ask first on a Linux-oriented > list/forum? > 2. Has anyone else noticed this or similar behaviour? > 3. Any ideas about fixes, workarounds, known bugs? >Sounds like rpc.imapd isn't working correctly for that Debian system. To check what's going on, capture some traffic (like an "ls -l" for a directory) and then look at it in wireshark and see what is going on the wire. The owner and owner_group names in the attributes should look like <user>@<your.dns.domain>. Usually the problem is that the domain name isn't set correctly. (Typically, Linux systems default to "my.domain" or something like that.) rick> -- norbert > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org"
I already had a problem with this, but this is fixed: 1. The hostnames are correct 2. in the debian /etc/idmapd.conf, the right domain name is specified 3. The names are transmitted correctly -- tested with Wireshark. If the problem was wrong domain names, I had found it because I always take a look at the traffic if I have a problem with network stuff. And (as mentioned), I already had the name problem and therefore the knowledge how to detect and fix it. Nevertheless, thank you for your answer.
It looks as if the problem is related to this bug which shows the exactly same symptoms (if you look at the package dumps). It's also Kernel 3.3 with which it also begun here. And with kernel 3.1, it works (same here). --> https://bugzilla.novell.com/show_bug.cgi?id=756897 I don't know what's the problem anyway. Maybe changed kernel interfaces?