From owner-freebsd-current@FreeBSD.ORG  Wed Oct 13 04:31:47 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A06AB16A4CE
	for <freebsd-current@FreeBSD.org>;
	Wed, 13 Oct 2004 04:31:47 +0000 (GMT)
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6878C43D1D
	for <freebsd-current@FreeBSD.org>;
	Wed, 13 Oct 2004 04:31:47 +0000 (GMT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com (localhost [127.0.0.1])
	i9D4VkvA094852;	Tue, 12 Oct 2004 21:31:46 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i9D4VjPJ094849;
	Tue, 12 Oct 2004 21:31:45 -0700 (PDT)
	(envelope-from dillon)
Date: Tue, 12 Oct 2004 21:31:45 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200410130431.i9D4VjPJ094849@apollo.backplane.com>
To: Mikhail Teterin <Mikhail.Teterin@murex.com>
References: <416AE7D7.3030502@murex.com>
	<200410112038.i9BKcCWt051290@apollo.backplane.com>
	<416C1B10.7030103@murex.com>
	<200410121818.i9CIIGRx092072@apollo.backplane.com>
	<416C2502.5040505@murex.com>
cc: freebsd-current@FreeBSD.org
cc: bde@zeta.org.au
Subject: Re: panic in ffs (Re: hangs in nbufkv)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2004 04:31:47 -0000


:I don't know, how, but the bug seems triggered by upping the 
:net.inet.udp.maxdgram from 9216 (default) to 16384 (to match the NFS 
:client's wsize). Once I do that, the machine will either panic or just 
:hang a few minutes into the heavy NFS writing (Sybase  database dumps 
:from a Solaris server). Happened twice already...
:
:    -mi
:
:P.S. Thanks for prompt responses and advice, BTW!

    Interesting.  That's getting a bit outside the realm I can help
    with.  NFS and the network stack have been issues in FreeBSD 
    recently so its probably something related.  I do seem to
    recall that NFS takes a callback from the network protocol
    stack for input processing.

    One thing I would do is to try using a TCP NFS mount instead
    of a UDP NFS mount.  It might work better simply due to 
    exercising a different part of the network code.  The buffer
    cache has some NFS specific stuff in it, but unless it has 
    been completely ripped up there shouldn't be anything that
    would actually crash the machine.  My bets are on the 
    network stack's interaction with NFS rather then NFS's
    interaction with the buffer cache.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>