From owner-freebsd-stable@FreeBSD.ORG  Tue Jul  1 10:57:07 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 9720C34E
 for <freebsd-stable@freebsd.org>; Tue,  1 Jul 2014 10:57:07 +0000 (UTC)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com
 [IPv6:2a00:1450:4010:c03::22f])
 (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 1CC5E2130
 for <freebsd-stable@freebsd.org>; Tue,  1 Jul 2014 10:57:06 +0000 (UTC)
Received: by mail-la0-f47.google.com with SMTP id s18so5692699lam.20
 for <freebsd-stable@freebsd.org>; Tue, 01 Jul 2014 03:57:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=content-type:mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=cHf3Ntl4rdi4rSUx4Cmpj0RRRFYgNt9tv3KsEaI2mr8=;
 b=WaE6S096X0EuGtQWHeeTr+6UPNxnD+h8yXknyI/0hZ/fdEKKUKsotbYchac3xVQpKe
 yoVUgzFqiQVVbbUA2omCOOJQBgBpfNAiossnEEwYDm0v4ngGVJJ7YJqKZCSDtQOZV5dl
 xQUYdk5UTSaxpBkO99EPvXeS90CyzQQHSf1pnAnhWAzCVy9Uc2kedXJdYDvL8/gh6q8Q
 auYhZeuzPhMQUb+zl1lCA+JJtTNluI5sA7XzSvQKDGLhzULa19ZFAGm0k8HokYPtTaaR
 YItF8IpowLhZX3l0GXYQk5SSrCH9NOFvnoCbQUO3D2FW5XMzIAbRBlbHxZ5hYhLXFPlt
 VlKg==
X-Received: by 10.112.156.199 with SMTP id wg7mr34452587lbb.1.1404212224829;
 Tue, 01 Jul 2014 03:57:04 -0700 (PDT)
Received: from 95.108.173.189-red.dhcp.yndx.net
 (95.108.173.189-red.dhcp.yndx.net. [95.108.173.189])
 by mx.google.com with ESMTPSA id uh6sm10075646lac.13.2014.07.01.03.57.03
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Tue, 01 Jul 2014 03:57:03 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: 10/stable panic: softdep_deallocate_dependencies: dangling deps
From: Dmitry Sivachenko <trtrmitya@gmail.com>
In-Reply-To: <op.xia61kp0kndu52@ronaldradial.radialsg.local>
Date: Tue, 1 Jul 2014 14:57:01 +0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F84286C1-EB0F-4049-A567-1BB0E0FD19AE@gmail.com>
References: <021AFCAD-7B0B-47FB-AAFF-8F7085C7E1A6@gmail.com>
 <op.xia61kp0kndu52@ronaldradial.radialsg.local>
To: Ronald Klop <ronald-lists@klop.ws>
X-Mailer: Apple Mail (2.1878.2)
Cc: freebsd-stable@freebsd.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18
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: Tue, 01 Jul 2014 10:57:07 -0000


On 01 =D0=B8=D1=8E=D0=BB=D1=8F 2014 =D0=B3., at 11:57, Ronald Klop =
<ronald-lists@klop.ws> wrote:

> On Mon, 30 Jun 2014 14:22:02 +0200, Dmitry Sivachenko =
<trtrmitya@gmail.com> wrote:
>=20
>> Hello!
>>=20
>> I have several machines with rather fresh FreeBSD-10/stable.
>>=20
>> They all have 4 SATA drives, I have small gmirrored root+var and the =
rest of the drive space is mounted as /disk1, /disk2, etc (UFS2+SU).
>> When a single disk fails, system panics with =
"softdep_deallocate_dependencies: dangling deps" message:
>> http://people.freebsd.org/~demon/softdep.png
>>=20
>> Since all vital data (root+var) are mirrored, I expect OS to stay =
alive.
>=20
> Hi,
>=20
> So /disk1, /disk2 are not (g)mirrored? In that case the system cannot =
handle write failure. Because writes are not synchronous (for speed) =
there is no possibility to return an error to the application.


No, they are not (g)mirrored.
I expect read/write errors, but not kernel panic.  Actually I =
encountered disk I/O errors since 2.2.5 and it is first time I faced =
kernel panic.