[comp.protocols.nfs] NFS I/O error returns

lyndon@cs.AthabascaU.CA (Lyndon Nerenberg) (12/06/89)

Does anyone have a compendium of "typical" errors returned when an
I/O operation to an NFS filesystem fails? I'm particularly interested
in differences between soft and hard mounted remote filesystems, and
whether the (Unix) NFS filesystem implementation differentiates
between "soft" (retryable) and "hard" (physical device) errors.

-- 
Lyndon Nerenberg  VE6BBM / Computing Services / Athabasca University
  {alberta,decwrl,lsuc}!atha!lyndon || lyndon@cs.AthabascaU.CA

                  The Connector is the Notwork.

LUBKT@vax1.cc.lehigh.edu (12/07/89)

In article <1292@atha.AthabascaU.CA>, lyndon@cs.AthabascaU.CA (Lyndon Nerenberg) writes:
> .....................................  I'm particularly interested
> in differences between soft and hard mounted remote filesystems, and
> whether the (Unix) NFS filesystem implementation differentiates
> between "soft" (retryable) and "hard" (physical device) errors....


I do not understand the way you defined soft or hard mounts as
"retryable" and "physical device" respectively. And, I do not think
that is appropriate.

As a general practice, soft mount is never tried if the mounted file
system is read-write. If the network error occurs and the file system
is mounted soft, and if you have some data on the mounted file system
unsaved, then you have a chance of losing some/all of your data. If
the file system is mounted "hard", the attempt (to save, taking the
bove example) continues untils the network error is resolved. As you
can see, this can lead your client machine to hang if server does not
respond soon. If the server responds after sufficiently long time, you
may get an error "Stale File handle" if you try to access the file
system. In that case, you will have to dismount the file system and
then, re-mount the it again. Usually, read-only file systems are
mounted soft.

Well, while addressing the NFS question, does any one know how to
mount with interrupt enabled (hitting control-C should abort the
mount). I have heard it is common for Sun or Vax machines. Does any
one know if this can be done for Apple Unix (A/UX), version 1.1?

 Binod Taterway, User Consultant, Lehigh University Computing Center
 Lehigh University, Bethlehem, PA 18015.         Tel: (215) 758-3984
 E-mail: LUBKT@vax1.cc.lehigh.EDU (Internet),     BT00@lehigh.BITNET