From owner-freebsd-stable@FreeBSD.ORG Tue Feb 10 21:37:40 2015 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 20A2B145; Tue, 10 Feb 2015 21:37:40 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8031BBF1; Tue, 10 Feb 2015 21:37:39 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id u10so25565780lbd.7; Tue, 10 Feb 2015 13:37:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bFCC9pQhxTeJptAMsfdmHzj2ZDOPeJbEZjuAKdgV3FE=; b=N86hPGrCmCA2eGdwp+ltqEKkgHeOsoG7XTiWd5qLWq/+cBvYKq8E55XE6uF9RkQskl OCxAn2LwvvC+rv1+E9Yh0D1YyC1oyKA0oXrQxxH/w3Cez1GEaS74ac0QUSsndrBzLzYD qRnoO9trnJw2m062PqE3PybObiTZcDVV6Bk4MEPBDnch8jh4I0I7fB+8w/3Mpvk+5qUO K76L/cWOloyuhVvzIj8WNBH16c1qFiiG16LYNoKROw69Gg2su78XDpUq8uHYfTvYmGo+ YJGvaQtg2TWQ5dUl6IAof+eADT2ukQgep98JD0HklVvJv3bvYos95NBymHFkVt2PrKrJ SWcA== MIME-Version: 1.0 X-Received: by 10.112.164.101 with SMTP id yp5mr25039824lbb.82.1423604257331; Tue, 10 Feb 2015 13:37:37 -0800 (PST) Received: by 10.25.76.131 with HTTP; Tue, 10 Feb 2015 13:37:37 -0800 (PST) In-Reply-To: <1423501720.16794.18.camel@freebsd.org> References: <2F9DC176-912C-40C0-BAB7-DB66BD572ABA@vnode.se> <54D8E341.101@pix.net> <1423501720.16794.18.camel@freebsd.org> Date: Tue, 10 Feb 2015 13:37:37 -0800 Message-ID: Subject: Re: freebsd-update and hang during reboot From: Nick Rogers To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD STABLE , Kurt Lidl 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: Tue, 10 Feb 2015 21:37:40 -0000 On Mon, Feb 9, 2015 at 9:08 AM, Ian Lepore wrote: > On Mon, 2015-02-09 at 11:41 -0500, Kurt Lidl wrote: > > Joel wrote: > > > Hi, > > > > > > Just about every machine I have seems to hang after running > freebsd-update and doing a reboot. The last message on the screen is "All > buffers synced=E2=80=9D and it just freezes. > > > > > > This happens when doing a freebsd-update and going from 10.0 to 10.1, > but also when doing a fresh 10.1 install and using freebsd-update to get > the latest -pX security patches. As soon as I reboot the machine, it hang= s. > > > > > > I=E2=80=99ve tried it on several different HP ProLiant models, on Int= el NUCs > and on VMware virtual machines. Same phenomenon everywhere. It=E2=80=99s = really > easy to trigger: just install 10.1, use default settings everywhere, > freebsd-update fetch/install, shutdown -r now and BOOM. It hangs. I think > I=E2=80=99ve seen it on > > > > > > > > > > > > > > > 30 servers or so now. > > > > > > Everything works like it should after the initial hang tough - no > matter how many times I reboot it completes the reboot cycle just fine. > > > > > > I=E2=80=99ve seen several people (mostly on IRC) mention this problem= , but no > solution. > > > > > > Is anyone working on fixing this? > > > > I ran into this problem in spades when upgrading a set of servers from > > FreeBSD 9.0 to 9.1. I happened consistently. Normal reboots worked, > > but when going from 9.0 to 9.1, it *ALWAYS* hung, and it always hung > > at the same place, after printing the "All buffers synced" message. > > > > I ultimately determined that if I did the following, rather than > > just a "reboot" or "shutdown -r now 'FreeBSD 9.1-RELEASE upgrade'", > > it would consistently AVOID the hang: > > > > sync ; sync ; sync ; shutdown -o -n -r now "FreeBSD 9.1 install" > > > > Your mileage may vary, but you don't have a lot to lose by trying it. > > > > -Kurt > > > > That is just bad advice. sync(1) does not g'tee that all data has been > written, no matter how many times you type it. shutdown -n tells the > system to abandon unwritten data. All in all, this is a recipe for > silent filesystem corruption. Using it after an update is just asking > to have a mix of old and new files on the system after the reboot. > > A more robust workaround would be to "mount -r" on all filesystems > before invoking the shutdown (even a shutdown -n should be safe after > everything has been remounted readonly). If the mount -r hangs on one > of the filesystems, then you've probably got a clue as to where a normal > shutdown is hanging. > FWIW mount -r on the root filesystem hangs for me. If I disable softupdates-journaling on the root filesystem before the upgrade process, the system no longer hangs on the last reboot after userland upgrade. However, the root filesystem still comes up dirty with an incorrect free block count during fsck. > -- Ian > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >