search for: dmu_objset_find

...:zil_claim_log_block+60 () Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e650 zfs:zil_parse+181 () Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e690 zfs:zil_claim+ce () Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e840 zfs:dmu_objset_find+b6 () Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e9f0 zfs:dmu_objset_find+12f () Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047eba0 zfs:dmu_objset_find+12f () Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ec10 zfs:spa_loa...

...fffe80004a1700 zfs:zil_claim_log_block+60 () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a1800 zfs:zil_parse+181 () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a1840 zfs:zil_claim+d0 () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a19f0 zfs:dmu_objset_find+176 () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a1ba0 zfs:dmu_objset_find+10d () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a1c10 zfs:spa_load+5d4 () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a1c80 zfs:spa_load+32d () Nov 24 04:03:35...

...fffff00053c4660 genunix:avl_add+59 () Feb 8 16:07:09 amber genunix: [ID 655072 kern.notice] ffffff00053c46c0 zfs:find_ds_by_guid+b9 () Feb 8 16:07:09 amber genunix: [ID 655072 kern.notice] ffffff00053c46f0 zfs:findfunc+23 () Feb 8 16:07:09 amber genunix: [ID 655072 kern.notice] ffffff00053c47d0 zfs:dmu_objset_find_spa+38c () Feb 8 16:07:09 amber genunix: [ID 655072 kern.notice] ffffff00053c4810 zfs:dmu_objset_find+40 () Feb 8 16:07:09 amber genunix: [ID 655072 kern.notice] ffffff00053c4a70 zfs:dmu_recv_stream+448 () Feb 8 16:07:09 amber genunix: [ID 655072 kern.notice] ffffff00053c4c40 zfs:zfs_ioc_recv+41d (...

...0xb3() ffffff0008f2b320 dmu_tx_assign+0x4b() ffffff0008f2b3b0 dmu_free_long_range_impl+0x12b() ffffff0008f2b400 dmu_free_object+0xe6() ffffff0008f2b710 dsl_dataset_destroy+0x122() ffffff0008f2b740 dsl_destroy_inconsistent+0x5f() ffffff0008f2b770 findfunc+0x23() ffffff0008f2b850 dmu_objset_find_spa+0x38c() ffffff0008f2b930 dmu_objset_find_spa+0x153() ffffff0008f2b970 dmu_objset_find+0x40() ffffff0008f2ba40 spa_load_impl+0xb23() ffffff0008f2bad0 spa_load+0x117() ffffff0008f2bb50 spa_load_best+0x78() ffffff0008f2bbf0 spa_import+0xee() ffffff0008f2bc40 zfs_ioc_pool_impor...

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything