From owner-freebsd-fs@FreeBSD.ORG  Mon Oct 16 06:41:11 2006
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
X-Original-To: fs@freebsd.org
Delivered-To: freebsd-fs@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5EAAC16A40F
	for <fs@freebsd.org>; Mon, 16 Oct 2006 06:41:11 +0000 (UTC)
	(envelope-from bde@zeta.org.au)
Received: from mailout1.pacific.net.au (mailout1-3.pacific.net.au [61.8.2.210])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F107A43D53
	for <fs@freebsd.org>; Mon, 16 Oct 2006 06:41:10 +0000 (GMT)
	(envelope-from bde@zeta.org.au)
Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au
	[61.8.2.162])
	by mailout1.pacific.net.au (Postfix) with ESMTP id 3CCBE69FDAF;
	Mon, 16 Oct 2006 16:41:10 +1000 (EST)
Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246])
	by mailproxy1.pacific.net.au (Postfix) with ESMTP id 57F858C3A;
	Mon, 16 Oct 2006 16:41:09 +1000 (EST)
Date: Mon, 16 Oct 2006 16:41:08 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@delplex.bde.org
To: Mohan Srinivasan <mohan_srinivasan@yahoo.com>
In-Reply-To: <20061015213509.60929.qmail@web30813.mail.mud.yahoo.com>
Message-ID: <20061016163015.C63585@delplex.bde.org>
References: <20061015213509.60929.qmail@web30813.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: fs@freebsd.org, rick@snowhite.cis.uoguelph.ca
Subject: Re: lost dotdot caching pessimizes nfs especially
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Oct 2006 06:41:11 -0000

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