From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 13:37:02 2014 Return-Path: Delivered-To: freebsd-stable@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 41152867 for ; Wed, 10 Dec 2014 13:37:02 +0000 (UTC) Received: from icp-osb-irony-out1.external.iinet.net.au (icp-osb-irony-out1.external.iinet.net.au [203.59.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id B9B4E1B4 for ; Wed, 10 Dec 2014 13:37:01 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiAGANBLiFR90bfD/2dsb2JhbABZgwa0YQEBAQEBAQaYNwKBFxYBAQEBAX2EAwEFMgFGEAsNFCUPBRgdFBOIN9dMAQEBAQYCIIYNiXYHgyGBFQWWcoENhF0lhR6GLoQCKjCCQwEBAQ X-IronPort-AV: E=Sophos;i="5.07,552,1413216000"; d="scan'208";a="281076578" Received: from unknown (HELO smtp.phoenix) ([125.209.183.195]) by icp-osb-irony-out1.iinet.net.au with ESMTP; 10 Dec 2014 21:36:59 +0800 Received: by smtp.phoenix (Postfix, from userid 1001) id 89A7175D; Thu, 11 Dec 2014 00:36:58 +1100 (AEDT) Date: Thu, 11 Dec 2014 00:36:58 +1100 From: andrew clarke To: Juan =?iso-8859-1?Q?Ram=F3n?= Molina Menor Subject: Re: System hang on shutdown when running freebsd-update Message-ID: <20141210133658.GA12721@ozzmosis.com> References: <548846F8.4080208@club-internet.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <548846F8.4080208@club-internet.fr> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org 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: Wed, 10 Dec 2014 13:37:02 -0000 On Wed 2014-12-10 14:13:28 UTC+0100, Juan Ramón Molina Menor (listjm@club-internet.fr) wrote: > > >/ Another update. I narrowed down the issue due to /sbin/init being > > >replaced. This might be the magic that freebsd-update does to make the > > >crash happen. (Although there might be more situations that cause a > > >hang.) > > > > />/ I can completely reliably trigger the hang on a default > > />/ 10.1-RELEASE install on UFS2 in VMware Fusion with the following > > >>/ procedure: > > />/ > > />/ # chflags noschg /sbin/init > > />/ # cp -Rp /sbin/init /sbin/init2 > > />/ # rm -f /sbin/init > > />/ # mv /sbin/init2 /sbin/init > > />/ # chflags schg /sbin/init > > />/ # reboot > > />/ => Hang after "All buffers synced." > > /These commands do not trigger the issue here on a 10.1-RELEASE on VMware > > Player, but do it in a real system with the same release, both i386. > > When I last freebsd-updated this latter machine from 10.0 to > > 10.1-RELEASE, I also remember seeing the hang on shutdown. > > > > Hope it helps, > > Juan > > The hang occurs again when running freebsd-update to install the > security advisories of today on a 10.1-RELEASE i386. No problem under > VMWare, same version. > > Best regards, > Juan A FreeBSD 10.1-REL amd64 VM here also hangs after /sbin/reboot is run, after installing updates with freebsd-update. The VM runs under VirtualBox on an Ubuntu 14.04 host. On hard-resetting the VM, it appears the filesystem (UFS) wasn't flushed: Dec 11 00:29:52 vbox-freebsd kernel: WARNING: / was not properly dismounted Regards Andrew