From owner-freebsd-stable@FreeBSD.ORG Wed Dec 4 02:41:12 2013 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 067483C5 for ; Wed, 4 Dec 2013 02:41:12 +0000 (UTC) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 674621856 for ; Wed, 4 Dec 2013 02:41:11 +0000 (UTC) X-Envelope-From: egrosbein@rdtc.ru X-Envelope-To: freebsd-stable@freebsd.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.7/8.14.7) with ESMTP id rB42f50d014420; Wed, 4 Dec 2013 09:41:05 +0700 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <529E9641.5000008@rdtc.ru> Date: Wed, 04 Dec 2013 09:41:05 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130415 Thunderbird/17.0.5 MIME-Version: 1.0 To: Matthias Andree Subject: Re: fsck_y_enable is broken for SUJ as well as fsck_ffs References: <529DA855.9040406@rdtc.ru> <529E6815.3080208@gmx.de> In-Reply-To: <529E6815.3080208@gmx.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eg.sd.rdtc.ru Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 02:41:12 -0000 On 04.12.2013 06:24, Matthias Andree wrote: [skip] > ...and then reboot, and hope for the best WRT hardware not lying to the > kernel (some makers let their drives report completion without > supercapacitors or nvram or battery backup before data was on permanent > storage in the past) - I've never tried that with RAID1 though, but on a > bare UFS2+SU+J it appears to help with avoiding SU+J inconsistencies in > Virtual machines if I forget to shut them down before rebooting the host. That's another topic - how to avoid inconsistencies. My question was "how to fix inconsistencies automatically". Eugene Grosbein