From owner-freebsd-stable@FreeBSD.ORG Mon Sep 2 07:53:29 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CE7BE1D2; Mon, 2 Sep 2013 07:53:29 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 649AD2518; Mon, 2 Sep 2013 07:53:29 +0000 (UTC) Received: by mail-ve0-f171.google.com with SMTP id pa12so2884617veb.16 for ; Mon, 02 Sep 2013 00:53:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=T4FPVuTlO6GzqeCxkGe8sOXs3cY0Y52pOvhwbahGE4c=; b=V4bsxwungVaZZi2ugw9FfN2JahVNdVzehW2p7DDiFLEWz6FDsMola8ae4aoIIWub5v cmgCOzHxEgKStCyDJgstsVbLCscalhR30k+vGzXzZkgASiRcA50TzLyoIbW0QskksapB R33H6qNEEGI65l39MxSUMXcJNXupsh48CuxtnG8lpKWTUj8m0Bs8IkVORVVTYY5Ppcv3 9KP94WrHTv44mKk3aICll6pCVWqt+XEl8S8LuP9HGwTZIZ1jVS1e02fELKhJcOizE9F/ oaj+SAf/2jQ9Kh8X3iVQkI2Ln1Dum3wF0DrWTDwFJnWr+ggd6lAQw0UShlQKFPl5cuTp BaMg== MIME-Version: 1.0 X-Received: by 10.220.105.199 with SMTP id u7mr21497724vco.1.1378108407067; Mon, 02 Sep 2013 00:53:27 -0700 (PDT) Received: by 10.220.122.1 with HTTP; Mon, 2 Sep 2013 00:53:26 -0700 (PDT) In-Reply-To: References: <370A25C8-7747-4B96-A506-EB92FD0F77CF@FreeBSD.org> <1377895898.1111.341.camel@revolution.hippie.lan> Date: Mon, 2 Sep 2013 03:53:26 -0400 Message-ID: Subject: Re: gmirror crash writing to disk? Or is it su+j crash? From: Zaphod Beeblebrox To: =?ISO-8859-2?Q?Edward_Tomasz_Napiera=B3a?= Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable , Ian Lepore 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: Mon, 02 Sep 2013 07:53:29 -0000 The first one (kern.geom.transient_map_retries) causes the system to wedge. The second one (default is 180, I doubled to 360) causes the system to crash but not dump. So... neither fixes the problem. On Sat, Aug 31, 2013 at 5:27 AM, Edward Tomasz Napiera=B3a wrote: > Wiadomo=B6=E6 napisana przez Zaphod Beeblebrox w dniu= 31 > sie 2013, o godz. 00:49: > > Because someone said that there would be no logging of unerlying ATA > errors without verbose, I rebooted with verbose and tried the same make -= j4 > again... and here is the relatively similar core.txt.5 > > > > > https://uk.eicat.ca/owncloud/public.php?service=3Dfiles&t=3Dd99648ef5876b= 91c5957148445e60c87 > > > > Looking at it, gmirror is dropping the same error and the underlying > hardware is not causing the error... > > Let me quote Konstantin: > > > It is either an exhaustion of the transient map, or a deadlock. > > For the first, setting kern.geom.transient_map_retries to 0 could help. > > For the second, the count of the transient buffers must be increased, > > by kern.bio_transient_maxcnt loader tunable. > > Could you try both and tell which one of them fixed the problem? Thanks! > >