|
Horms <horms@xxxxxxxxxxxx> writes:
> On Fri, Sep 28, 2001 at 02:11:09PM -0700, Steven Lang wrote:
> > I actually specifically tested for this. Now it may just be a
> > linux thing, not common to all NFS platforms, but in my tests,
> > when packets were sent to the server other than the one mounted,
> > it happily serves up the requested data without even blinking. So
> > whatever state is being saved (And I do know there is some minimal
> > state) seems unimportant. It actually surprised me how seamlessly
> > it all worked, as I was expecting the non-mounted server to reject
> > the requests or something similar.
>
> That is quite suprising as the server should maintain state as to
> what clients have what mounted.
Not really, it only maintains that list so that shutdown messages can
be sent all clients needing notification. So it's purely a matter of
user convenience.
All the file and filesystem handles information are traditionally
generated deterministically from information in the filesystem (inode)
and physical device (e.g. /dev/hda1). It is therefore not surprising
that it just works when the servers use the same filesystem. The
standard does not guarantee this behaviour, mind you, but I've never
seen an implementation which did it otherwise.
Kjetil T.
|
