From owner-freebsd-bugs@FreeBSD.ORG  Wed Jan 14 09:44:09 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 068C5F48
 for <freebsd-bugs@FreeBSD.org>; Wed, 14 Jan 2015 09:44:09 +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 E1C1B69D
 for <freebsd-bugs@FreeBSD.org>; Wed, 14 Jan 2015 09:44:08 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0E9i8Ko085336
 for <freebsd-bugs@FreeBSD.org>; Wed, 14 Jan 2015 09:44:08 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: Wed, 14 Jan 2015 09:44:07 +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: iamasmith.home@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: cc
Message-ID: <bug-195458-8-0VdxzG6GW7@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: Wed, 14 Jan 2015 09:44:09 -0000

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

Andrew Smith <iamasmith.home@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |iamasmith.home@gmail.com

--- Comment #10 from Andrew Smith <iamasmith.home@gmail.com> ---
It seems that this at last effects all Kernels since 10.1-RELEASE through p3.

If you have one of these Kernels with Softupdates active on the root filesystem
and you replace /sbin/init then you get this behaviour.

If you either disable file system softupdates on the filesystem or you disable
the softupdates option in a new Kernel build then the issue does not exist.

I suspect people that haven't had this issue have some other environmental
difference that nobody has highlighted yet.

The issue of course hits 10.0-RELEASE to 10.1-RELEASE upgrades since when
freebsd-update install is run, the first thing done is to replace the Kernel
and ask for a reboot then run freebsd-update again. The Kernel exhibiting the
problem is then in place.

Could this be related to the changes made to ufs for the per FFS-Filesystem
threading around August? (r269457, r269533, r269583).

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