From owner-freebsd-bugs@FreeBSD.ORG  Tue Mar 10 19:34:36 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@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 9DAB59B2
 for <freebsd-bugs@FreeBSD.org>; Tue, 10 Mar 2015 19:34:36 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 83E78238
 for <freebsd-bugs@FreeBSD.org>; Tue, 10 Mar 2015 19:34:36 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2AJYa0V028269
 for <freebsd-bugs@FreeBSD.org>; Tue, 10 Mar 2015 19:34:36 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195458] Hang on shutdown/root unmount after FreeBSD 10.1R upgrade
Date: Tue, 10 Mar 2015 19:34:32 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: rkoberman@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-195458-8-u2iQ4Nona7@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195458-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195458-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2015 19:34:36 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195458

--- Comment #49 from rkoberman@gmail.com ---
(In reply to Guy Helmer from comment #47)
I suspect that this is a different, though possibly related issue. In all cases
reported, while all filesystems were unclean on reboot, fsck never found any
errors on my system and ended up simply marking he volume "clean" (after a long
time had passed).

OTOH, the problem started on a system that had installed 10.0-R right after I
received it and figured out how to turn off boot signature checking so I could
boot the memstick install media. (That was hidden several menus deep in a menu
that only could be brought up when another, seemingly unrelated BIOS option was
modified.)

I can say that before I retired and still had many FreeBSD systems to maintain
that I never saw this with freebsd-update. Those were all version 9 systems,
and all were physical system, no virtualization involved.

-- 
You are receiving this mail because:
You are the assignee for the bug.