FUJITA Tomonori schrieb:
TMF (an initiator tries to abort a request due to timeout) might be related with your problem. I'll dig into it this weekend.
Here is how you can reproduce it reliably. You need to have LVM on your target. On the initiator, do: dd if=/dev/iscsi/disk of=/dev/null On the target, do: dmsetup suspend /dev/mapper/logical-volume This will block any I/O to userspace accessing that logical volume. Wait until you see in logs: Dec 16 13:54:51 megathecus tgtd: abort_task_set(988) found 60000a07 0 Dec 16 13:54:52 megathecus tgtd: conn_close(88) connection closed 0x807dc5c 4 Dec 16 13:54:55 megathecus tgtd: conn_close(88) connection closed 0x807dc5c 3 Dec 16 13:55:13 megathecus tgtd: conn_close(88) connection closed 0x807dc5c 2 Dec 16 13:55:31 megathecus tgtd: conn_close(88) connection closed 0x807dc5c 1 Then, make the volume accessible again: dmsetup resume /dev/mapper/megathecus-backup2 Which will result in: Dec 16 13:55:32 megathecus kernel: tgtd[4872]: segfault at 00000220 eip 0804f0b5 esp 77c43ff0 error 4 -- Tomasz Chmielewski http://wpkg.org -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
