Re: NFS hang + umount -f: better behaviour requested.

[Peter Staubach <staubach@redhat.com>]

Robin Lee Powell wrote:
> On Tue, Aug 21, 2007 at 01:01:44PM -0400, Peter Staubach wrote:
>   
>> John Stoffel wrote:
>>     
>>> Robin> I'm bringing this up again (I know it's been mentioned here
>>> Robin> before) because I had been told that NFS support had gotten
>>> Robin> better in Linux recently, so I have been (for my $dayjob)
>>> Robin> testing the behaviour of NFS (autofs NFS, specifically) under
>>> Robin> Linux with hard,intr and using iptables to simulate a hang.
>>>
>>> So why are you mouting with hard,intr semantics?  At my current
>>> SysAdmin job, we mount everything (solaris included) with
>>> 'soft,intr' and it works well.  If an NFS server goes down,
>>> clients don't hang for large periods of time. 
>>>       
>> Wow!  That's _really_ a bad idea.  NFS READ operations which
>> timeout can lead to executables which mysteriously fail, file
>> corruption, etc.  NFS WRITE operations which fail may or may not
>> lead to file corruption.
>>
>> Anything writable should _always_ be mounted "hard" for safety
>> purposes.  Readonly mounted file systems _may_ be mounted "soft",
>> depending upon what is located on them.
>>     
>
> Does write + tcp make this any different?

Nope...

TCP may make a difference if the problem is related to the network
being slow or lossy, but will not affect anything if the server
is just slow or down.  Even if TCP would have eventually gotten
all of the packets in a request or response through, the client
may time out, cease waiting, and corruption may occur again.

       ps