Date: Sat, 6 Feb 1999 02:01:36 +0100 (MET) From: "D. Rock" <rock@wurzelausix.CS.Uni-SB.DE> To: current@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr Message-ID: <199902060101.CAA04062@vodix.aremorika>
next in thread | raw e-mail | index | archive | help
Matt wrote: > This is very odd. This is the approximate backtrace that I get > when I throw my test machine into DDB: [..] > What is happening is that I am doing a 'make installworld' on my > test machine with / and /usr NFS V3 mounted R+W. I also have come to the conclusion that NFSv3 is badly broken. I switched all my R/W mounts back to NFSv2 and I am happy again. I can do a full "make relase" with an NFS mounted chroot directory with no problems, while I have seen many problems with v3 mounts. One thing to lock up the system (probably only the filesystem code, I can still switch virtual screens with Alt+Fx, but getty cannot start /usr/bin/login) if I mount NFSv3 with the -l flag. I tried to track down some of the problems doing a network snoop and noticed something interesting: NFSv3 seems to produce more than twice the packets during file write than NFSv2 Is this true. There are many more getattr() calls with NFSv3 than with NFSv2. Since my NFS server exports one filesystem exclusively to one FreeBSD machine (which is a little short on disk space), I also tried some tricks for speedup. I just mounted one big file, vnconfig'd, newfs'd it and mounted it via UFS. But unfortunately the machine panic'd really fast during filesystem activity. My tests on this are 3-4 months old though, I will give it another try. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902060101.CAA04062>