Date: Mon, 25 May 2015 00:59:09 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-current@freebsd.org Subject: FreeBSD_HEAD-tests - Build #1056 - Unstable Message-ID: <64154000.57.1432515549964.JavaMail.jenkins@jenkins-9.freebsd.org>
next in thread | raw e-mail | index | archive | help
FreeBSD_HEAD-tests - Build #1056 - Unstable: Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1056/ to view the results. From owner-freebsd-current@FreeBSD.ORG Mon May 25 01:10:45 2015 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@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 37677928 for <freebsd-current@freebsd.org>; Mon, 25 May 2015 01:10:45 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (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 F25D9345 for <freebsd-current@freebsd.org>; Mon, 25 May 2015 01:10:44 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by igbhj9 with SMTP id hj9so27715419igb.1 for <freebsd-current@freebsd.org>; Sun, 24 May 2015 18:10:44 -0700 (PDT) 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=aeckTLmlZu0awCxlzAj8nIi/3u8O3w94Fo8sktnMZXA=; b=lk49ZLSpzjwDMwYEBgRKcPHi/22zbEVeaOv5RwS52jWpURWBh/Yj3WFP7ZNdba2gwt BKnbQgzcc3Winr7bI0vPY2faUuR2+r3u65oO62I7s3NVjowsRBUvONOtZHwn13l98tDl G7TiI+twIaFLp7PKmPn2Df3qWVucjxrBSD4u7KCt0MqFPwiM0uelPxjNa0koQKGAGUGA ijKRZVfonEN+Z8zQ+GKJl2Y0Ra4uaS+zKzgA3tuSGz25avCyfEyEoVvvYGwG8EejbdgB ytx+L/CEFyPYcG5UdiLaIixij/GPpdntionCKdWOqJtjdeO3+TZRv+3Lt4+UM+IlQnu9 nJaQ== MIME-Version: 1.0 X-Received: by 10.50.57.112 with SMTP id h16mr20128803igq.35.1432516244495; Sun, 24 May 2015 18:10:44 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.174.22 with HTTP; Sun, 24 May 2015 18:10:44 -0700 (PDT) In-Reply-To: <D6DC0EEA-3929-4258-986C-3FCBDBC5D9EB@gmail.com> References: <CACyC=qY62b5=6=T9dwuWASXeOREMkhafXcUpqt3ctYJHTnJF8A@mail.gmail.com> <D6DC0EEA-3929-4258-986C-3FCBDBC5D9EB@gmail.com> Date: Sun, 24 May 2015 18:10:44 -0700 X-Google-Sender-Auth: Lt1r48uy9vepA-TCPKLXqDM6qe8 Message-ID: <CAN6yY1vXv0GKPHc1xbF+K5i0kzULpuWE6LhWa=18GuuFthYD+Q@mail.gmail.com> Subject: Re: Slow shutdown From: Kevin Oberman <rkoberman@gmail.com> To: Garrett Cooper <yaneurabeya@gmail.com> Cc: "Ranjan1018 ." <214748mv@gmail.com>, FreeBSD CURRENT <freebsd-current@freebsd.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 25 May 2015 01:10:45 -0000 On Sun, May 24, 2015 at 1:33 PM, Garrett Cooper <yaneurabeya@gmail.com> wrote: > On May 24, 2015, at 6:33, Ranjan1018 . <214748mv@gmail.com> wrote: > > > On my laptop running r283297, after the message =E2=80=9CAll buffers sy= nced.=E2=80=9D and > > before =E2=80=9CUptime: =E2=80=A6..=E2=80=9D it takes more than 55 seco= nds. > > Not a lot of info here to diagnose your issue... > - What happens if you hit control-t, i.e. what wait channel does it print > out? > - What filesystems do you have mounted (fuse, NFS, UFS, ZFS)? > - What=E2=80=99s your root media (SSDs, SATA/PATA hard drives, etc)? > > Thanks.. > By this point in the shutdown, ctrl-t (and the shell, itself) are no longer available. This feels like it might be related to the very messy issue with shutdown that triggered the EN and patched 10.1 release. That one was the result of a composite of several bugs and is believed fixed, but,in most cases, shutting down to single user and waiting for 1 minute (pretty close to 55 seconds) before issuing a halt fixed the problem. One difference... a "shutdown -r" or "shutdown -p" never completed. It just hung. At least an odd coincidence. This issue only occurred on SU+J UFS file systems. Since this is default for UFS systems, it's pretty likely that any UFS file systems are SU+J. You can try turning this off (tunefs(9)) and see if it helps. If you crash without this, the fsck will take a while, though, if it is a large FS. It was patched in 10.1 with r282873. I have only heard of this bug impacting 10.1, not head, but the similarity makes me suspect some link. -- Kevin Oberman, Network Engineer, Retired
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64154000.57.1432515549964.JavaMail.jenkins>