Lines Matching +full:write +full:- +full:only

38 This section borrows heavily from work done on Spritely-NFS [Srinivasan89],
54 file whenever that file is write shared\**.
56 \** Write sharing occurs when at least one client is modifying a file while
60 There are three types of leases: read caching, write caching and non-caching.
65 A write caching lease allows for client caching of writes,
69 \** Cached write data is not yet pushed (written) to the server.
71 when a write cache lease has almost expired, it will attempt to
75 frequent RPCs Getattr, Setattr, Lookup, Readlink, Read, Write and Readdir
80 are not write cached.
88 a write caching lease and any other client,
98 correspond to a Sprite server\(->client callback, but are not implemented as an
103 file operation for the duration of the operation only. For example, the
104 \fBCreate RPC\fR will get an intrinsic write lease on the directory in which
121 an expired write caching lease to push dirty writes.
133 The low order longword is stored in main memory only and is initialized to
141 Since the high order longword only increments once per second and the inode
148 the LRU inode cache, but this should only reduce the client caching performance
172 before servicing a request if write sharing of a file with a cachable lease
179 server network connection is severed just before a write caching lease expires,
183 is intrinsic in any delay write caching scheme unless the server is required to
186 \** Gray and Cheriton avoid this problem by using a \fBwrite through\fR policy.
188 Since the write caching lease has expired on the client,
190 server as soon as the network connection has been re-established.
197 the following lease termination rule for write caching leases
199 A write caching lease is only terminated on the server when there are have
206 There is a serious unresolved problem for delayed write caching with respect to
208 When the disk on the file server is full, delayed write RPCs can fail
215 may not attempt the write RPC until after the process has done the close
218 the only solution is to modify programs writing important
293 \** To be safe, the client may only assume that the lease is valid
307 the server. Flushing includes pushing any dirty writes via. write RPCs.
331 Use of this RPC avoids accessibility problems caused by client->server uid
340 the "stat" field only if "stat == NFS_OK".
478 name being looked up if it is non-zero and the lease is specified
490 Write RPC
499 The "append" argument is true for apeend only write operations.