From owner-freebsd-stable@FreeBSD.ORG  Sat Aug 31 09:27:19 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 85A417FC;
 Sat, 31 Aug 2013 09:27:19 +0000 (UTC)
 (envelope-from etnapierala@gmail.com)
Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com
 [IPv6:2a00:1450:4008:c01::233])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id DBEB225A0;
 Sat, 31 Aug 2013 09:27:18 +0000 (UTC)
Received: by mail-bk0-f51.google.com with SMTP id mx10so994645bkb.10
 for <multiple recipients>; Sat, 31 Aug 2013 02:27:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=CvQhmtEWBBHmd7iZIkMXYXSwlrX+AL7eMc1kjFbebEY=;
 b=jOsBwmNN8UB4N8yn/W9wPVza/Cipg6O1yJbLJDYfcAZMcfidxxgc7TZM+fS0UoPmGZ
 t02doXt0khw2ZPe1W6JmVVfaL1WUAFXOeSAYaT5VwnvBi/w4K/8oWCTnf+CHoCeYAS6X
 Bqod87VQEebfrDsMaQ5LoCSFNi73BxNRJ0Aq5huYEtpd5jzDxFtiGIPGfHSID2xd7KAX
 X4zQiV07NTnzZTwjW0zP9Qr7mzjRMP6cirvexjhEpElaFgvKwP4KAxQc2Th0ScgfD9pc
 MRoALKgebXq8KJCESLR28mUSVOgOci9/7KdXkNxJqNIWQbwf6uH5+ccotyGDLTsQEy10
 G16w==
X-Received: by 10.204.224.142 with SMTP id io14mr482454bkb.27.1377941236130;
 Sat, 31 Aug 2013 02:27:16 -0700 (PDT)
Received: from [192.168.1.102] (addr147.neoplus.adsl.tpnet.pl. [79.184.69.147])
 by mx.google.com with ESMTPSA id nv4sm260411bkb.3.1969.12.31.16.00.00
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Sat, 31 Aug 2013 02:27:15 -0700 (PDT)
Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= <etnapierala@gmail.com>
Content-Type: text/plain; charset=iso-8859-2
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: gmirror crash writing to disk? Or is it su+j crash?
From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@freebsd.org>
In-Reply-To: <CACpH0Mc+egqb7V9=bJ73VpzLvc5K0cTRN6fQZOkBwPD_TetRDg@mail.gmail.com>
Date: Sat, 31 Aug 2013 11:27:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8B0CAB6-6646-4AA0-A03C-412C2438716D@freebsd.org>
References: <CACpH0MdU5NMi=GvYbG5W-F-UkH=s89d8Docvz8_KS0+fqNH1cQ@mail.gmail.com>
 <370A25C8-7747-4B96-A506-EB92FD0F77CF@FreeBSD.org>
 <1377895898.1111.341.camel@revolution.hippie.lan>
 <CACpH0MeOG9v422AdpGpbos6mTLFu69PNXmP3ZFTV66Vc=H9Eew@mail.gmail.com>
 <CACpH0Mc+egqb7V9=bJ73VpzLvc5K0cTRN6fQZOkBwPD_TetRDg@mail.gmail.com>
To: Zaphod Beeblebrox <zbeeble@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, Ian Lepore <ian@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 09:27:19 -0000

Wiadomo=B6=E6 napisana przez Zaphod Beeblebrox <zbeeble@gmail.com> 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
>=20
> =
https://uk.eicat.ca/owncloud/public.php?service=3Dfiles&t=3Dd99648ef5876b9=
1c5957148445e60c87
>=20
> 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!