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