From owner-freebsd-stable@freebsd.org Sun Jun 11 22:54:09 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B5CFBEED7F for ; Sun, 11 Jun 2017 22:54:09 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0370F79C4B for ; Sun, 11 Jun 2017 22:54:08 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7FEFABEED79; Sun, 11 Jun 2017 22:54:08 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F7F9BEED78; Sun, 11 Jun 2017 22:54:08 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D85B879C47; Sun, 11 Jun 2017 22:54:06 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v5BMs2fk003670; Sun, 11 Jun 2017 22:54:05 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v5BI8ugc001605; Sun, 11 Jun 2017 11:08:56 -0700 (PDT) (envelope-from david) Date: Sun, 11 Jun 2017 11:08:56 -0700 From: David Wolfskill To: Michael Butler Cc: stable@freebsd.org Subject: Re: post ino64: lockd no runs? Message-ID: <20170611172022.GA3184@albert.catwhisker.org> Reply-To: stable@freebsd.org Mail-Followup-To: stable@freebsd.org, Michael Butler MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline In-Reply-To: <24b27f3e-f91b-553d-f2c1-e876608e0baf@protected-networks.net> User-Agent: Mutt/1.8.2 (2017-04-18) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jun 2017 22:54:09 -0000 --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 04, 2017 at 08:57:44AM -0400, Michael Butler wrote: > It seems that {rpc.}lockd no longer runs after the ino64 changes on any > of my systems after a full rebuild of src and ports. No log entries > offer any insight as to why :-( >=20 > imb I don't tend to use NFS on my systems that are running head, so I haven't had occasion to test this as stated. However, I just completed my weekly update of the "prooduction" systems here at home, running stable/11. And I find that lockd seems to be ... claiming that all is well, but declining to run (for long). To the best of my knowledge, that was not the case until this last update, which was from: FreeBSD albert.catwhisker.org 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #316 = r319566M/319569:1100514: Sun Jun 4 03:54:41 PDT 2017 root@freebeast.c= atwhisker.org:/common/S1/obj/usr/src/sys/ALBERT amd64 to FreeBSD albert.catwhisker.org 11.1-BETA1 FreeBSD 11.1-BETA1 #322 r319823M/= 319823:1100514: Sun Jun 11 03:56:10 PDT 2017 root@freebeast.catwhisker.= org:/common/S1/obj/usr/src/sys/ALBERT amd64 The "glaringly obvious" symptom in my case is that I am now unable to (directly) save an email message from within mutt(1) by appending it to an NFS-resident file. (Saving it to a local file, then using cat(1) to append that to the NFS- resident file & removing the local copy works....) After a few variations on a theme of: albert(11.1)[5] sudo service lockd restart lockd not running? Starting lockd. albert(11.1)[6] echo $? 0 albert(11.1)[7] service lockd status lockd is not running. I finally(!) thought to ask ktrace what's going on (as tailing /var/log/messages was completely unproductive, even after enabling rc_debug). So I tried: "sudo ktrace -di service lockd restart"; upon exanimation of the output of kdump(1), I see that the trace ends with: ... 2811 rpc.lockd NAMI "/var/run/logpriv" 2786 sh CALL read(0xa,0x627fc0,0x400) 2786 sh GIO fd 10 read 0 bytes "" 2811 rpc.lockd RET connect 0 2786 sh RET read 0 2811 rpc.lockd CALL sendto(0x3,0x7fffffffe2c0,0x27,0,0,0) 2786 sh CALL exit(0) 2811 rpc.lockd GIO fd 3 wrote 39 bytes "<30>Jun 11 15:43:10 rpc.lockd: Starting" 2811 rpc.lockd RET sendto 39/0x27 2811 rpc.lockd CALL sigaction(SIGALRM,0x7fffffffec20,0) 2811 rpc.lockd RET sigaction 0 2811 rpc.lockd CALL nlm_syscall(0,0x1e,0x4,0x801015040) 2811 rpc.lockd RET nlm_syscall -1 errno 14 Bad address 2811 rpc.lockd CALL sigprocmask(SIG_BLOCK,0x800830c78,0x7fffffffea40) 2811 rpc.lockd RET sigprocmask 0 2811 rpc.lockd CALL sigprocmask(SIG_SETMASK,0x800830c8c,0) 2811 rpc.lockd RET sigprocmask 0 2811 rpc.lockd CALL sigprocmask(SIG_BLOCK,0x800830c78,0x7fffffffe5b0) 2811 rpc.lockd RET sigprocmask 0 2811 rpc.lockd CALL sigprocmask(SIG_SETMASK,0x800830c8c,0) 2811 rpc.lockd RET sigprocmask 0 2811 rpc.lockd CALL sigprocmask(SIG_BLOCK,0x800830c78,0x7fffffffe5b0) 2811 rpc.lockd RET sigprocmask 0 2811 rpc.lockd CALL sigprocmask(SIG_SETMASK,0x800830c8c,0) 2811 rpc.lockd RET sigprocmask 0 2811 rpc.lockd CALL sigprocmask(SIG_BLOCK,0x800830c78,0x7fffffffe5b0) 2811 rpc.lockd RET sigprocmask 0 2811 rpc.lockd CALL sigprocmask(SIG_SETMASK,0x800830c8c,0) 2811 rpc.lockd RET sigprocmask 0 2811 rpc.lockd CALL exit(0x1) Then, when I tried to send this message, I started getting more whines =66rom mutt(1). I finall gave up and rebooted from the previous environment: FreeBSD albert.catwhisker.org 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #316 = r319566M/319569:1100514: Sun Jun 4 03:54:41 PDT 2017 root@freebeast.c= atwhisker.org:/common/S1/obj/usr/src/sys/ALBERT amd64 and lockd is running: albert(11.1-P)[2] service lockd status lockd is running as pid 629. albert(11.1-P)[3]=20 so mutt(1) is not pitchng a hisssy-fit every time I try to save or send a message. In light of the above, I have Bcced: this message to current@ (where the thread originated) and sent it (and set replies) to stable@. I have a test system, last updated to stable/11 as of mid-October last year; lockd was running on it, as well (which is why I tried going back to last week's image). I'm happy to update it to points where lockd may be broken, if it might help figure out what's broken and how to fix it. Peace, david --=20 David H. Wolfskill david@catwhisker.org Looking forward to telling Mr. Trump: "You're fired!" See http://www.catwhisker.org/~david/publickey.gpg for my public key. --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZPYc3XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XN3oIAM28Fz1XHx5Y8ZOj3XFVh3Ik 7a54Z972WwfLwSCuYuk+U7lDurBMuBklQHVTOy7+rcghZMLAbuvXRUwkjF7lxErj nbwtxzy/z2xXKdAAxuTxq4OXZvwH/eVD1Pcywu9tA4EKjJeoivFEOmFbVJ7qSyJH W9hQLdZBp9jcGxZyuoGPRkW8EbDLKbybO4VjxsYhf/nkaNrNJoG0BOHLjSlnD2kB rgfjH4PSlHeHEb4IsKHsusLEgRDMxgHIKmw1FkgIQBkfNouV4jUhmUqMUSHk7+dd oCEo2Z6cS5xCU+h1R1ztZvNIJNMJYNvnYhrjwYo3O2RUlwnxO8x1K4u7OK5JEpE= =eWJh -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7--