Date: Tue, 13 Oct 1998 02:17:35 -0400 (EDT) From: Alfred Perlstein <bright@hotjobs.com> To: Dan Strick <dan@math.berkeley.edu> Cc: current@FreeBSD.ORG Subject: Re: -current NFS problem Message-ID: <Pine.BSF.4.05.9810130215040.13772-100000@porkfriedrice.ny.genx.net> In-Reply-To: <199810130405.VAA18347@math.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
this has been a problem for me sorta, if you are using UDP mounts to solaris boxen and seeing this try using tcp mounts instead. solaris _should_ allow that. you might want to try these options: tcp,nfsv3,intr,bg,rw in your /etc/fstab file or to your -o options then again i'm still having pine knock my system for a loop recently while deleting mail. so maybe, nfsv2 for mail and nfsv3 for ftp? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Mon, 12 Oct 1998, Dan Strick wrote: > I haven't reported this before because it is kind of hard to be > very specific about the cause and because I am under the impression > that people are aware of NFS problems in a general way. I am reporting > this now necause I believe this to be very important and I haven't > heard any discussion of this specific problem. > > There is some sort of NFS problem that causes processes to wedge > in a high priority (i.e. non-interruptable) wait state. I encounter > this problem whenever I use the ncftp2 program on a 3.0-SNAP or BETA > system to make copy of a FreeBSD release in a remotely mounted file > system. It doesn't happen immediately, but it always happens before > the copy is complete. The ncftp2 program just stops reporting any > progress and a ps shows it to be in a "disk" wait state. The ncftp2 > program is normally not killable and attempts (on the 3.0-SNAP or BETA > system) to examine the directory it was copying into also wedge in a > "disk" wait state. Eventually the entire 3.0-SNAP or BETA system > will wedge. I suspect the NFS problem, which initially is localized > to one file or directory, cascades through the automounter. > > The NFS server, a sun workstation running Solaris 2.5, does not > appear to be affected. The directory that is wedged on the > 3.0-SNAP or BETA FreeBSD system is visible and behaves normally > on the server even after the FreeBSD NFS client system locks up. > > The only (temporary) fix is to reboot the FreeBSD 3.0-SNAP or BETA > system and restart the ncftp2 program where it left off. Eventually > it will finish. I normally avoid the problem entirely by doing > my FreeBSD release copies on a 2.2.7-RELEASE system which never > hangs. > > Note: after a NFS wedge, I never find a partially written file. > The wedge always seems to happen "between" files. > > Dan Strick > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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?Pine.BSF.4.05.9810130215040.13772-100000>