From owner-freebsd-stable@FreeBSD.ORG Sun Jun 23 13:05:14 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B4680F4 for ; Sun, 23 Jun 2013 13:05:14 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) by mx1.freebsd.org (Postfix) with ESMTP id 76FBE1C29 for ; Sun, 23 Jun 2013 13:05:14 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 55A4A153434; Sun, 23 Jun 2013 15:05:13 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FaXZHzVZaXGo; Sun, 23 Jun 2013 15:05:12 +0200 (CEST) Received: from [192.168.10.120] (10G [192.168.10.120]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPS id 0449A153433; Sun, 23 Jun 2013 15:05:12 +0200 (CEST) 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> In-Reply-To: <20130623011544.GA77759@icarus.home.lan> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: X-Mailer: iPad Mail (9B206) From: Willem Jan Withagen Subject: Re: shutdown -r / shutdown -h / reboot all hang and don't cleanly dismount Date: Sun, 23 Jun 2013 15:05:19 +0200 To: Jeremy Chadwick Cc: "freebsd-stable@freebsd.org" , Adam Strohl X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2013 13:05:14 -0000 Op 23 jun. 2013 om 03:15 heeft Jeremy Chadwick 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