From owner-freebsd-stable@FreeBSD.ORG Tue Jul 1 19:17:28 2014 Return-Path: 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 DB28D5FD; Tue, 1 Jul 2014 19:17:28 +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 33E9724F8; Tue, 1 Jul 2014 19:17:28 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id s18so6170002lam.20 for ; Tue, 01 Jul 2014 12:17:26 -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=8rlQyNMyRfY5izNlDIcxbb6mXmqVkqeX5cpdFbYXxL0=; b=L8QEyIGBmPOIYldjJciSHiIONDhhm/PbXswGaVOjt5i4zKerC41KWPY/ywkKNJxB62 k8LL9RDNE/ZiqhNGG4Zytkht5T5XgFqG1uOrUNV2Esm60NoKEuU50kQr8jfcp6Y+id5v hbZgzYKgiYhYtAT44rrETAUFrfSQw5u/CEUezaVA9i5IyAWehum1OCT/Vg2Hl3NSUB9t xzXjLe7Q0+boFfdFsdb7OMm8ZEvNEQc7X1dH9vxLhB8/hu3WiaZzTxZm94c2dB5WBY33 /7K9BhBzU8YPh0gK5qZ+EzgOKXAN6rDOqgEbSpkpFoz/slbSz30MMDfvZVIt3cHJ6e8c IMTg== X-Received: by 10.112.84.199 with SMTP id b7mr33121189lbz.25.1404242246052; Tue, 01 Jul 2014 12:17:26 -0700 (PDT) Received: from [10.0.1.2] ([176.193.57.15]) by mx.google.com with ESMTPSA id q3sm10622355lae.23.2014.07.01.12.17.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Jul 2014 12:17:23 -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 In-Reply-To: <20140701184749.GA8617@brick.home> Date: Tue, 1 Jul 2014 23:17:22 +0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <021AFCAD-7B0B-47FB-AAFF-8F7085C7E1A6@gmail.com> <20140701184749.GA8617@brick.home> To: =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-Mailer: Apple Mail (2.1878.2) Cc: freebsd-stable@freebsd.org, Ronald Klop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2014 19:17:28 -0000 On 01 =D0=B8=D1=8E=D0=BB=D1=8F 2014 =D0=B3., at 22:47, Edward Tomasz = Napiera=C5=82a wrote: >=20 > Soft updates cannot gracefully handle IO errors. It _will_ panic. > You can either prevent errors from happening by using redundancy > (ie. mirroring), or disable soft updates. That's how it works, > sorry. >=20 > In theory it would be possible to prevent this from happening; > panic here is actually to terminate the system before it corrupts > data, and in situations like this one, where the disk is no longer > accessible, it's not possible to corrupt anything. IIRC I've > actually added a workaround for that a while ago, but, as you can > see, it's not enough, and I don't understand soft updates well > enough to fix it properly. >=20 Will ZFS fail without a panic? Or UFS without SU is the only choice?=