From owner-freebsd-current@FreeBSD.ORG Fri Jan 4 14:56:50 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 71049D7B for ; Fri, 4 Jan 2013 14:56:50 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 1DA077D8 for ; Fri, 4 Jan 2013 14:56:49 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1Tr8hU-0003F2-32>; Fri, 04 Jan 2013 15:56:48 +0100 Received: from e178036024.adsl.alicedsl.de ([85.178.36.24] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1Tr8hT-000BP6-VQ>; Fri, 04 Jan 2013 15:56:48 +0100 Message-ID: <50E6EDAE.9010908@zedat.fu-berlin.de> Date: Fri, 04 Jan 2013 15:56:46 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Rick Macklem Subject: Re: r245005M: NFSv4 usermapping not working anymore References: <416983367.1668162.1357306220561.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <416983367.1668162.1357306220561.JavaMail.root@erie.cs.uoguelph.ca> X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE1FA6F100C8E3CE763C93D9B" X-Originating-IP: 85.178.36.24 Cc: Current FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2013 14:56:50 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE1FA6F100C8E3CE763C93D9B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 01/04/13 14:30, schrieb Rick Macklem: > O. Hartmann wrote: >> Since yesterday's update and buildworld on two FreeBSD 10.0-CURRENT >> boxes, i realize a strange behaviour. I have one server exporting via >> NFSv4 several ZFS volumes. The UID mapping went pretty well so far, >> but >> with a reboot of yesterday (after a buildworld), files are seen with >> uid >> root:wheel and users are no longer seen. >> > You might want to check (ifconfig -a) and see that there is a mapping > for 127.0.0.1 for lo. That is what is used to do the upcall to nfsused > and some systems have had this missing recently. (I had the impression > that the problem was caused by r244678, which was reverted by r244989, > but maybe your system still has that issue.) >=20 > Here's basically how it works, which may help with diagnosing what is > going on: > - when the nfsuserd starts up, it pushes a DNS domain (usually the > hostname with the first component stripped off) plus a couple of > hundred mappings acquired via getpwent()/getgrent() into the kernel > cache. > (The easiest way to break it for all users is to have the wrong DNS > domain name. "man nfsuserd" gives you a command line option that can > override the default of using the hostname.) > - Then the nfsuserd waits for upcalls for cache misses and pushes > mappings for those requests into the kernel. > - The cache entries time out with a rather long default of 1hr. >=20 > To get entries, nfsused just uses the getpwent() and getgrent() libc > calls, so it depends on whatever you have configured for that via > /etc/nsswitch.conf. >=20 > I'll grab a new kernel and do a quick test, to see if it works ok for m= e. > (The most recent commit related to this is r240720, which added support= > to the client for numeric uids/gids in the string on the wire. This ch= ange > should not have affected the server.) >=20 > Good luck with it, rick >=20 >> The server and client in question are >> >> server: FreeBSD 10.0-CURRENT #2 r245005M: Thu Jan 3 20:25:00 CET 2013 >> client: FreeBSD 10.0-CURRENT #2 r245005M: Thu Jan 3 20:27:25 CET 2013 >> >> I think this is not supposed to be that way. Another box, our lab's >> server, doesn't show this phenomenon (but at the moment I have only >> the >> opportunity to check with a FreeBSD 9.1-STABLE client). This specific >> server is >> >> server-1: FreeBSD 10.0-CURRENT #0 r244957: Wed Jan 2 12:06:13 CET 2013= >> >> By the way, can someone give me a hint why some boxes show up with an >> attached "M" to the SVN revision number (like r245005M)? >> >> Thanks, >> >> oh Me stupid killed the nfsuserd=3D"YES" entry in rc.conf on the client side= ! So, by starting it again, everything works as before and expected. Many thanks for the quick response! Oliver --------------enigE1FA6F100C8E3CE763C93D9B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJQ5u2vAAoJEOgBcD7A/5N8yngIAMigBSnTb5uH/GdalzwhOs0Q iglQB7wWuF47YFhSX64QjC2nwUnUV8SwybUS5Z30S2ob4RJNCkPGv7Effc4qi5a3 bR5YoFRZiJJg5apM3aASsZcqpursRMEl3dI2rd8TYHxhJHgES0f3hK8pQ13imoWx dYULGPujOGQ/Yo0lVNA8lR6L/Z7TZXvfib5tU9jX11d2P3meiMKpHGkcjJZ25JGl m2WyYxRGlW1wdo5p78YK0b4eS8Fb5FFZRN6A5Fgfe2yk1e8/0Bs9w/TxKa2v9ks7 4aZEqIzWIOOmOYyrOmbDp8J/5o1EEya1HMTYiIz0f1yFrxzp/kotqKfci6xmcbU= =UCaJ -----END PGP SIGNATURE----- --------------enigE1FA6F100C8E3CE763C93D9B--