From owner-freebsd-current@FreeBSD.ORG  Sat May  1 22:21:32 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 1B0651065670
	for <current@freebsd.org>; Sat,  1 May 2010 22:21:32 +0000 (UTC)
	(envelope-from brucec@muon.cran.org.uk)
Received: from muon.cran.org.uk (muon.cran.org.uk [109.74.192.160])
	by mx1.freebsd.org (Postfix) with ESMTP id DC1448FC1A
	for <current@freebsd.org>; Sat,  1 May 2010 22:21:31 +0000 (UTC)
Received: by muon.cran.org.uk (Postfix, from userid 1000)
	id 04F9EC400D; Sat,  1 May 2010 22:21:31 +0000 (UTC)
Date: Sat, 1 May 2010 22:21:30 +0000
From: Bruce Cran <brucec@cran.org.uk>
To: Jeff Roberson <jroberson@jroberson.net>
Message-ID: <20100501222130.GA25044@muon.cran.org.uk>
References: <alpine.BSF.2.00.1004291832080.1398@desktop>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1004291832080.1398@desktop>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Mailman-Approved-At: Sun, 02 May 2010 00:54:56 +0000
Cc: current@freebsd.org
Subject: Re: SUJ update
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Sat, 01 May 2010 22:21:32 -0000

On Thu, Apr 29, 2010 at 06:37:00PM -1000, Jeff Roberson wrote:

> I fixed a few SUJ bugs.  If those of you who reported one of the 
> following bugs could re-test I would greatly appreciate it.
>

I've started seeing a panic "Sleeping thread owns a non-sleepable lock", 
though it seems to be occurring both with and without journaling. The 
back trace when journaling is disabled is:

sched_switch
mi_switch
sleepq_wait
_sleep
bwait
bufwait
bufwrite
ffs_balloc_ufs2
ffs_write
VOP_WRITE_APV
vnode_pager_generic_putpages
VOP_PUTPAGES
vnode_pager_putpages
vm_pageout_flush
vm_object_page_collect_flush
vm_object_page_clean
vfs_msync
sync_fsync
VOP_FSYNC_APV
sync_vnode
sched_sync
fork_exit
fork_trampoline

I've also noticed that since disabling journaling a full fsck seems to 
be occurring on boot; background fsck seems to have been disabled.

-- 
Bruce Cran