Hi Mike, we had a locking issue yesterday with iscsi_tcp (open-iscsi 2.0-869 from OFED-1.5.4) on Ethernet and a defective SSD on the target storage system at the same time.
The storage crashed, because the OS was on the SSD without replication and another server with the QEMU/KVM VMs running on that iSCSI target crashed, too. This is just a testing environment - therefore no replication and no InfiniBand. I've seen commit 52734d26ffca727da0e687963333ae88056ad84b from linux-stable and wanted to apply it to that 2.6.30-based open-iscsi kernel code. But when testing without the patch I can't trigger the panic again. I've already tried many parallel I/O and CPU intensive processes and then pulling out the Ethernet plug. Do you have an idea how to trigger this? I couldn't find anything in the list archives related to that commit. I've attached the screenshot of the panic. Cheers, Sebastian -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
<<attachment: iscsi_tcp server panic.png>>
