From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: client apps not surviving nfsd restart
Date: Fri, 20 Aug 2004 15:55:47 +0200 [thread overview]
Message-ID: <412602E3.5040000@bio.ifi.lmu.de> (raw)
In-Reply-To: <20040820130246.GB12371@suse.de>
Olaf Kirch wrote:
> On Fri, Aug 20, 2004 at 02:12:15PM +0200, Frank Steiner wrote:
>
>> In the NFS howto I read that the disadvantage of nfs-over-tcp is that
>> "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 have never observed this behavior. TCP reconnect works just fine.
Hmm, ok. So the stales we saw might have been cause by some other
difference between SuSE 7.3 and 9.0. Could the lock manager be a
cause for this? With SuSE 7.3 we had everything mounted with "nolock".
Now with SusE 9.0 we use locks. Could that cause stales like we
experienced on /usr?
>
>
>>2) We are currently testing kernel 2.6.8.1. The nfs behaviour seems
>> to have changed in some ways. Running e.g. "find /" on a diskless
>> client with kernel 2.4 would just hang when the server rebootet
>> and later go on when the server was back.
>
>
> What does your exports table look like? Do you have network exports
> or other kinds of wildcarding? I have a report of nfsd/mountd not
> properly reloading the kernel's export table after a nfsd restart.
We are using netgroups. For testing I removed them and just left
entries for one diskless client, without any wildcards or group
but it does not make a difference (I rebooted client and server
with the new exports just to make sure...)
>
>
>> With 2.6.8.1, the find command will immediately abort and report
>> some stale nfs handles.
>
>
> Do you mean it will report ESTALE when the server goes down, or when
> it comes back up?
Immediately when the server goes down. "find" and "cp" immediately
abort and I'm back on the shell prompt.
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-20 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 12:12 client apps not surviving nfsd restart Frank Steiner
2004-08-20 13:02 ` Olaf Kirch
2004-08-20 13:55 ` Frank Steiner [this message]
2004-08-20 13:21 ` Olaf Kirch
2004-08-20 14:26 ` Frank Steiner
2004-08-20 13:25 ` Bernd Schubert
2004-08-20 14:34 ` Frank Steiner
2004-08-20 14:46 ` Olaf Kirch
2004-08-20 18:28 ` Hans-Peter Jansen
2004-08-20 15:31 ` mehta kiran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=412602E3.5040000@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.