Subject: Re: (long) NFS misbehaving under -current?
To: None <firstname.lastname@example.org>
From: Christoph Badura <email@example.com>
Date: 10/08/1998 17:54:34
kre@munnari.OZ.AU (Robert Elz) writes:
>I see the same, and I don't use amd (on NetBSD) at all, just NFS mounts
>from fstab. Accesses to filesystems mounted as "soft" never time out,
>nor do accesses ever complete after the server returns if they have
>hung while the server was down. Interruptable mounts can be interrupted
>just fine though. All this suggests that there's a problem with the
>timers in the NFS code, or the way they're handled.
I saw this problem in 1.1 too and asked Rick Macklem about hit. He thought
that maybe the NFS code doesn't notice that the socket isn't connected
anymore. Obviously, this is only for TCP mounts.
I haven't researched that since, so this is just a wild guess.