[EMAIL PROTECTED] wrote on 19/07/2007 11:19:03 PM: > Could you try using the 'mdb' debugger command on the core file, > and enter commands "::status" and "::stack" (or $c), > and post the result to this forum. > This will give us all an idea of where the problem lies.
Two new ones although I suspect both == bug id 6558751. tachikoma:~# mdb iscsitgtd.core.20070720 Loading modules: [ libumem.so.1 libavl.so.1 libc.so.1 libnvpair.so.1 libuutil.so.1 ld.so.1 ] > ::stack libc.so.1`_lwp_kill+0xa() libc.so.1`raise+0x19() libc.so.1`abort+0xd1() libc.so.1`_assert+0x74() t10_cmd_state_machine+0x407() t10_cmd_shoot_event+0x5d() sess_process+0x46c() libc.so.1`_thr_setup+0x67() libc.so.1`_lwp_start() > ::status debugging core file of iscsitgtd (64-bit) from tachikoma file: /usr/sbin/amd64/iscsitgtd initial argv: /usr/sbin/iscsitgtd threading model: native threads status: process terminated by SIGABRT (Abort) panic message: Assertion failed: 0, file ../t10_sam.c, line 523 and tachikoma:~# mdb iscsitgtd.core.20070719 Loading modules: [ libumem.so.1 libavl.so.1 libc.so.1 libnvpair.so.1 libuutil.so.1 ld.so.1 ] > ::stack libc.so.1`_lwp_kill+0xa() libc.so.1`raise+0x19() libc.so.1`abort+0xd1() libc.so.1`_assert+0x74() t10_cmd_state_machine+0x15b() t10_handle_destroy+0xd1() sess_from_t10+0xad() libc.so.1`_thr_setup+0x67() libc.so.1`_lwp_start() > ::status debugging core file of iscsitgtd (64-bit) from tachikoma file: /usr/sbin/amd64/iscsitgtd initial argv: /usr/sbin/iscsitgtd threading model: native threads status: process terminated by SIGABRT (Abort) panic message: Assertion failed: 0, file ../t10_sam.c, line 634 > This email, including any attachments, is intended only for the use of the individual or entity named above and may contain information that is confidential and privileged. Any information contained in this email is not to be used or disclosed for any purpose other than the purpose for which you received it. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email by mistake, please delete this email permanently from your system. WARNING: Although Editure has taken reasonable precautions to ensure no viruses are present in this email, Editure can not accept responsibility for any losses or damages whatsoever, arising from the use of this email and/or its attachments. www.editure.com _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
