On Tue, 3 Jan 2006, Sebastian Rother wrote:
> Hi everybody,
>
> I've a question related to NFS.
>
> I#ve 2 PCs at home. One is a Server (NFS) running 3.8 and the other is my
> workstation running current.
>
> Server provides a NFS-Share. Let's call it /nfs
> Workstation mounts the NFS-Share into /mnt/nfs
>
> If the Workstation calculates something and I power off the Server to
> save some energy and power on this system later the workstation
> will NOT be able to read/write anything to the NFS-Share.
> It will simply report:
>
> nfs server server:/nfs: not responding
>
> The workstation will not hang but the shell where I did e.g.
> ls /mnt/nfs hangs and can't get killed anyway.
>
> Even a "sudo umount -f /mnt/nfs" stoped working and reported the same
> error-message.
>
> I would say it's a Bug in the NFS-Implementation because it should
> handle such things.
>
> My fstab-entry is:
> server:/nfs on /mnt/nfs type nfs (nodev, nosuid, v3, tcp, soft, intr,
> timeo=100)
>
> So there IS a timeout specified but it wont help.
> The only solution is to reboot the workstation.
>
> So is this a Problem related to NFS or did I missed anything???
> It seams just during a "reboot" the timeout is noticed so after ~some
> seconds the machine will reboot.
>
> I've the same issues with an 3.8 Client so it shouldn't be
> current-related.
A workaround is probably not to use tcp. I use udp here (with standard
options), and my clients recover nicely after a server
powerdown/powerup.
-Otto
