Re: [PATCH] NFS: Sign Extentions with Tru64 FSIDs.

[Peter Staubach <staubach@redhat.com>]

Trond Myklebust wrote:
> On Mon, 2007-03-05 at 16:46 -0500, Peter Staubach wrote:
>   
>> It is an ickey idea and the right way is to fix the Tru64 server, but
>> given that we probably can't get it fixed, this seems relatively low
>> risk.
>>     
>
> I disagree. The fact that people are using the fsid in creative ways, is
> reason enough to be cautious about quick fixes. If we really must work
> around on the client, then I'd prefer something like a mount option that
> just causes us to ignore fsid changes (i.e. fall back to the 2.4.x
> behaviour).
>
> Hacking the fsid on behalf of the server is certainly vetoed.

Well, I find it a little hard to imagine that anyone would choose
a combination of fsids which would cause this to do the wrong thing,
but okay.  It is definitely a heuristic and thus, subject to possible
failure, no matter how remote.

Perhaps the right thing to do is to revert the NFSv2/NFSv3 support
completely and not have them worry about changing fsids?  The common
practice is to use an automounting facility or static mounts to
construct namespaces for NFSv2/NFSv3 networks.  It is really only
with the advent of NFSv4 that the fsids actually become interesting
and something that the client needs to be aware of.

Or we could just punt and document that READDIRPLUS must be disabled
on all Tru64 NFS servers if this problem is seen.

    Thanx...

       ps

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs