A few weeks ago, I wrote: > Yesterday I tried to clone a xen dom0 zfs root > filesystem and hit this panic (probably Bug ID 6580715): > > > > ::status > debugging crash dump vmcore.6 (64-bit) from moritz > operating system: 5.11 wos_b73 (i86pc) > panic message: freeing free segment (vdev=0 offset=11c14df000 size=1000) > dump content: kernel pages only > > > $c > vpanic() > vcmn_err+0x28(3, fffffffff812d818, ffffff0004850798) > zfs_panic_recover+0xb6() > metaslab_free_dva+0x1a2(ffffff01487ec580, ffffff0162231b20, 20b236c, 0) > metaslab_free+0x97(ffffff01487ec580, ffffff0162231b20, 20b236c, 0) > zio_free_blk+0x4c(ffffff01487ec580, ffffff0162231b20, 20b236c) > zil_sync+0x334(ffffff015b7d94c0, ffffff015689d180) > dmu_objset_sync+0x18e(ffffff014ff39c40, ffffff017c500d58, ffffff015689d180) > dsl_dataset_sync+0x5d(ffffff01571efa00, ffffff017c500d58, ffffff015689d180) > dsl_pool_sync+0xb5(ffffff014f4ace00, 20b236c) > spa_sync+0x1c5(ffffff01487ec580, 20b236c) > txg_sync_thread+0x19a(ffffff014f4ace00) > thread_start+8()
Btw, a few weeks later I got more strange panics on this machine, in the procfs filesystem module, which I finally traced as a single defective bit in a ddr2 ram module (verified by memtest86). So, I guess it's possible that the above zfs panic happened due to the defective ram module. This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
