From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 05:27:59 2012 Return-Path: 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 3B470106564A for ; Tue, 3 Jan 2012 05:27:59 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id C9EDD8FC13 for ; Tue, 3 Jan 2012 05:27:58 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so27097782wgb.31 for ; Mon, 02 Jan 2012 21:27:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.208.133 with SMTP id gc5mr49724358wbb.25.1325568477518; Mon, 02 Jan 2012 21:27:57 -0800 (PST) Received: by 10.216.159.135 with HTTP; Mon, 2 Jan 2012 21:27:57 -0800 (PST) In-Reply-To: References: Date: Mon, 2 Jan 2012 23:27:57 -0600 Message-ID: From: Bryce Edwards To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2012 05:27:59 -0000 I have a RELENG_9 machine that hangs when a snapshot is created on the root fs (UFS, with SU+J). =A0More accurately, all the processes show a state of "suspfs" (with ^T) and no fs activity is completed from then on. =A0A hard reboot (power cycle) was the only way to proceed. Here's some reference info - let me know what else I should provide. $uname -a FreeBSD xxx.xxx.net 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0: Sun Dec 25 05:04:37 UTC 2011 =A0 =A0 root@xxx.xxx.net:/usr/obj/usr/src/sys/GENERIC amd64 csup was run just before build[world|kernel] so you have reference on the version information. $mount /dev/gpt/root on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) linprocfs on /compat/linux/proc (linprocfs, local) { zfs info removed } $df -h Filesystem =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Size =A0 =A0Used =A0 Avail Ca= pacity =A0Mounted on /dev/gpt/root =A0 =A0 =A0 =A0 =A0 =A0 =A0 454G =A0 =A09.1G =A0 =A0409G =A0 = =A0 2% =A0 =A0/ devfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1.0k =A0 =A01.0k =A0 =A0 = =A00B =A0 100% =A0 =A0/dev linprocfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.0k =A0 =A04.0k =A0 =A0 =A00= B =A0 100% =A0 =A0/compat/linux/proc { zfs info removed } After the hard reset, there was a snapshot file listed in /.snap and it was ~465 GB, iirc. =A0Unfortunately, I needed to get things going again so I was not able to debug or diagnose further. =A0I may be able to schedule a time that I could recreate the issue and diagnose better, but I wanted to get your input on what data points and/or command you would be interested in. Thanks in advance, Bryce