[1423] in linux-net channel archive

home help back first fref pref prev next nref lref last post

Re: Strange behaviour with NFS

daemon@ATHENA.MIT.EDU (Robert L Krawitz)
Fri Nov 24 16:56:52 1995

Date: Fri, 24 Nov 1995 08:30:52 -0500
From: Robert L Krawitz <rlk@tiac.net>
To: linux-net@vger.rutgers.edu
In-reply-to: <199511232037.OAA18238@khijol> (khijol!erc@vger.rutgers.edu)


   Um, this isn't limited to Linux - Solaris also exhibits this
   behavior.  When one of our NFS servers dumps the big one, we often
   have to reboot the clients.  Someone suggested that the mounts be
   changed from 'hard' to 'soft', but I don't think this would make
   any difference.

Soft NFS mounts are dangerous because I/O operations will fail on any
timeout.  This can cause file corruption (if programs don't check
return status), unnecessary program failures, and possibly nasty
program aborts if paging in a binary fails.

Mounting hard and interruptable is generally the best bet.  Rebooting
the NFS server also generally brings things back to life.

-- 
Robert Krawitz <rlk@tiac.net>           http://www.tiac.net/users/rlk/

Member of the League for Programming Freedom  -- mail lpf@uunet.uu.net
Tall Clubs International  --  tci-request@aptinc.com or 1-800-521-2512

home help back first fref pref prev next nref lref last post