Hi, on one of the machines of a dual with shared backend, I found this core two times during july/august: bash-4.2# mdb core.fmd.25911 Loading modules: [ fmd libumem.so.1 libc.so.1 libnvpair.so.1 libtopo.so.1 libuutil.so.1 libavl.so.1 libsysevent.so.1 eft.so ld.so.1 ] $C fda8e988 libc.so.1`_lwp_kill+0x15(3, 6, 22a2, fef58000, fef58000, b) fda8e9a8 libc.so.1`raise+0x2b(6, 0, fda8e9c0, feed83e9, 0, 0) fda8e9f8 libc.so.1`abort+0x10e(3a646d66, 4f424120, 203a5452, 75736e69, 63696666 , 746e6569) fda8ee18 fmd_panic(8080ec0, fda8ee44, 1, 0) fda8ee38 fmd_panic+0x12(8080ec0, c, 3e8, 584cefe4) fda8ee78 fmd_alloc+0x81(c, 1, c762b98, 0, 8842648, 8507b78) fda8eeb8 fmd_eventq_insert_at_head+0x43(887c720, 8d66800, 0, 165738c) fda8eed8 fmd_module_gc+0x66(8842640, 0, 0, fda8eef8) fda8ef18 fmd_modhash_apply+0x3e(8507b78, 8073d50, 0, 0, 56e5de52, 652aff) fda8ef48 fmd_gc+0x28(80998c0, 5, 584b51de, 652b04, 84fd688) fda8efa8 fmd_timerq_exec+0x127(84fd680, 0, feda1aa0, fef58000) fda8efc8 fmd_thread_start+0x5b(8263038, 0, 0, 0) fda8efe8 libc.so.1`_thrp_setup+0x88(feda1a40) fda8eff8 libc.so.1`_lwp_start(feda1a40, 0, 0, 0, 0, 0) This is the same machine where I find the infolog_hival growing forever and where fmd is unable to rotate the log, as stated previously. What's happening? This is not happening on the 1st machine. Gabriele Sonicle S.r.l. http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon
------------------------------------------ illumos-discuss Archives: https://illumos.topicbox.com/groups/discuss/discussions/T1677a1719312096c-M87847890987b027e4304975e Powered by Topicbox: https://topicbox.com
