zfs code - Sep 2008 - panic dirtying dbuf obj=3d199 lvl=1 blkid=1 but not tx_held

I''ve just experienced a panic with a shaky USB cable.

I have searched for bugs, but have not found a matching one which is not already
closed.

If anyone is interested, I could provide a crash dump.

Thanks, Nils

panic[cpu0]/thread=ffffff016a147c80:
dirtying dbuf obj=3d199 lvl=1 blkid=1 but not tx_held


ffffff00048194d0 zfs:dmu_tx_dirty_buf+2d6 ()
ffffff0004819570 zfs:dbuf_dirty+63 ()
ffffff00048195a0 zfs:dbuf_will_dirty+60 ()
ffffff0004819680 zfs:dnode_free_range+46b ()
ffffff0004819700 zfs:dnode_reallocate+160 ()
ffffff0004819790 zfs:dmu_object_reclaim+91 ()
ffffff0004819810 zfs:restore_object+12d ()
ffffff0004819970 zfs:dmu_recv_stream+71d ()
ffffff0004819c20 zfs:zfs_ioc_recv+28b ()
ffffff0004819ca0 zfs:zfsdev_ioctl+12e ()
ffffff0004819ce0 genunix:cdev_ioctl+48 ()
ffffff0004819d20 specfs:spec_ioctl+86 ()
ffffff0004819da0 genunix:fop_ioctl+7b ()
ffffff0004819eb0 genunix:ioctl+174 ()
ffffff0004819f00 unix:brand_sys_sysenter+2d7 ()

Has happened again after I replaced the faulty cable, seems to be reproducible 
with my zfs send/receive script.

Should I open a bug?

panic[cpu1]/thread=ffffff0167f4b200:
dirtying dbuf obj=3d199 lvl=1 blkid=1 but not tx_held


ffffff00050e94d0 zfs:dmu_tx_dirty_buf+2d6 ()
ffffff00050e9570 zfs:dbuf_dirty+63 ()
ffffff00050e95a0 zfs:dbuf_will_dirty+60 ()
ffffff00050e9680 zfs:dnode_free_range+46b ()
ffffff00050e9700 zfs:dnode_reallocate+160 ()
ffffff00050e9790 zfs:dmu_object_reclaim+91 ()
ffffff00050e9810 zfs:restore_object+12d ()
ffffff00050e9970 zfs:dmu_recv_stream+71d ()
ffffff00050e9c20 zfs:zfs_ioc_recv+28b ()
ffffff00050e9ca0 zfs:zfsdev_ioctl+12e ()
ffffff00050e9ce0 genunix:cdev_ioctl+48 ()
ffffff00050e9d20 specfs:spec_ioctl+86 ()
ffffff00050e9da0 genunix:fop_ioctl+7b ()
ffffff00050e9eb0 genunix:ioctl+174 ()
ffffff00050e9f00 unix:brand_sys_sysenter+2d7 ()

yes, please do, and include a crash dump.

--matt

Nils Goroll wrote:
> Has happened again after I replaced the faulty cable, seems to be
reproducible
> with my zfs send/receive script.
> 
> Should I open a bug?
> 
> panic[cpu1]/thread=ffffff0167f4b200:
> dirtying dbuf obj=3d199 lvl=1 blkid=1 but not tx_held
> 
> 
> ffffff00050e94d0 zfs:dmu_tx_dirty_buf+2d6 ()
> ffffff00050e9570 zfs:dbuf_dirty+63 ()
> ffffff00050e95a0 zfs:dbuf_will_dirty+60 ()
> ffffff00050e9680 zfs:dnode_free_range+46b ()
> ffffff00050e9700 zfs:dnode_reallocate+160 ()
> ffffff00050e9790 zfs:dmu_object_reclaim+91 ()
> ffffff00050e9810 zfs:restore_object+12d ()
> ffffff00050e9970 zfs:dmu_recv_stream+71d ()
> ffffff00050e9c20 zfs:zfs_ioc_recv+28b ()
> ffffff00050e9ca0 zfs:zfsdev_ioctl+12e ()
> ffffff00050e9ce0 genunix:cdev_ioctl+48 ()
> ffffff00050e9d20 specfs:spec_ioctl+86 ()
> ffffff00050e9da0 genunix:fop_ioctl+7b ()
> ffffff00050e9eb0 genunix:ioctl+174 ()
> ffffff00050e9f00 unix:brand_sys_sysenter+2d7 ()
> _______________________________________________
> zfs-code mailing list
> zfs-code at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-code

http://defect.opensolaris.org/bz/show_bug.cgi?id=3669

I have put the same information into the bugster queue, but it will usually take
a couple of days until the actual bug gets opened. I will update the bugzilla 
bug accordingly.

I will also upload the crash dumps.

Nils