Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Dec 1998 17:00:55 -0700 (MST)
From:      "David G. Andersen" <danderse@cs.utah.edu>
To:        Alfred Perlstein <bright@hotjobs.com>
Cc:        spork <spork@super-g.com>, Bernd Walter <ticso@cicely.de>, Kevin Day <toasty@home.dragondata.com>, hackers@FreeBSD.ORG
Subject:   Re: NFS thoughts
Message-ID:  <13941.42539.360724.653774@torrey.cs.utah.edu>
In-Reply-To: Alfred Perlstein's message of Mon, December 14 1998 <Pine.BSF.4.05.9812141150391.27793-100000@bright.fx.genx.net>
References:  <Pine.BSF.4.00.9812141110220.28944-100000@super-g.inch.com> <Pine.BSF.4.05.9812141150391.27793-100000@bright.fx.genx.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Lo and Behold, Alfred Perlstein said:
> > 
> > I also haven't seen the "I've mounted soft and intr, yet things still
> > hang" behaviour using version 2 and udp.  Any consensus on that?
> 
> why would you mount _both_ soft and intr? to me they seem mutually
> exclusive.
> 
> 'intr' allows you to intrupt a hung NFS proc so that it recives a
> transient error on a filesystem call, the process will hang forever unless
> NFS comes back, or you ^C it
> 
> 'soft' automates that with a timeout however signals won't work, but after
> some time the process will unhang and get an error on the filesystem call.
> 
> Are you trying to get an auto-timeout like mount with that ability to ^C?
> 
> generally intr is best, the idea of many processes timeing out on NFS
> mounts should the server crash, makes my stomach turn.

   Note that until kern/8732 is fixed, this can be dangerous (hang
your machine dangerous).  Mounting with 'intr' and then sending
SIGINTR while a process is attempting to flush a dirty block will
cause the machine to wedge.

   -Dave

--
work: danderse@cs.utah.edu                     me:  angio@pobox.com
      University of Utah                            http://www.angio.net/
      Department of Computer Science

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13941.42539.360724.653774>