From owner-freebsd-stable@FreeBSD.ORG Fri Oct 17 09:58:43 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13825511 for ; Fri, 17 Oct 2014 09:58:43 +0000 (UTC) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCC72F5B for ; Fri, 17 Oct 2014 09:58:42 +0000 (UTC) Received: from [130.209.247.112] (port=54919 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Xf4Iw-00051i-6K; Fri, 17 Oct 2014 10:58:38 +0100 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: System hang on shutdown when running freebsd-update From: Colin Perkins In-Reply-To: Date: Fri, 17 Oct 2014 10:58:27 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <64A14F51-E115-4929-8CE9-9F786A43C9A1@csperkins.org> References: <7479DC25-4451-4940-AFE7-7C81D08206D4@csperkins.org> To: "Bjoern A. Zeeb" X-Mailer: Apple Mail (2.1878.6) X-BlackCat-Spam-Score: -28 X-Mythic-Debug: Threshold = On = X-Spam-Status: No, score=-2.9 Cc: Kevin Oberman , FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 09:58:43 -0000 On 16 Oct 2014, at 16:29, Bjoern A. Zeeb = wrote: > On 15 Oct 2014, at 17:23 , Kevin Oberman wrote: > I have seen similar hangs on a ZFS-only system (even without = freebsd-update I think). I have often not been patient enough to wait = for the reboot to happen but I do remember that one time I walked away = and came back and the system was still stuck, got distracted and by the = time I got back again, it had rebooted. >=20 > I wonder if anyone actually had been patient enough to wait an hour or = two, just to see if the system moves forward all by itself? I gave up waiting after about an hour with my system that showed the = problem. --=20 Colin Perkins https://csperkins.org/