Date: Wed, 2 Mar 2011 01:03:25 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Nikos Vassiliadis <nvass@gmx.com> Cc: freebsd-fs@freebsd.org Subject: Re: panic: ffx_valloc: dup alloc + SU+J + fsck Message-ID: <20110301230325.GX78089@deviant.kiev.zoral.com.ua> In-Reply-To: <4D6D5F15.4080009@gmx.com> References: <4D6D5F15.4080009@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110301230325.GX78089>