> I think we're quite narrowed this to be stgt's fault, we'll see... OK, I have managed to narrow it to the following commit commit 36078d43e3fdccb0ffd4a28d5ef4d9d14d50a9e0 Author: Alexander Nezhinsky <nezhinsky at gmail.com> Date: Sun Sep 28 12:38:35 2008 +0300 iscsi: improve iser scheduling When running resetting stgt's git to the commit which precedes it commit 0c2d06e1f66acf15cf53b234c14571af49c809d3 Author: Tomasz Chmielewski <mangoo at wpkg.org> Date: Fri Sep 26 11:32:13 2008 +0200 tgt-admin: document device-type usage in targets.conf.example things seem to work fine and when resetting to the iser scheduling patch I see the corruption. Many thanks for pointing this out, we'll try to come with a quick fix. Or. BTW, I think there's some low chance that the bug is not in the commit itself but rather some rare problem (of the scsi response somehow crossing the rdma-write) which is exposed by the commit - so if you have the patch I was asking on, please send it. -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html |