Date: Wed, 22 Nov 2006 13:01:03 +0100 From: Lapo Luchini <lapo@lapo.it> To: freebsd-fs@freebsd.org Subject: Re: Snapshot corruption on 6.1/amd64 Message-ID: <ek1e60$a5r$1@sea.gmane.org> In-Reply-To: <455890AE.9050807@centtech.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ek1e60$a5r$1>