From owner-freebsd-fs@FreeBSD.ORG Mon Jun 4 12:08:02 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B858106566B for ; Mon, 4 Jun 2012 12:08:02 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id E44878FC1C for ; Mon, 4 Jun 2012 12:08:01 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1SbW4l-0003lQ-VP for freebsd-fs@freebsd.org; Mon, 04 Jun 2012 14:08:00 +0200 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1SbW4l-00055u-Sr for freebsd-fs@freebsd.org; Mon, 04 Jun 2012 14:07:59 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-fs@freebsd.org References: Date: Mon, 04 Jun 2012 14:07:58 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/11.64 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.0 X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_50 autolearn=disabled version=3.2.5 X-Scan-Signature: 76f3589a93270604ea078d468a2051b3 Subject: Re: "panic: snapblkfree: inconsistent block type" on FreeBSD 9.0 RELEASE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 12:08:02 -0000 On Sun, 03 Jun 2012 20:08:07 +0200, José García Juanino wrote: > On 3 June 2012 14:16, José García Juanino wrote: >> Hi, >> >> I am getting a lot of "snapblkfree: inconsistent block type" panics on >> my FreeBSD 9.0-RELEASE. My file systems have not any inconsistencies, >> I am checked them with fsck. But I have some snapshots with softupdate >> inconsistencies (fsck_ffs /path/to/snapshot), and I suspect that may >> be the cause of the panics. I have several questions: >> >> 1- Snapshots with fsck inconsistencies might be the cause of my panics? >> 2- Should I remove any of such "corrupt" snapshots? >> >> If someone is interested, I can provide a full backtrace. Kernel is >> GENERIC, with no tweaks. File system are been created with normal >> "newfs -U". No special setting is using. > > I have three full core dumps: > > http://www.mipaginapersonal.movistar.es/web3/jjuanino/core.txt.1 > http://www.mipaginapersonal.movistar.es/web3/jjuanino/core.txt.2 > http://www.mipaginapersonal.movistar.es/web3/jjuanino/core.txt.3 > > The relevant code is, in the three examples: > > #3 0xffffffff80a40124 in ffs_snapblkfree (fs=0xfffffe0002deb000, > devvp=Variable "devvp" is not available. > ) > at /usr/src/sys/ufs/ffs/ffs_snapshot.c:1799 > > Regards I don't know about the internals of FFS, but I know there were some fixes to FFS + snapshots ( + journal (SUJ) ??) after 9.0-RELEASE. So maybe you can test updating to and running with 9-STABLE. Ronald.