From owner-freebsd-fs@FreeBSD.ORG Wed Nov 22 12:04:32 2006 Return-Path: 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 77AF216A494 for ; Wed, 22 Nov 2006 12:04:32 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E86E943D9A for ; Wed, 22 Nov 2006 12:00:55 +0000 (GMT) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Gmqn1-0008Sx-0O for freebsd-fs@freebsd.org; Wed, 22 Nov 2006 13:01:19 +0100 Received: from firewall.andxor.it ([195.223.2.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Nov 2006 13:01:18 +0100 Received: from lapo by firewall.andxor.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Nov 2006 13:01:18 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Lapo Luchini Date: Wed, 22 Nov 2006 13:01:03 +0100 Lines: 23 Message-ID: References: <854C78DB-2099-4DA5-9E3B-F30D6947C532@jlauser.net> <4512F957.2090205@centtech.com> <20060922041535.GF4842@deviant.kiev.zoral.com.ua> <455890AE.9050807@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: firewall.andxor.it User-Agent: Thunderbird 1.5.0.8 (X11/20061116) In-Reply-To: <455890AE.9050807@centtech.com> X-Enigmail-Version: 0.94.0.0 OpenPGP: Sender: news 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 12:04:32 -0000 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) Does "snapacct_ufs2: bad block" really mean "bad" as in "unreadable"? RTFS I tought it was just a "logic" inconsistency. Anyway, after having de-activated all snapshots for weeks (and deleted all the old ones) I got this panic again. I'm currently doing a "dd if=/dev/ad0 of=/dev/null bs=1m" as suggested by dd(1) in order to be sure it is not an hardwareissue. And if all is well I will "dd if=/dev/ad0 of=/dev/ad0 bs=1m" too. And then recompile with latest -STABLE just to be sure to have the latest amd64-based snapshot fixes. Hope this is the last time I see that panic... -_- Lapo