From owner-freebsd-stable@FreeBSD.ORG Wed Jan 2 04:13:21 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E5EE154; Wed, 2 Jan 2013 04:13:21 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 45C5F8FC14; Wed, 2 Jan 2013 04:13:21 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id r024DKPB074174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 1 Jan 2013 20:13:20 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id r024DKYg074173; Tue, 1 Jan 2013 20:13:20 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA02962; Tue, 1 Jan 13 20:02:27 PST Date: Tue, 01 Jan 2013 20:02:05 -0800 From: perryh@pluto.rain.com (Perry Hutchison) To: hrs@freebsd.org Subject: Re: NFS-exported ZFS instability Message-Id: <50e3a32d.y5esCCIn50EhNFml%perryh@pluto.rain.com> References: <20130102.105304.1817355190360003433.hrs@allbsd.org> In-Reply-To: <20130102.105304.1817355190360003433.hrs@allbsd.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 04:13:21 -0000 Hiroki Sato wrote: > I have been in a trouble about my NFS server for a long time. > The symptom is that it stops working in one or two weeks after > a boot ... It did not panic, just stopped working---while it > responded to ping, userland programs seemed not working ... > Does anyone see how to debug this? I guess this is due to a > deadlock somewhere ... If you can afford the overhead, you could try running with some of the kernel debug options enabled (e.g. WITNESS, INVARIANTS, MUTEX_DEBUG). See conf/NOTES for descriptions.