Snapshot corruption on 6.1/amd64
Kris Kennaway
kris at obsecurity.org
Wed Nov 22 17:12:13 UTC 2006
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)
>
> 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... -_-
I've lost context, how are you reproducing the panic?
Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20061122/a870e9df/attachment.pgp
More information about the freebsd-fs
mailing list