From owner-freebsd-net@FreeBSD.ORG  Fri May 13 18:58:48 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C7E6D16A4CE
	for <freebsd-net@freebsd.org>; Fri, 13 May 2005 18:58:48 +0000 (GMT)
Received: from web80603.mail.yahoo.com (web80603.mail.yahoo.com
	[66.218.79.92])	by mx1.FreeBSD.org (Postfix) with SMTP id 96A7943D81
	for <freebsd-net@freebsd.org>; Fri, 13 May 2005 18:58:48 +0000 (GMT)
	(envelope-from mohan_srinivasan@yahoo.com)
Message-ID: <20050513185848.78077.qmail@web80603.mail.yahoo.com>
Received: from [64.165.201.18] by web80603.mail.yahoo.com via HTTP;
	Fri, 13 May 2005 11:58:48 PDT
Date: Fri, 13 May 2005 11:58:48 -0700 (PDT)
From: Mohan Srinivasan <mohan_srinivasan@yahoo.com>
To: Heinrich Rebehn <rebehn@ant.uni-bremen.de>
In-Reply-To: 6667
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: freebsd-net@freebsd.org
Subject: Re: nfsrvstats.srvrpc_errs rapidly increasing
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2005 18:58:48 -0000

--- Heinrich Rebehn <rebehn@ant.uni-bremen.de> wrote:

> > There's no problem report on this. 
> 
> I wonder if it will ever get fixed then..

It will. It's purely a question of priorities and time.

> Since i am neither familiar with kernel sources nor with the internals 
> of NFS: Could you show me, where the bug can be traced, i.e. at which 
> point one can detect that the stream is out of sync? I would like to 
> insert another log() in order to see, if
> - the error occurs at all
> - is in any way related to our problems.

For the bug where the stream gets out of sequence, you might want
to start by looking at this fragment of code in nfssvc_nfsd().

                        /*
                         * For stream protocols, prepend a Sun RPC
                         * Record Mark.
                         */
                        if (sotype == SOCK_STREAM) {
                                M_PREPEND(m, NFSX_UNSIGNED, M_TRYWAIT);
                                *mtod(m, u_int32_t *) = htonl(0x80000000 | siz);
                        }

mohan