From: Thomas Stockheim <tommi@bub-agema.de>
To: nfs@lists.sourceforge.net
Subject: Re: NFS problem - close to open cache consistency broken ?
Date: Thu, 15 Sep 2005 17:14:12 +0200 [thread overview]
Message-ID: <43298FC4.3080008@bub-agema.de> (raw)
In-Reply-To: <12528729.1126796454117.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net>
Lever, Charles wrote:
>>>peter, do you happen to know how the solaris NFS client
>>
>>behaves when an
>>
>>>application holds a file open like this?
>>>
>>>close-to-open is a convention, not a specification, so it's
>>
>>really up to
>>
>>>the client developers to implement what they think is right. i'm
>>>guessing that the Linux client is working as designed here. i'm not
>>>convinced it's very *convenient* behavior, though.
>>>
>>>
>>>
>>
>>Well, linux did not allways do this - same directory mounted
>>on an older
>>redhat with kernel 2.4.2 and its working fine.
>
>
> those ancient kernels don't support close-to-open. that was introduced
> around 2.4.20.
>
>
I don't know what model they had instead, but it worked better
for us. I've been running linux clusters for 5 years or so and
never had this problem before.
--
************************************************************************
**
** B&B-AGEMA GmbH
**
** Thomas Stockheim
** Juelicher Strasse 338
** D-52070 Aachen
** Germany
**
** Tel. (Zentrale): ++49-(0)241-56878-0
** Tel. (Durchwahl): ++49-(0)241-56878-31
** Fax.: ++49-(0)241-56878-79
** e-mail: <tommi@bub-agema.de>
** Internet: http://www.bub-agema.de
**
************************************************************************
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2005-09-15 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12528729.1126796454117.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net>
2005-09-15 15:14 ` Thomas Stockheim [this message]
[not found] ` <18266122.1126803664464.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net>
2005-09-16 7:22 ` NFS problem - close to open cache consistency broken ? Thomas Stockheim
2005-09-15 13:50 Lever, Charles
2005-09-15 14:19 ` Peter Staubach
2005-09-15 15:08 ` J. Bruce Fields
2005-09-15 15:12 ` Peter Staubach
[not found] <6063053.1126674084242.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net>
2005-09-15 7:47 ` Thomas Stockheim
-- strict thread matches above, loose matches on Subject: below --
2005-09-14 2:22 Lever, Charles
2005-09-13 9:04 Thomas Stockheim
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=43298FC4.3080008@bub-agema.de \
--to=tommi@bub-agema.de \
--cc=nfs@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox