Date: Thu, 30 Jan 1997 12:19:59 -0800 (PST) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: Bruce Evans <bde@zeta.org.au> Cc: current@freebsd.org Subject: Re: nfs hang Message-ID: <Pine.BSF.3.95.970130121147.19079C-100000@opus.cts.cwu.edu> In-Reply-To: <199701301631.DAA15277@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
I had a similar hang with a -current from a few days ago. I v2 mounted the -current box's /usr from a releng_2_2 box and was in the middle of a cvs update on the -current machines /usr/src when everything stopped. I was still able to telnet to the current machine and access that file system ok, but the cvs process on the 2_2 machine was hung in an nfs state (that I don't remember at the moment :( Can you suggest a debugging strategy to help me pin this down further? When I flip things around and mount the cvs repository from 2_2 system to -current (i.e. -current now is client) I haven't seen any further hangs and I've thrashed that with at least 3 cvs updates of the source tree. Whether or not it matters the two machines have a crossover cable between two 100mb PCI ethernet nics. -Chris On Fri, 31 Jan 1997, Bruce Evans wrote: > mount -t nfs -o-3 localhost:/usr /mnt > cd /usr/writable-dir > iozone auto > # get bored with this and hit ^C > > caused iozone to hang on "nfsaio" and most or all further fs activity to > hang somewhere. nfs v2 seemed to work better but I didn't try it for as > long. > > Bruce >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970130121147.19079C-100000>