Date: Mon, 16 Oct 2006 16:41:08 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Mohan Srinivasan <mohan_srinivasan@yahoo.com> Cc: fs@freebsd.org, rick@snowhite.cis.uoguelph.ca Subject: Re: lost dotdot caching pessimizes nfs especially Message-ID: <20061016163015.C63585@delplex.bde.org> In-Reply-To: <20061015213509.60929.qmail@web30813.mail.mud.yahoo.com> References: <20061015213509.60929.qmail@web30813.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 15 Oct 2006, Mohan Srinivasan wrote: > of applications. Since the other NFS clients (that matter) Solaris and Linux support it, > I would argue that not supporting cto consistency is not really an option. I agree. > We can however provide a mount option "nocto" (like those clients do) that overrides > the default for specific cases (read only mounts, single client mounts etc). PR 78673 has a patch to break consistency unconditionally for r/o mounts. I use this, but it doesn't help for my most active file system (/usr/obj) since that needs to be r/w. It is obviously wrong to do this unconditonally on the client. It is the server's read-onlyness that matters. I don't know how to track the server's read-onlyness short of asking it on every open() or Access. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061016163015.C63585>