From owner-freebsd-fs@FreeBSD.ORG Mon Jan 30 08:10:12 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFD7B106564A for ; Mon, 30 Jan 2012 08:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 944478FC18 for ; Mon, 30 Jan 2012 08:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0U8AC2T033654 for ; Mon, 30 Jan 2012 08:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0U8ACGj033653; Mon, 30 Jan 2012 08:10:12 GMT (envelope-from gnats) Date: Mon, 30 Jan 2012 08:10:12 GMT Message-Id: <201201300810.q0U8ACGj033653@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: "Eugene M. Zheganin" Cc: Subject: Re: kern/164472: [ufs] fsck -B panics on particular data inconsistency X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Eugene M. Zheganin" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2012 08:10:12 -0000 The following reply was made to PR kern/164472; it has been noted by GNATS. From: "Eugene M. Zheganin" To: bug-followup@FreeBSD.org, eugene@zhegan.in Cc: Subject: Re: kern/164472: [ufs] fsck -B panics on particular data inconsistency Date: Mon, 30 Jan 2012 13:50:35 +0600 This state can be achieved (and sometimes is achieved) after a server hangup and/or reset. I cannot agree that using fsck -B should lead to panic, because there is no way to distinguish filesystem between the state where it can be cured with fsck -B and where it can not. After all, this is what the bgfsck is for.