Date: Mon, 9 Mar 2015 09:19:36 -0700 From: Nick Rogers <ncrogers@gmail.com> Cc: FreeBSD STABLE <freebsd-stable@freebsd.org> Subject: Re: freebsd-update and hang during reboot Message-ID: <CAKOb=YZvhF60oCRZdoBX0moQL5a1m_P35Fr=cH7ppPEcGi7TGg@mail.gmail.com> In-Reply-To: <CAKOb=YZUm-oWgggPmt9Av6uRGhomgSQHkjdxcbG5QB-erUDSdg@mail.gmail.com> References: <2F9DC176-912C-40C0-BAB7-DB66BD572ABA@vnode.se> <54D8E341.101@pix.net> <1423501720.16794.18.camel@freebsd.org> <CAKOb=YZUm-oWgggPmt9Av6uRGhomgSQHkjdxcbG5QB-erUDSdg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 10, 2015 at 1:37 PM, Nick Rogers <ncrogers@gmail.com> wrote: > > > On Mon, Feb 9, 2015 at 9:08 AM, Ian Lepore <ian@freebsd.org> 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 "Al= l >> 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 han= gs. >> > > >> > > I=E2=80=99ve tried it on several different HP ProLiant models, on In= tel 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 thin= k >> 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 proble= m, 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. > Is anyone working on fixing this problem? It seems like this should have some kind of "full court press" as it is obviously affecting plenty of people, some of which have spoken up in the following PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195458 I realize its a tough problem to track down, and if I had the appropriate skills I would help. But so far all I've been able to do, like others, is replicate and complain about the problem. Its still affecting upgrading to 10.1-RELEASE-p6 from the official 10.1-RELEASE distribution, and from 10.1-RELEASE-p5. I just had another production server hang during reboot after updating to p6, and I don't see this changing for the inevitable p7 unless this problem gets more attention. Can someone with the right skill-set please help figure this out? Thank you. >> -- 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= " >> > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKOb=YZvhF60oCRZdoBX0moQL5a1m_P35Fr=cH7ppPEcGi7TGg>