From owner-freebsd-fs@FreeBSD.ORG Mon Jan 30 05:40:13 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 85EC6106564A for ; Mon, 30 Jan 2012 05:40:13 +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 565508FC08 for ; Mon, 30 Jan 2012 05:40:13 +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 q0U5eD0h068368 for ; Mon, 30 Jan 2012 05:40:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0U5eDYi068367; Mon, 30 Jan 2012 05:40:13 GMT (envelope-from gnats) Date: Mon, 30 Jan 2012 05:40:13 GMT Message-Id: <201201300540.q0U5eDYi068367@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Kostik Belousov 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: Kostik Belousov List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2012 05:40:13 -0000 The following reply was made to PR kern/164472; it has been noted by GNATS. From: Kostik Belousov 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 07:30:04 +0200 You failed to mention which panic you got. Was it 'dup alloc' ? A backtace would be also useful. If it was indeed 'dup alloc', then there is nothing fsck or snapshots can be accused for. Your filesystem is in inconsistent state, which requires full fsck to recover. It must be not mounted while not repaired. Somewhat more interesting is how the fs got into this state.