From owner-freebsd-current@FreeBSD.ORG Fri Mar 1 06:22:51 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7AACA312; Fri, 1 Mar 2013 06:22:51 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2501C9DE; Fri, 1 Mar 2013 06:22:51 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:9421:367:9d7d:512b]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id E0E064AC57; Fri, 1 Mar 2013 10:22:43 +0400 (MSK) Date: Fri, 1 Mar 2013 10:22:37 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <352538988.20130301102237@serebryakov.spb.ru> To: Don Lewis Subject: Re: Panic in ffs_valloc (Was: Unexpected SU+J inconsistency AGAIN -- please, don't shift topic to ZFS!) In-Reply-To: <201303010511.r215BWoU092532@gw.catspoiler.org> References: <1698593972.20130228164821@serebryakov.spb.ru> <201303010511.r215BWoU092532@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-5 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 06:22:51 -0000 Hello, Don. You wrote 1 =DC=D0=E0=E2=D0 2013 =D3., 9:11:32: DL> The fact that the filesystem code called panic() indicates that the DL> filesystem was already corrupt by that point. That's a likely reason DL> for fsck complaining about the unexpected SU+J inconsistency. DL> Incorrect write ordering that allowed the filesystem to become DL> inconsistent because some pending writes were lost because of the panic DL> might not be necessary, but this might have allowed an earlier crash DL> where a full fsck was skipped to leave the filesystem in this state. As far, as I understand, if this theory is right (file system corruption which left unnoticed by "standard" fsck), it is bug in FFS SU+J too, as it should not be corrupted by reordered writes (if writes is properly reported as completed even if they were reordered). DL> This panic might also be a result of the bug fixed in 246877, but I have DL> my doubts about that. It was not MFCed :( --=20 // Black Lion AKA Lev Serebryakov