From owner-freebsd-stable@FreeBSD.ORG  Wed Oct  3 21:25:46 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3C471106564A
	for <freebsd-stable@freebsd.org>; Wed,  3 Oct 2012 21:25:46 +0000 (UTC)
	(envelope-from rmacklem@uoguelph.ca)
Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca
	[131.104.91.36])
	by mx1.freebsd.org (Postfix) with ESMTP id E30DD8FC15
	for <freebsd-stable@freebsd.org>; Wed,  3 Oct 2012 21:25:45 +0000 (UTC)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EADesbFCDaFvO/2dsb2JhbABFhg+1JoRRgiABAQUjVhsOCgICDRIHAlkGiBilKZJkgSGKAoUogRIDlWmJPIZvgwmBew
X-IronPort-AV: E=Sophos;i="4.80,530,1344225600"; d="scan'208";a="184529215"
Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca)
	([131.104.91.206])
	by esa-annu-pri.mail.uoguelph.ca with ESMTP; 03 Oct 2012 17:25:44 -0400
Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1])
	by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 68C5DB404C;
	Wed,  3 Oct 2012 17:25:44 -0400 (EDT)
Date: Wed, 3 Oct 2012 17:25:44 -0400 (EDT)
From: Rick Macklem <rmacklem@uoguelph.ca>
To: Konstantin Belousov <kostikbel@gmail.com>
Message-ID: <1965862480.1682152.1349299544413.JavaMail.root@erie.cs.uoguelph.ca>
In-Reply-To: <20121003173931.GZ35915@deviant.kiev.zoral.com.ua>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.17.91.202]
X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692)
Cc: Norbert Aschendorff <norbert.aschendorff@yahoo.de>,
	freebsd-stable@freebsd.org
Subject: Re: panic "Sleeping thread owns a non-sleepable lock" via
 cv_timedwait_signal, was "rsync over NFS"
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 21:25:46 -0000

Konstantin Belousov wrote:
> On Wed, Oct 03, 2012 at 07:26:47PM +0200, Norbert Aschendorff wrote:
> > On 10/03/2012 05:54 PM, Konstantin Belousov wrote:
> > > So do you use nullfs exported mounts ? And stable ?
> > > Can you try to remove nullfs from the set up ?
> >
> > Yes, I am using nullfs for the exports (mounting the exported
> > directories to subdirectories of /srv). In the FreeBSD man pages and
> > the
> > documentation, the V4 export line in /etc/exports is often set to /,
> > but
> > as I come from Linux where /etc/exports looks completely different,
> > I
> > just followed my habits.
> >
> > As I wrote this, I executed the critical operation. It's finished
> > and
> > the FreeBSD server still runs *yay* :) So it's quite likely that the
> > problem stems from the nullfs mount.
> >
> > I just remember an issue I already wanted to tell: Before the server
> > crashed, the nfsd process ('nfsd: server') used 100% CPU (one core),
> > but
> > without progress on client side. Usually, the nfsd uses only up to
> > 10%
> > cpu time when rsyncing (values taken from htop - 100% = one used
> > CPU).
> >
> > ...aaand I just run it once more, and it worked again :)
> 
> Can you try HEAD kernel ?
Kostik, thanks for thinking of this. The crash had me baffled, rick.