Date: Sun, 23 Jun 2013 15:05:19 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Jeremy Chadwick <jdc@koitsu.org> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, Adam Strohl <adams-freebsd@ateamsystems.com> Subject: Re: shutdown -r / shutdown -h / reboot all hang and don't cleanly dismount Message-ID: <E8C6BEF5-524E-4ABD-BC65-730BCABD0599@digiware.nl> In-Reply-To: <20130623011544.GA77759@icarus.home.lan> References: <51C1979D.3010305@ateamsystems.com> <20130619122143.GA70813@icarus.home.lan> <51C1A9BF.8030304@ateamsystems.com> <20130619133538.GA71689@icarus.home.lan> <51C1BCF6.8090606@ateamsystems.com> <20130619150414.GA72566@icarus.home.lan> <51C64437.3000007@digiware.nl> <20130623011544.GA77759@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Op 23 jun. 2013 om 03:15 heeft Jeremy Chadwick <jdc@koitsu.org> het volgende= geschreven: > On Sun, Jun 23, 2013 at 02:41:27AM +0200, Willem Jan Withagen wrote: >> On 19-6-2013 17:04, Jeremy Chadwick wrote: >>> - Adam runs 9.1-RELEASE because of business needs pertaining to >>> freebsd-update and binary updates. (I ask more about this for >>> benefits of readers below, however -- because this situation comes >>> up a lot and I want to know what real-world admins do) >>=20 >> The bug is very specifically available in 9.1-RELEASE because I got >> bit by it before the release of 9.1. But discussed it with avg@ and >> it did not make it into the release, but was submitted only like 2 >> weeks later. >>=20 >> So in that case you can probably stop looking. >>=20 >> For just about any 9.1-STABLE after that should the fix be in the code. >=20 > I'm not sure why so many people (so far) seem to think that this problem > is always the same issue -- it isn't. There are multiple things that > have historically (and/or presently) have caused this issue. >=20 > Here's the list I composed only a few days ago, and it is far from > thorough: >=20 > http://lists.freebsd.org/pipermail/freebsd-stable/2013-June/073863.html >=20 Being in software for over 30 years I assume very little about: it's correctness. But I assume that it could be me, causing pilot-errors. So what I was trying to say: Several of the bugs in this range were fixed shortly after the 9.1-release, s= o the first step I'd like to suggest, is to get beyond this point in the rel= ease stream. And test again. My reasoning was more the other way around: unless you have gone to a releas= e with at least these fixes, you cannot tell whether it is already fixed or n= ot. Until then, a lot of the debugging could be not fully usefull. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E8C6BEF5-524E-4ABD-BC65-730BCABD0599>