From owner-freebsd-fs@FreeBSD.ORG  Fri Oct 31 15:59:01 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id F1A3DBFF
 for <freebsd-fs@freebsd.org>; Fri, 31 Oct 2014 15:59:01 +0000 (UTC)
Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu
 [IPv6:2001:470:8b2d:1e1c:21b:21ff:feb8:d7b0])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "khavrinen.csail.mit.edu", Issuer "Client CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id B12F15FE
 for <freebsd-fs@freebsd.org>; Fri, 31 Oct 2014 15:59:01 +0000 (UTC)
Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1])
 by khavrinen.csail.mit.edu (8.14.9/8.14.9) with ESMTP id s9VFx0j0040276
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256
 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA);
 Fri, 31 Oct 2014 11:59:00 -0400 (EDT)
 (envelope-from wollman@khavrinen.csail.mit.edu)
Received: (from wollman@localhost)
 by khavrinen.csail.mit.edu (8.14.9/8.14.9/Submit) id s9VFwx92040273;
 Fri, 31 Oct 2014 11:58:59 -0400 (EDT) (envelope-from wollman)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <21587.45507.688734.672857@khavrinen.csail.mit.edu>
Date: Fri, 31 Oct 2014 11:58:59 -0400
From: Garrett Wollman <wollman@csail.mit.edu>
To: "Russell L. Carter" <rcarter@pinyon.org>
Subject: Re: Definite NFS  bug
In-Reply-To: <5452D2C3.9040902@pinyon.org>
References: <21586.48982.64913.250497@khavrinen.csail.mit.edu>
 <5452D2C3.9040902@pinyon.org>
X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (khavrinen.csail.mit.edu [127.0.0.1]); Fri, 31 Oct 2014 11:59:00 -0400 (EDT)
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Fri, 31 Oct 2014 15:59:02 -0000

<<On Thu, 30 Oct 2014 17:07:31 -0700, "Russell L. Carter" <rcarter@pinyon.org> said:

> The problems I'm seeing on -current for the last few months
> seem to me to be out-of-date targets, so that the failure is a
> desire by the remote client to try to rebuild the out-of-date target
> on the RO file system.

Nope, nothing at all to do with that.  As I said in my original
message, the problem is that the server is returning NFS3ERR_IO or
NFS3ERR_ACCES for RPCs that should (and a few seconds later DO)
succeed.

-GAWollman