From owner-freebsd-fs@FreeBSD.ORG  Wed Mar  2 15:57:05 2011
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id EAAE8106566B
	for <freebsd-fs@freebsd.org>; Wed,  2 Mar 2011 15:57:05 +0000 (UTC)
	(envelope-from nvass@gmx.com)
Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42])
	by mx1.freebsd.org (Postfix) with SMTP id 3E5238FC12
	for <freebsd-fs@freebsd.org>; Wed,  2 Mar 2011 15:57:05 +0000 (UTC)
Received: (qmail invoked by alias); 02 Mar 2011 15:57:03 -0000
Received: from adsl-93.109.242.21.tellas.gr (EHLO [192.168.73.192])
	[109.242.21.93]
	by mail.gmx.com (mp-eu004) with SMTP; 02 Mar 2011 16:57:03 +0100
X-Authenticated: #46156728
X-Provags-ID: V01U2FsdGVkX18fvLgwOkYfKIsDWEym5DZsA6SKwMr5rBESgivxzk
	K3UEBx2EbILqMX
Message-ID: <4D6E68CD.60507@gmx.com>
Date: Wed, 02 Mar 2011 17:57:01 +0200
From: Nikos Vassiliadis <nvass@gmx.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
	rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Kostik Belousov <kostikbel@gmail.com>
References: <4D6D5F15.4080009@gmx.com>
	<20110301230325.GX78089@deviant.kiev.zoral.com.ua>
In-Reply-To: <20110301230325.GX78089@deviant.kiev.zoral.com.ua>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: freebsd-fs@freebsd.org
Subject: Re: panic: ffx_valloc: dup alloc + SU+J  + fsck
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 15:57:06 -0000

On 3/2/2011 1:03 AM, Kostik Belousov wrote:
> Note that if your fs somehow managed to get a corruption by whatever
> means, then neither journaling not background fsck can repair it.

The corruption was the result of an unrelated to ufs kernel panic.

> UFS panic that explicitely mentions fs corruption shall be always
> followed by full fsck.

That makes sense, a ufs related panic should be followed by a full
fsck. And indeed, a full fsck fixes the fs just fine.

Thanks,

Nikos