Re: network storage solutions

["Jeffrey B. Layton" <laytonjb@bellsouth.net>]

Josip Loncaric wrote:

> Glen Kaukola wrote:
>
>> Greg Lindahl wrote:
>>
>>> There are soft and hard mounts, and there are interruptable mounts
>>> ("intr" -- check out "man nfs").
>>>
>>> A hard mount will never time out. If you make it interruptable, then
>>> the user can choose to ^C. This is the safe option.
>>>  
>>>
>>
>> You know, I thought that's how it was supposed to work too.  I do use 
>> the intr option, but even with that option, when a nfs drive is down, 
>> and something like a df command gets stuck, hitting ctrl-c doesn't 
>> seem to do a thing.  All I can ever do is just kill my xterm or 
>> whatever.  
>
>
> We've had similar problems while I was at ICASE.  "Hard" mounts would 
> lock up client processes (even unmount) when the NFS server went down, 
> but "soft" mounts were "too soft" for some of our users.  A reasonable 
> solution is to "harden" your soft mounts by insisting on longer major 
> timeouts, as in "retrans=15" (the default is 3). 


I still think this is dangerous. With soft mounts you can
still get silent data corruption despite the longer timeouts.
Chuck, do you agree?

Jeff

>
>
> Sincerely,
> Josip
>
> P.S.  Our NFS servers virtually never went down, except due to 
> hardware problems or service, so indefinite retransmissions were 
> highly undesirable.
>




-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs