Lines Matching full:server

35 It is an adaptation of the NFS protocol such that the server supports both NFS
36 and NQNFS clients while maintaining full consistency between the server and
39 but uses Leases [Gray89] to avoid the need to recover server state information
62 the server via. RPCs.
66 but requires that all writes be pushed to the server when the lease expires.
69 \** Cached write data is not yet pushed (written) to the server.
84 It is the server's responsibility to ensure that consistency is maintained
85 among the NQNFS clients by disabling client caching whenever a server file
89 or local operations on the server,
92 At this time, the server sends an \fBeviction notice\fR to all clients holding
98 correspond to a Sprite server\(->client callback, but are not implemented as an
99 actual RPC, to avoid the server waiting indefinitely for a reply from a dead
102 Server consistency checking can be viewed as issuing intrinsic leases for a
107 By relegating this responsibility to the server, consistency between the
108 server and NQNFS clients is maintained when NFS clients are modifying the
112 the server.
117 the server. The \fBmaximum_lease_term\fR sets an upper bound on lease duration.
118 The \fBclock_skew\fR is added to all lease terms on the server to correct for
119 differing clock speeds between the client and server and \fBwrite_slack\fR is
120 the number of seconds the server is willing to wait for a client with
123 The server maintains a \fBmodify_revision\fR number for each file. It is
125 increase whenever the corresponding file is modified on the server.
152 The server must maintain the state of all the current leases held by clients.
154 after the server stops issuing leases, there are no current leases left.
155 As such, server crash recovery does not require any state recovery. After
156 rebooting, the server refuses to service any RPCs except for writes until
163 By then, the server would not have any outstanding leases to recover the
165 writes to the server and get the server sync'd up to date. After this, the
166 server simply services requests in a manner similar to NFS.
168 the server replies \fBtry_again_later\fR to the RPCs it is not
171 After a client crashes, the server may have to wait for a lease to timeout
175 outstanding leases for that client on the server prior to the crash will either be renewed or expire
179 server network connection is severed just before a write caching lease expires,
180 the client cannot push the dirty writes to the server. After the lease expires
181 on the server, the server permits other clients to access the file with the
183 is intrinsic in any delay write caching scheme unless the server is required to
190 server as soon as the network connection has been re-established.
192 There is another failure condition that can occur when the server is congested.
193 The worst case scenario would have the client pushing dirty writes to the server
194 but a large request queue on the server delays these writes for more than
199 A write caching lease is only terminated on the server when there are have
200 been no writes to the file and the server has not been overloaded during
201 the previous write_slack seconds. The server has not been overloaded
204 .sh 2 "Server Disk Full"
207 server disk space allocation.
208 When the disk on the file server is full, delayed write RPCs can fail
291 was issued on the server\**.
294 for ``duration'' seconds from when the RPC request was sent to the server.
304 This message is sent from the server to the client. When the client receives
307 the server. Flushing includes pushing any dirty writes via. write RPCs.
314 This message is sent from the client to the server in response to the
329 The access RPC does permission checking on the server for the given type
331 Use of this RPC avoids accessibility problems caused by client->server uid
374 value is returned by the server when it wishes the client to retry the
376 and may also be useful for server congestion control.
398 and increases every time the corresponding file is modified on the server.
477 The additional "duration" argument tells the server to get a lease for the