From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 00:04:49 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 848F4106566C for ; Tue, 21 Aug 2012 00:04:49 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3D69D8FC0A for ; Tue, 21 Aug 2012 00:04:48 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EAK/PMlCDaFvO/2dsb2JhbABFhgG1YYIgAQEBBAEBASArIAsbGAICDRkCKQEJJgYIBwQBHASHbAumRpMdgSGKBIVmgRIDkyWCK4EUjn6CfYFF X-IronPort-AV: E=Sophos;i="4.77,800,1336363200"; d="scan'208";a="176042852" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 20 Aug 2012 20:04:49 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 32D7DB4036; Mon, 20 Aug 2012 20:04:48 -0400 (EDT) Date: Mon, 20 Aug 2012 20:04:48 -0400 (EDT) From: Rick Macklem To: Norbert Aschendorff Message-ID: <672849509.877573.1345507488192.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <50325008.200@yahoo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-stable@freebsd.org Subject: Re: Problem with Linux >= 3.3 as NFSv4 server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 00:04:49 -0000 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 @. 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"