Date: Tue, 18 Apr 2006 09:53:48 -0700 (PDT) From: Mohan Srinivasan <mohan_srinivasan@yahoo.com> To: Alfred Perlstein <alfred@freebsd.org>, Xin LI <delphij@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, ps@freebsd.org, cvs-all@FreeBSD.org, mohans@freebsd.orgc Subject: Re: cvs commit: src/sys/nfsclient nfs_bio.c nfs_vnops.c Message-ID: <20060418165348.55185.qmail@web30804.mail.mud.yahoo.com> In-Reply-To: <20060418133832.GF35896@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <alfred@freebsd.org> 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060418165348.55185.qmail>