Tomasz Chmielewski schrieb:
3) If IO errors appear on the initiator (thi seems important), reboot it
without logging out of the target:
# echo b >/proc/sysrq-trigger
4) Initiator will start booting and will connect to the target.
It won't be able to boot (hdparm loop still running on the target; some
data still in cache/dirty/writeback).
Interrupt the loop, if you have luck, tgtd _may_ segfault.
This is what gdb said:
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x6fc1d8c0 (LWP 22565)]
iscsi_tm_done (mreq=0x8120fd8) at ./list.h:74
74 __list_add(new, head->prev, head);
--
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
