Date: Sat, 6 Dec 1997 14:00:29 -0500 (EST) From: spork <spork@super-g.com> To: Sean Eric Fagan <sef@kithrup.com> Cc: bugs@freebsd.org Subject: Re: Is this a bug? Message-ID: <Pine.BSF.3.96.971206135737.9172A-100000@super-g.inch.com> In-Reply-To: <199712050436.UAA27559@kithrup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've seen this many times; if you don't properly umount the nfs stuff and a machine disappears, it's hell to get them talking again. I have a few machines sitting around waiting to do something, so if anyone would like me to cvsup them and nfs them together and try to break things, I'm game. I should have two available for use for about two weeks. Charles Sprickman spork@super-g.com ---- "I'm not a prophet or a stone-age man Just a mortal with potential of a superman I'm living on" -DB On Thu, 4 Dec 1997, Sean Eric Fagan wrote: > Today, my development system paniced (oops; that's what I get for trying a > kernel change :)). > > After I rebooted, the interaction between the development system ("garth") > and my server ("kithrup") was weird... first of all, the NFS mount of a > filesystem from kithrup didn't work -- garth said that the NFS server wasn't > responding. It had never done that before. > > After it came up, I logged in -- and couldn't log in from garth to kithrup > via kerberos. I could, however, via normal rlogin and via encrypted kerberos > login. > > Poking around a bit, it seemed that the reason I couldn't do the klogin was > because there was still the old klogin from garth to kithrup (that had been > active when the panic happened). Doing "kill -HUP" on that PID cleared it > up, and I could do the klogin. > > I am assuming that garth's NFS mount is failing because there is a > connection still present on kithrup -- > > Active Internet connections > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp 0 0 kithrup.shilp garth.kithrup.1024 ESTABLISHED > > (obviously, I'm using NFS-ver-TCP). > > garth is running a 2.2-GAMMA kernel, and kithrup is running 2.2.5-STABLE > kernel (entire sources updated 12 days ago). > > Anyone have any ideas about what's going on, and/or what to do? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971206135737.9172A-100000>