From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 23:03:30 2011 Return-Path: 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 39AFC106564A for ; Tue, 1 Mar 2011 23:03:30 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 923D78FC0C for ; Tue, 1 Mar 2011 23:03:29 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p21N3PJZ095633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Mar 2011 01:03:25 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p21N3P8I034839; Wed, 2 Mar 2011 01:03:25 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p21N3Pkg034838; Wed, 2 Mar 2011 01:03:25 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 2 Mar 2011 01:03:25 +0200 From: Kostik Belousov To: Nikos Vassiliadis Message-ID: <20110301230325.GX78089@deviant.kiev.zoral.com.ua> References: <4D6D5F15.4080009@gmx.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JApREUx0IJoLZdd8" Content-Disposition: inline In-Reply-To: <4D6D5F15.4080009@gmx.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2011 23:03:30 -0000 --JApREUx0IJoLZdd8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 01, 2011 at 11:03:17PM +0200, Nikos Vassiliadis wrote: > Hello, >=20 > I am seeing this kernel panic on a su+j ufs. It seems that > a su+j aware fsck cannot repair the file system, fsck corrects > all fs-problems it finds but the kernel panics on the first > write operation. The file system is corrected when a full fsck > takes place. This fs lives on a virtual machine and I do have a > snapshot of the fs in this problematic state in case someone > wants to investigate further. >=20 > The panic: > http://img135.imageshack.us/img135/1111/panicw.png >=20 > and a backtrace: > http://img856.imageshack.us/img856/7516/65759196.png >=20 Note that if your fs somehow managed to get a corruption by whatever means, then neither journaling not background fsck can repair it. UFS panic that explicitely mentions fs corruption shall be always followed by full fsck. --JApREUx0IJoLZdd8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk1tez0ACgkQC3+MBN1Mb4hayACfYc+g1FsaOtelr61JNseqNqME Qc4AoJ0UpgVnTdydpi3+RiIDEDAJSNwR =2efO -----END PGP SIGNATURE----- --JApREUx0IJoLZdd8--