Hi, [ Please Cc: me when replying, as I'm not subscribed to -stable@. ] My filer at home runs FreeBSD. A single data RAID-1 zpool with 10~15 datasets, two of them using compression. Over the night, I got the following panic: Tracing pid 0 tid 100111 td 0x86393a00 kdb_enter(809faa5b,809faa5b,80a12e84,cb114aec,0,...) at kdb_enter+0x3a panic(80a12e84,1c000,2e3e8000,80a12e7e,7d0,...) at panic+0x131 kmem_malloc(8169008c,1c000,2,cb114b6c,80909a99,...) at kmem_malloc+0x285 page_alloc(0,1c000,cb114b5f,2,2f0c800,...) at page_alloc+0x27 uma_large_malloc(1c000,2,0,8609b3f0,30,...) at uma_large_malloc+0x4a malloc(1c000,860b2120,2,cb114bb0,8601d36d,...) at malloc+0x7c zfs_kmem_alloc(1c000,2,cb114bf0,8601f77b,1c000,...) at zfs_kmem_alloc+0x20 zio_buf_alloc(1c000,cb114c30,86008817,92c33bd0,cb114bf0,...) at zio_buf_alloc+0x44 zio_compress_data(3,b4264000,20000,0,cb114c58,...) at zio_compress_data+0x8b zio_write_bp_init(92c339c0,92bba254,cb114c80,8071a322,cb114ca0,...) at zio_write_bp_init+0xff zio_execute(92c339c0,8638e0c0,cb114cd0,8071c5f4,92c33c14,...) at zio_execute+0xab taskq_run_safe(92c33c14,1,0,80a8429c,0,...) at taskq_run_safe+0x13 taskqueue_run(8638e0c0,8638e0d8,0,809ef596,0,...) at taskqueue_run+0x15d taskqueue_thread_loop(8638c3d0,cb114d38,8071c72a,0,cb114d20,...) at taskqueue_thread_loop+0xbd fork_exit(8071c72a,8638c3d0,cb114d38) at fork_exit+0x91 fork_trampoline() at fork_trampoline+0x8 I couldn't get a crash dump, sorry. However, I'm still using the same kernel so I can probably use addr2line(1) if you need it. Regards, -- Jeremie Le Hen Humans are born free and equal. But some are more equal than others. Coluche
on 15/12/2010 10:28 Jeremie Le Hen said the following:> Hi, > > [ Please Cc: me when replying, as I'm not subscribed to -stable@. ] > > My filer at home runs FreeBSD. A single data RAID-1 zpool with 10~15 > datasets, two of them using compression. Over the night, I got the > following panic:Thanks for the stack trace! But where is the promised panic message? :) I suspect that you ran out of kernel address space. You'd probably have to tune your system and/or add more memory. Please research this topic via mailing lists archives.> Tracing pid 0 tid 100111 td 0x86393a00 > kdb_enter(809faa5b,809faa5b,80a12e84,cb114aec,0,...) at kdb_enter+0x3a > panic(80a12e84,1c000,2e3e8000,80a12e7e,7d0,...) at panic+0x131 > kmem_malloc(8169008c,1c000,2,cb114b6c,80909a99,...) at kmem_malloc+0x285 > page_alloc(0,1c000,cb114b5f,2,2f0c800,...) at page_alloc+0x27 > uma_large_malloc(1c000,2,0,8609b3f0,30,...) at uma_large_malloc+0x4a > malloc(1c000,860b2120,2,cb114bb0,8601d36d,...) at malloc+0x7c > zfs_kmem_alloc(1c000,2,cb114bf0,8601f77b,1c000,...) at > zfs_kmem_alloc+0x20 > zio_buf_alloc(1c000,cb114c30,86008817,92c33bd0,cb114bf0,...) at > zio_buf_alloc+0x44 > zio_compress_data(3,b4264000,20000,0,cb114c58,...) at > zio_compress_data+0x8b > zio_write_bp_init(92c339c0,92bba254,cb114c80,8071a322,cb114ca0,...) at > zio_write_bp_init+0xff > zio_execute(92c339c0,8638e0c0,cb114cd0,8071c5f4,92c33c14,...) at > zio_execute+0xab > taskq_run_safe(92c33c14,1,0,80a8429c,0,...) at taskq_run_safe+0x13 > taskqueue_run(8638e0c0,8638e0d8,0,809ef596,0,...) at taskqueue_run+0x15d > taskqueue_thread_loop(8638c3d0,cb114d38,8071c72a,0,cb114d20,...) at > taskqueue_thread_loop+0xbd > fork_exit(8071c72a,8638c3d0,cb114d38) at fork_exit+0x91 > fork_trampoline() at fork_trampoline+0x8 > > I couldn't get a crash dump, sorry. However, I'm still using the same > kernel so I can probably use addr2line(1) if you need it.-- Andriy Gapon