From owner-freebsd-current@FreeBSD.ORG  Fri Jan 20 15:31:28 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id EB1FB106566B
	for <freebsd-current@freebsd.org>; Fri, 20 Jan 2012 15:31:28 +0000 (UTC)
	(envelope-from dalescott@shaw.ca)
Received: from idcmail-mo2no.shaw.ca (idcmail-mo2no.shaw.ca [64.59.134.9])
	by mx1.freebsd.org (Postfix) with ESMTP id B358A8FC1C
	for <freebsd-current@freebsd.org>; Fri, 20 Jan 2012 15:31:28 +0000 (UTC)
Received: from lb7f8hsrpno-svcs.dcs.int.inet (HELO pd6ml2no-ssvc.prod.shaw.ca)
	([10.0.144.222])
	by pd6mo1no-svcs.prod.shaw.ca with ESMTP; 20 Jan 2012 08:02:48 -0700
X-Cloudmark-SP-Filtered: true
X-Cloudmark-SP-Result: v=1.1 cv=oQE6vNJ3d7oTBHj4PDKYH99BAdyPlqTp0xAtaaBYR4E=
	c=1 sm=1
	a=32h6IRsir0wA:10 a=BLceEmwcHowA:10 a=s1lrx0EV61IYYNPiyc1Uww==:17
	a=6I5d2MoRAAAA:8 a=qCOvMRwvPJsHiHnfotUA:9 a=CjuIK1q_8ugA:10
	a=tlJW8gxtbz4A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8
	a=zhQOHNTdlabQIn1BlQQA:9 a=Tr7nZERcOiBkD3Sh-_cA:7 a=gKO2Hq4RSVkA:10
	a=hTZeC7Yk6K0A:10 a=j06pYs8rzNYA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Received: from unknown (HELO HPdv9000) ([70.73.37.138])
	by pd6ml2no-dmz.prod.shaw.ca with ESMTP; 20 Jan 2012 08:02:48 -0700
From: "Dale Scott" <dalescott@shaw.ca>
To: <freebsd-current@freebsd.org>,
	<mckusick@mckusick.com>
Date: Fri, 20 Jan 2012 08:02:49 -0700
Message-ID: <007301ccd784$93499630$b9dcc290$@shaw.ca>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-index: AczXgmLPc/LWlccUR3WCBnayGQEdaQ==
Content-language: en-us
X-Mailman-Approved-At: Fri, 20 Jan 2012 16:13:54 +0000
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: 
Subject: Re: FS hang when creating snapshots on a UFS SU+J setup
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: Fri, 20 Jan 2012 15:31:29 -0000

> First step in debugging is to find out if the problem is SU+J

> specific. To find out, turn off SU+J but leave SU. This change

> is done by running:

> 

>             umount <filesystem>

>             tunefs -j disable <filesystem>

>             mount <filesystem>

>             cd <filesystem>

>             rm .sujournal

 

Success! Thanks Mr. McKusick.

 

I posted having this problem to the FreeBSD forum
http://forums.freebsd.org/showthread.php?t=25787, but wanted to emphasize
that in two VirtualBox VMs that were created in exactly the same way, the
dump issue didn't occur in the absolutely fresh FreeBSD-9.0 install (not
even portsnap yet), but it did occur in the system I had installed some
ports on (an Apache/MySQL/Python stack, a few additional GNU build tools,
and some other miscellaneous ports). I don't know if this means anything,
just hoping it might help - presumably SU+J would be a good thing.  ;)

 

Regards,

Dale