From: Tom McNeal <trmcneal@attbi.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Re: NFS as a Cluster File System (Locking question)
Date: Sat, 25 Jan 2003 12:32:27 -0800 [thread overview]
Message-ID: <3E32F45B.3020903@attbi.com> (raw)
In-Reply-To: 6440EA1A6AA1D5118C6900902745938E07D551E9@black.eng.netapp.com
Hi -
> best. however, on Linux, the client purges the entire file
> from its cache when a file is locked, rather than just the
> areas that were byte-range locked.
The purge must occur at lock time (or lock attempt time), right? Or
does the metadata also keep lock status, and therefore should occur
even when just a stat is done? (I don't think this is the case, but I
thought I'd make sure, not having looked at it recently)
Tom
Lever, Charles wrote:
>>On Thursday January 9, alanr@unix.sh wrote:
>>
>>>NFS V3 and before have problems with "cache coherency".
>>>
>>That is, the
>>
>>>different nodes in the cluster are not guaranteed to see
>>>
>>the same contents.
>>
>>>I think this is supposed to be fixed in v4.
>>>
>>>
>>NFSv4 does not try to "fix" this. It makes no attempts at
>>"cache coherency" beyond what NFSv2/3 provide which is "close
>>to open" cohenrence, meaning that if only one process has a
>>file open at a time, then everythnig will appear coherent,
>>and if multiple processes have the file open at the same
>>time, they need to use record locking.
>>
>
> well, coherency is partially addressed in NFSv4 with delegations.
> a server can delegate a file to a client, allowing the client
> to cache the file and trust that the server will notify it when
> another client wants to access the file (read or write).
>
> for an aggressively shared file, this doesn't perform well, but
> NFS has always assumed that there is little concurrent sharing
> of files.
>
> this paradigm probably doesn't fit well with typical file
> usage in clusters, where files are very very large, and many
> nodes may be working on independent pieces of the same file
> at the same time. in that case, record locking might be
> best. however, on Linux, the client purges the entire file
> from its cache when a file is locked, rather than just the
> areas that were byte-range locked.
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
>
>
--
Tom McNeal
(650)906-0761(cell)
(650)964-8459(fax)
Email: trmcneal@attbi.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-01-25 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 16:01 Re: NFS as a Cluster File System Lever, Charles
2003-01-25 20:32 ` Tom McNeal [this message]
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=3E32F45B.3020903@attbi.com \
--to=trmcneal@attbi.com \
--cc=Charles.Lever@netapp.com \
--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