From: Mike Fedyk <mfedyk@matchmail.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Steffen Persvold <sp@scali.no>,
Christopher Friesen <cfriesen@nortelnetworks.com>,
linux-kernel@vger.kernel.org
Subject: NFS, Paging & Installing [was: Re: Swap]
Date: Tue, 20 Nov 2001 13:50:59 -0800 [thread overview]
Message-ID: <20011120135059.D4210@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011120131839.B4210@mikef-linux.matchmail.com> <Pine.LNX.3.95.1011120163024.14793A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1011120163024.14793A-100000@chaos.analogic.com>
On Tue, Nov 20, 2001 at 04:43:01PM -0500, Richard B. Johnson wrote:
> On Tue, 20 Nov 2001, Mike Fedyk wrote:
> > IIRC (if wrong flame...)
> >
> > When you delete an open file, the entry is removed from the directory, but
> > not unlinked until the file is closed. This is a standard UNIX semantic.
> >
> > Now, if you have a set of processes with shared memory, and one closes, and
> > another is created to replace, the new process will get the new libraries,
> > or even new version of the process. This could/will bring down the entire
> > set of processes.
> >
> > Apps like samba come to mind...
> >
> > Mike
>
> If the file is local, everything is fine. A file won't actually
> be deleted until the last access is closed. However, the long-standing
> problem with NFS is that it's `phony`. Basically, we send a message
> to a server that says "Give me a directory listing...". The server
> does the `opendir()` etc., and returns the results. If I want to
> open a file on the server, the server has no knowledge of the `open`.
> The client's software just emulated a file-system open(). When the
> client wants to read data from a server's file, it sends a message;
> "Gimmie data from file xxx, offset x, length y.". The server responds
> with that data. To get that data, the server did an open/lseek/read/close.
>
> So, as far as the server is concerned, that file is closed. Somebody
> else (with privilege) can delete the file and replace it. The client,
> the one that got the data for an executable, doesn't even know it.
>
> This is 'nice' for the server, it doesn't have the overhead of maintaining
> a file-system state. That's why servers are supposed to be read-only.
> However, somebody has got to write the stuff to the file-system that's
> going to (eventually) be read-only. Beware when such access occurs.
>
Do any newer versions of NFS fix the stateless server problem?
If not, are there any drop in (at least for linux) replacements that do keep
state on the server?
SMB is out because it doesn't propagate the unix uid/gid
Striped down (auth wise) AFS?
Intermezzo?
next prev parent reply other threads:[~2001-11-20 21:51 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.inl6g6v.1mmbp4@ifi.uio.no>
[not found] ` <fa.heevhav.sjs8an@ifi.uio.no>
2001-11-18 22:15 ` Swap Dan Maas
2001-11-18 22:43 ` Swap François Cami
2001-11-19 9:18 ` Swap James A Sutherland
2001-11-19 10:51 ` Swap Remco Post
2001-11-19 13:33 ` Swap James A Sutherland
2001-11-19 13:46 ` Swap Remco Post
2001-11-19 16:58 ` Swap Rik van Riel
[not found] ` <Pine.LNX.4.33L.0111191458150.1491-100000@duckman.distro.conecti va>
2001-11-19 21:13 ` Swap Alex Bligh - linux-kernel
2001-11-19 21:17 ` Swap Rik van Riel
[not found] ` <Pine.LNX.4.33L.0111191917000.1491-100000@duckman.distro.conecti va>
2001-11-19 21:52 ` Swap Alex Bligh - linux-kernel
2001-11-19 16:36 ` Swap Jesse Pollard
2001-11-20 14:51 ` Swap J.A. Magallon
2001-11-20 16:01 ` Swap Wolfgang Rohdewald
2001-11-20 16:06 ` Swap Remco Post
2001-11-20 16:12 ` Swap Nick LeRoy
2001-11-20 16:20 ` Swap Richard B. Johnson
2001-11-20 17:14 ` Swap Christopher Friesen
2001-11-20 17:40 ` Swap Richard B. Johnson
2001-11-20 18:14 ` Swap Nick LeRoy
2001-11-21 10:17 ` Swap Helge Hafting
2001-11-21 11:17 ` Swap Alan Cox
2001-11-20 23:20 ` Swap Luigi Genoni
2001-11-21 16:44 ` Swap Remco Post
2001-11-20 17:58 ` Swap Wolfgang Rohdewald
2001-11-26 21:51 ` [Linux-abi-devel] Swap Christoph Hellwig
2001-11-20 21:05 ` Swap Steffen Persvold
2001-11-20 21:18 ` Swap Mike Fedyk
2001-11-20 21:33 ` Swap Nick LeRoy
2001-11-20 21:44 ` Swap Mike Fedyk
2001-11-20 22:00 ` Swap Nick LeRoy
2001-11-21 16:53 ` Swap Remco Post
2001-11-20 21:43 ` Swap Richard B. Johnson
2001-11-20 21:50 ` Mike Fedyk [this message]
2001-11-21 1:22 ` NFS, Paging & Installing [was: Re: Swap] Horst von Brand
2001-11-21 1:46 ` Mike Fedyk
2001-11-21 10:55 ` Trond Myklebust
2001-11-22 5:16 ` Bernd Eckenfels
2001-11-22 12:19 ` Trond Myklebust
2001-11-23 19:33 ` Mike Fedyk
2001-11-20 21:19 ` Swap Nick LeRoy
2001-11-21 16:48 ` Swap Remco Post
2001-11-20 20:58 ` Swap Mike Fedyk
2001-11-19 10:03 ` Swap Tim Connors
2001-11-19 10:16 ` Swap Dan Maas
2001-10-18 5:06 RFC - tree quotas for Linux (2.4.12, ext2) Neil Brown
2001-10-18 5:53 ` Ben Greear
2001-10-18 8:38 ` James Sutherland
2001-10-18 20:20 ` Mike Fedyk
2001-10-18 20:47 ` Tim Walberg
2001-10-19 1:07 ` Neil Brown
2001-10-19 3:03 ` Rik van Riel
2001-10-19 11:50 ` Horst von Brand
2001-10-19 17:00 ` Mike Fedyk
2001-10-18 21:17 ` Andreas Dilger
2001-10-18 22:56 ` Mike Fedyk
2001-10-19 0:14 ` Horst von Brand
2001-10-19 0:51 ` Mike Fedyk
2001-10-19 1:13 ` Neil Brown
2001-10-19 0:53 ` Neil Brown
2001-10-24 15:16 ` Jan Kara
2001-10-24 15:34 ` James Sutherland
2001-10-24 15:39 ` Jan Kara
2001-10-24 15:50 ` James Sutherland
2001-10-24 17:41 ` Rik van Riel
2001-10-24 18:08 ` James Sutherland
2001-10-26 11:25 ` Pavel Machek
2001-10-24 21:24 ` Neil Brown
2001-10-25 15:48 ` Jan Kara
2001-10-26 4:36 ` Neil Brown
2001-10-29 14:06 ` Jan Kara
2001-10-29 23:23 ` Neil Brown
2001-10-30 12:33 ` Jan Kara
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=20011120135059.D4210@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=sp@scali.no \
/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