From owner-freebsd-stable@freebsd.org Sun Jun 11 18:48:29 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 BD7F0D8C8ED for ; Sun, 11 Jun 2017 18:48:29 +0000 (UTC) (envelope-from cy.schubert@komquats.com) 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 9FA3E72AE6 for ; Sun, 11 Jun 2017 18:48:29 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9EC3ED8C8EC; Sun, 11 Jun 2017 18:48:29 +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 9E48BD8C8EB for ; Sun, 11 Jun 2017 18:48:29 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7252872AE5 for ; Sun, 11 Jun 2017 18:48:29 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id K7uNdxNkIETFpK7uOdp6sV; Sun, 11 Jun 2017 12:48:21 -0600 X-Authority-Analysis: v=2.2 cv=dZbw5Tfe c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=kj9zAlcOel0A:10 a=LWSFodeU3zMA:10 a=JAf30KXuAAAA:8 a=capo1NdyAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=ultTwZIKIEoFYwmveK8A:9 a=CjuIK1q_8ugA:10 a=v2312BZ5C20A:10 a=GEL62FyrTCmHtEug2d3R:22 a=9rL3IfpHMVDODJIA5_Zr:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 7CEFEC35 for ; Sun, 11 Jun 2017 11:48:19 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id v5BIl4Jw011214 for ; Sun, 11 Jun 2017 11:47:04 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201706111847.v5BIl4Jw011214@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: stable@freebsd.org Subject: Re: post ino64: lockd no runs? In-Reply-To: Message from David Wolfskill of "Sun, 11 Jun 2017 11:12:25 -0700." <20170611172022.GA3184@albert.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Jun 2017 11:47:04 -0700 X-CMAE-Envelope: MS4wfLvtda9Mpi+1o5kYVSMvCI6QhMiuUOxyeQKopWxCC7PHSbgs7/W7u/ORH0Xom/jPFNxirKklhRlq8q94OFjtmA8NysSCL1Pfm86zJH+0s7ZWMnnFizQZ aBd+dfZhq2UfhN9KVf3FWe1cXYOKazmUj6e2L7UjrxTMR7I3SIXC1oO5J5f1Wu/5jXSLTQK5qD/MFg== 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 18:48:29 -0000 In message <20170611172022.GA3184@albert.catwhisker.org>, David Wolfskill write s: > > --0eh6TmSyL6TZE2Uz > 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. I'm running lockd on recent -CURRENT systems. No issues so far. Locking works as expected. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.