From owner-freebsd-stable@FreeBSD.ORG Tue Nov 4 18:51:21 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 566821D2 for ; Tue, 4 Nov 2014 18:51:21 +0000 (UTC) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 15A84CC9 for ; Tue, 4 Nov 2014 18:51:21 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id rp18so8128135iec.37 for ; Tue, 04 Nov 2014 10:51:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5xQ6J4LFon20gmW0ud9ezVjCBzNJBBh0x1S2uv/J124=; b=dcRCjWikaOMEooUuRJ6M2IoNuBNbbpzaxZ4kK6IPVN9J7cM+l2xkpBFUKVodtrGcgM JTr+8pHeDcMIYs35IJlLQpUT7Db6qRwcXNOTX61ncea+7nuvVf+ZYaC+wYqM+iziY9BX gTh258ug3Dwtp4YgJv0vj7JOSQI/z+BFG42D2ZnziWZMnPQfZCwpzfSp6JBVrUZC1U1q NMbtmQOF5TcgTu/X8BlVb3kl/W3halpBZCJGFFaO06VVpQAyJzUwlYFh8gcw4CKq1KVA Egf0u4Tt5V/cj+bGk6IryUMFYYvU9zTevhz1NI0vWOBoD0zolI8BGzAN/izSHSSXWsbE gugg== MIME-Version: 1.0 X-Received: by 10.50.164.194 with SMTP id ys2mr25831925igb.35.1415127080452; Tue, 04 Nov 2014 10:51:20 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Tue, 4 Nov 2014 10:51:20 -0800 (PST) In-Reply-To: References: <7479DC25-4451-4940-AFE7-7C81D08206D4@csperkins.org> <64A14F51-E115-4929-8CE9-9F786A43C9A1@csperkins.org> Date: Tue, 4 Nov 2014 10:51:20 -0800 X-Google-Sender-Auth: hMvM7KyTz4YBzCuqZdcFGJssHsY Message-ID: Subject: Re: System hang on shutdown when running freebsd-update From: Kevin Oberman To: Colin Perkins Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "Bjoern A. Zeeb" , FreeBSD-STABLE Mailing List 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, 04 Nov 2014 18:51:21 -0000 On Fri, Oct 17, 2014 at 10:23 AM, Kevin Oberman wrote: > On Fri, Oct 17, 2014 at 2:58 AM, Colin Perkins wrote: > >> On 16 Oct 2014, at 16:29, Bjoern A. Zeeb >> wrote: >> > On 15 Oct 2014, at 17:23 , Kevin Oberman wrote: >> > I have seen similar hangs on a ZFS-only system (even without >> freebsd-update I think). I have often not been patient enough to wait for >> the reboot to happen but I do remember that one time I walked away and came >> back and the system was still stuck, got distracted and by the time I got >> back again, it had rebooted. >> > >> > I wonder if anyone actually had been patient enough to wait an hour or >> two, just to see if the system moves forward all by itself? >> >> I gave up waiting after about an hour with my system that showed the >> problem. >> > > My server is production, so waiting is not an option, nor is using it for > testing. > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > > I have now run several freebsd-update operations and have always done "shutdown now" to drop into single user, then waited about 30 seconds, issued a "sync", and then "reboot". In all cases including an upgrade from 10.0-RELEASE to 10.1-RC4 with no hangs. Really looking like something needs to flush before things are REALLY shutdown and does not have time before something is killed. Going to single user seems to allow it to finish up and all is well. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com