On Fri, Jun 01, 2007 at 09:14:53AM -0400, Peter Staubach wrote: > J. Bruce Fields wrote: > >From: J. Bruce Fields <[EMAIL PROTECTED]> > > > >Currently leases are only kept locally, so there's no way for a distributed > >filesystem to enforce them against multiple clients. We're particularly > >interested in the case of nfsd exporting a cluster filesystem, in which > >case nfsd needs cluster-coherent leases in order to implement delegations > >correctly. > > A couple of naive questions -- > > Do the semantics of these leases really match the requirements from NFSv4?
The only problem I'm aware of is that leases aren't broken on rename, link, and unlink. This is kind of tricky to fix. David Richter (cc'd) and I sketched out a few different approaches, and I think he has some patches implementing at least one of them. This may require defining some new type of lease, to avoid changing the documented behavior of the fcntl lease operations (which only break on open). Although actually I believe Samba needs the same behavior we do, and they're probably the most important user of leases.... > Does the internal NFSv4 server state also need to be shared? Not that I can see. The setup we're trying to deal with here is one where we have a cluster filesystem mounted by several nodes, at least two of which are running nfs servers exporting that filesystem. The servers don't share clients--so no clientid's or stateid's are shared--but they need leases, locks, etc., to be coherent across all the servers. --b. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
