From owner-freebsd-fs@FreeBSD.ORG  Wed Nov 22 17:12:13 2006
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
X-Original-To: freebsd-fs@freebsd.org
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 AFEA716A403
	for <freebsd-fs@freebsd.org>; Wed, 22 Nov 2006 17:12:13 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E41C043E28
	for <freebsd-fs@freebsd.org>; Wed, 22 Nov 2006 17:08:58 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196])
	by elvis.mu.org (Postfix) with ESMTP id 679731A3C1E;
	Wed, 22 Nov 2006 09:09:28 -0800 (PST)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id B110C5126C; Wed, 22 Nov 2006 12:09:13 -0500 (EST)
Date: Wed, 22 Nov 2006 12:09:13 -0500
From: Kris Kennaway <kris@obsecurity.org>
To: Lapo Luchini <lapo@lapo.it>
Message-ID: <20061122170913.GA38255@xor.obsecurity.org>
References: <854C78DB-2099-4DA5-9E3B-F30D6947C532@jlauser.net>
	<4512F957.2090205@centtech.com>
	<20060922041535.GF4842@deviant.kiev.zoral.com.ua>
	<loom.20061113T154045-932@post.gmane.org>
	<455890AE.9050807@centtech.com> <ek1e60$a5r$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND"
Content-Disposition: inline
In-Reply-To: <ek1e60$a5r$1@sea.gmane.org>
User-Agent: Mutt/1.4.2.2i
Cc: freebsd-fs@freebsd.org
Subject: Re: Snapshot corruption on 6.1/amd64
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2006 17:12:13 -0000


--d6Gm4EdcadzBjdND
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 22, 2006 at 01:01:03PM +0100, Lapo Luchini wrote:
> Eric Anderson wrote:
> >>   Panic String: snapacct_ufs2: bad block
> >> I have the dump file, for the latest problem.
> > Maybe you have a bad disk?  You might try swapping the drive out. (just
> > a wild guess here)
>=20
> Does "snapacct_ufs2: bad block" really mean "bad" as in "unreadable"?
> RTFS I tought it was just a "logic" inconsistency.
>=20
> Anyway, after having de-activated all snapshots for weeks (and deleted
> all the old ones) I got this panic again.
>=20
> I'm currently doing a "dd if=3D/dev/ad0 of=3D/dev/null bs=3D1m" as sugges=
ted
> by dd(1) in order to be sure it is not an hardwareissue.
>=20
> And if all is well I will "dd if=3D/dev/ad0 of=3D/dev/ad0 bs=3D1m" too.
>=20
> And then recompile with latest -STABLE just to be sure to have the
> latest amd64-based snapshot fixes.
>=20
> Hope this is the last time I see that panic... -_-

I've lost context, how are you reproducing the panic?

Kris

--d6Gm4EdcadzBjdND
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFZIQ5Wry0BWjoQKURAuzPAKDb5arS5uVct5eHUfMgp8mbsgScfwCeOM9I
1sew/C9nM3fzUZ07EYQ6lkM=
=n0F5
-----END PGP SIGNATURE-----

--d6Gm4EdcadzBjdND--