Date: Tue, 09 Apr 2019 15:36:02 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: freebsd-current@freebsd.org, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, David Boyd <David.Boyd49@twc.com> Subject: Re: lsof hangs with latest 13.0-CURRENT snapshot Message-ID: <3A0D37FF-317F-45CE-88E5-64E4642BACD6@cschubert.com> In-Reply-To: <201904091941.x39JfY49061789@gndrsh.dnsmgr.net> References: <201904091941.x39JfY49061789@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On April 9, 2019 12:41:34 PM PDT, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> wrote: >> On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: >> > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 >to >> > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from >> > > packages) >> > > hangs. >> > > >> > > This is true for bare metal installs and virtual machine >installs. >> > > >> > > How to recreate: >> > > >> > > Install FreeBSD-13.0-CURRENT-amd64-20190404-r345863 snapshot. >> > > >> > > as root: lsof /sbin/init >> > > >> > > By running command with -b option, this error is displayed: >> > > >> > > lsof: status error on /sbin/init: Resource temporarily >unavailable >> > > >> > > The return code is 1. >> > > >> > > This probably requires adjustment to lsof, but only the FreeBSD >> > > snapshot changed, so I'll start here. >> > >> > Where did you get your lsof binary from? >> > >> > lsof has internal knowledge of kernel data structures >> > and must be compiled to match the running system. >> > >> > >> > > Thanks. >> > > David Boyd. >> >> >> lsof was installed via pkg install from pkg.freebsd.org. > >That does not work well on ^head or for that mater any snapshot, >as I said, lsof has internal knowledge of kernel data structures >and must match the running kernel for it to work. > >It should be complaining about a version mismatch, but perhaps >it was compiled recently enough that these are matching, but >there is still a datastruct that changed. Version mismatches are innocuous. I tend to use it on -current until it breaks, rebuilding it as needed. Rebuilding is a good time to update the port while I'm at it. This policy has served me well over the years. -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A0D37FF-317F-45CE-88E5-64E4642BACD6>