Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Jan 2012 05:40:13 GMT
From:      Kostik Belousov <kostikbel@gmail.com>
To:        freebsd-fs@FreeBSD.org
Subject:   Re: kern/164472: [ufs] fsck -B panics on particular data inconsistency
Message-ID:  <201201300540.q0U5eDYi068367@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/164472; it has been noted by GNATS.

From: Kostik Belousov <kostikbel@gmail.com>
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201300540.q0U5eDYi068367>