I had just upgraded (pkg image-update) to snv_98 then was trying to do
a build of ON. The build was happening inside of virtualbox, so I
can't really say for sure what layer is at fault. I'll keep the disk
image and crash dump around for a few days in case anyone is
interested in more data from them.
Here's the interesting bits from ::msgbuf
panic[cpu0]/thread=d48f6de0:
assertion failed: 0 == zap_add(dp->dp_meta_objset,
DMU_POOL_DIRECTORY_OBJECT, DMU_POOL_SCRUB_FUNC, sizeof (uint32_t), 1,
&dp->dp_scrub_func, tx), file: ../../common/fs/zfs/dsl_scrub.c, line:
124
d48f6c0c genunix:assfail+5a (feb96258, feb96238,)
d48f6c58 zfs:dsl_pool_scrub_setup_sync+2cc (d68e8b00, ea9dadb4,)
d48f6c90 zfs:dsl_sync_task_group_sync+da (df8ceac0, ee97d518)
d48f6cdc zfs:dsl_pool_sync+121 (d68e8b00, 610b, 0)
d48f6d4c zfs:spa_sync+2b5 (d3104500, 610b, 0)
d48f6dc8 zfs:txg_sync_thread+2aa (d68e8b00, 0)
d48f6dd8 unix:thread_start+8 ()
Here's what my pool looks like:
pool: export
id: 10328403348002192848
state: FAULTED
status: One or more devices contains corrupted data.
action: The pool cannot be imported due to damaged devices or data.
The pool may be active on another system, but can be imported using
the '-f' flag.
see: http://www.sun.com/msg/ZFS-8000-5E
config:
export FAULTED corrupted data
c6t0d0 UNAVAIL corrupted data
--
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
