Lecture 06 Distributed File Systems.ppt

* * * * * * * * * * Transaction based File Sharing File operations are included in transactions Atomic and consistent File Locking A central lock manager, in general Locking is complex, to allow concurrent accessing Different locks exist, and Different granularities used NFS v4 as an example File Locking in NFS v4 Conceptually simple If a “lock” fails due to confliction, an error message is returned (nonblocking),and then The client tries later (simple) or Request the server to put its request on a FIFO list, and poll the server in time (fairness guaranteed) File Share Reservation in NFS An implicit way to lock a file Completely independent from locking management Specifying the type of access upon opening a file §6.5 Consistency and Replication Cache, client side Replication, server side NFS as the example Client-side Caching in NFS v3: not considered in NFS protocol itself Handled in an implementation-dependent way Can be stale for a few seconds or even 30 seconds No consistency guaranteed Client-side Caching in NFS v4: considered caching Still in an implementation-dependent way Session semantics specified When a client opens a file and caches the data it obtains from the server as the result of various read operations. Write operations can be carried out in the cache as well. Flushing cache back to the server upon closing the file Clients at the same machine can share cache Cache can be kept after file close Need to be revalidated after re-opening Open Delegation A server may delegate some of its rights to a client when a file is opened for writing The client machine is allowed to locally handle open and close operations from other clients on the same machine file locking requests can be handled locally. The server will still handle locking requests from clients on other machines, by simply denying those clients access to the file. Open Delegation The server needs to be able to recall the delegation Recalling a delegation is done by a callback to the client Se