From owner-freebsd-fs@FreeBSD.ORG  Mon May 20 21:08:00 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@smarthost.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 02DD14AB;
 Mon, 20 May 2013 21:08:00 +0000 (UTC)
 (envelope-from rmacklem@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 by mx1.freebsd.org (Postfix) with ESMTP id D08C41451;
 Mon, 20 May 2013 21:07:59 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
 by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4KL7xKH013170;
 Mon, 20 May 2013 21:07:59 GMT
 (envelope-from rmacklem@freefall.freebsd.org)
Received: (from rmacklem@localhost)
 by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4KL7xSM013169;
 Mon, 20 May 2013 21:07:59 GMT (envelope-from rmacklem)
Date: Mon, 20 May 2013 21:07:59 GMT
Message-Id: <201305202107.r4KL7xSM013169@freefall.freebsd.org>
To: astrange@gmail.com, rmacklem@FreeBSD.org, freebsd-fs@FreeBSD.org
From: rmacklem@FreeBSD.org
Subject: Re: kern/178231: [nfs] 8.3 nfsv4 client reports "nfsv4 client/server
 protocol prob err=10026"
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
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: Mon, 20 May 2013 21:08:00 -0000

Synopsis: [nfs] 8.3 nfsv4 client reports "nfsv4 client/server protocol prob err=10026"

State-Changed-From-To: open->feedback
State-Changed-By: rmacklem
State-Changed-When: Mon May 20 21:06:30 UTC 2013
State-Changed-Why: 

I have emailed the reporter and asked him to test without
the "intr" mount option, which could cause this. The error
indicates that the client got "out of sync" with the server
while doing open/lock operations, which are serialized via
a sequence number.

http://www.freebsd.org/cgi/query-pr.cgi?pr=178231