Date: Wed, 6 Jun 2012 08:24:12 +0200 From: Yamagi Burmeister <lists@yamagi.org> To: jjuanino@gmail.com Cc: freebsd-fs@freebsd.org, ronald-freebsd8@klop.yi.org Subject: Re: "panic: snapblkfree: inconsistent block type" on FreeBSD 9.0 RELEASE Message-ID: <20120606082412.bd21757e.lists@yamagi.org> In-Reply-To: <20120605203718.GA2630@banach> References: <CAAVO5%2BLzKnmh%2BHxaPs1PA1bA4%2BbcbijnHakW6xF72%2BJ_tGhx-A@mail.gmail.com> <CAAVO5%2BKaf348CVeP1uzfKMJ0cS34SzkXyzt1-hXRY_earV_b-A@mail.gmail.com> <op.wfdnzktr8527sy@ronaldradial.versatec.local> <20120605203718.GA2630@banach>
next in thread | previous in thread | raw e-mail | index | archive | help
--Signature=_Wed__6_Jun_2012_08_24_12_+0200_2Uf/RJ5bsCQxVA3+ Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello :) On Tue, 5 Jun 2012 22:37:21 +0200 Jose Garcia Juanino <jjuanino@gmail.com> wrote: > > > 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=3D0xfffffe0002deb000, > > > devvp=3DVariable "devvp" is not available. > > > ) > > > at /usr/src/sys/ufs/ffs/ffs_snapshot.c:1799 > > > > > > Regards > >=20 > > I don't know about the internals of FFS, but I know there were some fix= es =20 > > to FFS + snapshots ( + journal (SUJ) ??) after 9.0-RELEASE. So maybe yo= u =20 > > can test updating to and running with 9-STABLE. >=20 > Thanks for your reply. I cannot upgrade to 9-STABLE; it is a production > environment and only can run -RELEASE. In the other hand, I removed the > unclean snapshots (checked with fsck_ffs), but unfortunately did not > help and I got a new "snapblkfree: inconsistent block type" panic a few > hours later. At this moment, the overall of filesystems and snapshots > were clean (checked again with fsck). > > When the system started up again, I decided remove all the snapshots, > but while I am doing this work, the computer again raised a new panic: > "ffs_blkfree_cg: freeing free block". Related this panic, I found this > post on freebsd-current: >=20 > http://lists.freebsd.org/pipermail/freebsd-current/2011-October/028860.ht= ml >=20 > I am almost sure I have not hardware failures. Indeed, after that panic, > I definitively removed all the remaining snapshots, and did a new fsck on > the filesystems. The system now goes smoothly, and the computer does not > panic anymore. If you're using SU+J this is a known problem. In 9.0-RELEASE creating and removing snapshots on filesystems with SU+J has a high chance to lead to panics, filesystem corruption and several more not so nice things. While there were some commits in 9-STABLE in that area, snapshots are still not working with SU+J. They are disabled and an error messages is printed when you try to create one. --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB --Signature=_Wed__6_Jun_2012_08_24_12_+0200_2Uf/RJ5bsCQxVA3+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk/O95EACgkQWTjlg++8y8vMggCggO8vZlIzYD1v9tSoNUVmYa01 DhYAoLWMiRUVp2StlMc5D+buySNq+RSP =rEVV -----END PGP SIGNATURE----- --Signature=_Wed__6_Jun_2012_08_24_12_+0200_2Uf/RJ5bsCQxVA3+--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120606082412.bd21757e.lists>