Alfred, If the operation times out because the server rebooted (or because of a network glitch), rather than losing data, the client can potentially have the data written out successfully later.
Other NFS client implementations (at least the Solaris client) re-dirty pages on soft mount timeouts. mohan --- Alfred Perlstein <[EMAIL PROTECTED]> wrote: > > Log: > > MFC src/sys/nfsclient/nfs_bio.c,v 1.154 > > and src/sys/nfsclient/nfs_vnops.c,v 1.262 (by ps@): > > > ... > > - Treat ETIMEDOUT as a "recoverable" error, causing the buffer > > to be re-dirtied. ETIMEDOUT can occur on soft mounts, when > > the number of retries are exceeded, and we don't want data loss > > in that case. > > Actually that's the documented behavior, if the mount times out, > one will lose data. > > What does this do? Leave the buffer dirty/held until forcefully > unmounted? I guess that sort of makes sense, can someone explain > a bit better? > > -- > - Alfred Perlstein > _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
