On Jun 28, 2010, at 9:32 PM, Andrew Jones wrote: > Update: have given up on the zdb write mode repair effort, as least for now. > Hoping for any guidance / direction anyone's willing to offer... > > Re-running 'zpool import -F -f tank' with some stack trace debug, as > suggested in similar threads elsewhere. Note that this appears hung at near > idle.
It looks like it is processing huge inconsistent data set that was destroyed previously. So you need to wait a bit longer. regards victor > > > ffffff03e278c520 ffffff03e9c60038 ffffff03ef109490 1 60 ffffff0530db4680 > PC: _resume_from_idle+0xf1 CMD: zpool import -F -f tank > stack pointer for thread ffffff03e278c520: ffffff00182bbff0 > [ ffffff00182bbff0 _resume_from_idle+0xf1() ] > swtch+0x145() > cv_wait+0x61() > zio_wait+0x5d() > dbuf_read+0x1e8() > dnode_next_offset_level+0x129() > dnode_next_offset+0xa2() > get_next_chunk+0xa5() > dmu_free_long_range_impl+0x9e() > dmu_free_object+0xe6() > dsl_dataset_destroy+0x122() > dsl_destroy_inconsistent+0x5f() > findfunc+0x23() > dmu_objset_find_spa+0x38c() > dmu_objset_find_spa+0x153() > dmu_objset_find+0x40() > spa_load_impl+0xb23() > spa_load+0x117() > spa_load_best+0x78() > spa_import+0xee() > zfs_ioc_pool_import+0xc0() > zfsdev_ioctl+0x177() > cdev_ioctl+0x45() > spec_ioctl+0x5a() > fop_ioctl+0x7b() > ioctl+0x18e() > dtrace_systrace_syscall32+0x11a() > _sys_sysenter_post_swapgs+0x149() > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
