Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Jul 2014 14:57:01 +0400
From:      Dmitry Sivachenko <trtrmitya@gmail.com>
To:        Ronald Klop <ronald-lists@klop.ws>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: 10/stable panic: softdep_deallocate_dependencies: dangling deps
Message-ID:  <F84286C1-EB0F-4049-A567-1BB0E0FD19AE@gmail.com>
In-Reply-To: <op.xia61kp0kndu52@ronaldradial.radialsg.local>
References:  <021AFCAD-7B0B-47FB-AAFF-8F7085C7E1A6@gmail.com> <op.xia61kp0kndu52@ronaldradial.radialsg.local>

next in thread | previous in thread | raw e-mail | index | archive | help

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.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F84286C1-EB0F-4049-A567-1BB0E0FD19AE>