From: James Pearson <james-p@moving-picture.com>
Subject: Questions about NFS over TCP
Date: Wed, 23 Apr 2003 11:30:48 +0100
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <3EA66B58.2B1E4A45@moving-picture.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: nfs@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

I've just started experimenting with NFS over TCP and have a few
questions:

The Linux NFS-HOWTO states that:

> The disadvantage of using TCP is that it is not a stateless
> protocol like UDP. If your server crashes in the middle of a
> packet transmission, the client will hang and any shares will
> need to be unmounted and remounted.

I take this to mean that any client that is not actively accessing data
on the server at the time of a crash will be OK after the server
reboots?

As, I believe, some other OS's use NFS over TCP by default, how do they
get round this problem (or not)?

What is the 'best' way to get mount to try an TCP mount first - if that
fails, then try a UDP mount - I had a look at the mount source and
hacked in something to do this if the options -o tcp,udp are given - my
hack is very simple, if the TCP mount fails (for whatever reason), the
try a UDP mount - however, I don't know how 'safe' this is ...

Thanks

James Pearson


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs