Tomasz Chmielewski schrieb: >> This is how the kernel log looks on the target - everything happened >> in one second >> (SATA timeout, hard reset, tgtd segfault) - is it a known issue? I use >> tgt-0.9.5. > > Here is the syslog with tgtd entries - it "noticed" something's wrong 13 > seconds before the kernel did? > Apr 7 04:02:54 san3 kernel: [153755.829415] ata1: hard resetting link > Apr 7 04:02:54 san3 tgtd: abort_task_set(988) found 10000a01 0 > Apr 7 04:02:54 san3 kernel: [153756.312026] ata1: SATA link up 1.5 Gbps > (SStatus 113 SControl 300) > Apr 7 04:02:54 san3 kernel: [153756.386453] ata1.00: configured for > UDMA/133 > Apr 7 04:02:54 san3 kernel: [153756.386548] ata1: EH complete > Apr 7 04:02:54 san3 kernel: [153756.386733] sd 1:0:0:0: [sdb] > 2930277168 512-byte hardware sectors (1500302 MB) > Apr 7 04:02:54 san3 kernel: [153756.386841] sd 1:0:0:0: [sdb] Write > Protect is off > Apr 7 04:02:54 san3 kernel: [153756.386889] sd 1:0:0:0: [sdb] Mode > Sense: 00 3a 00 00 > Apr 7 04:02:54 san3 kernel: [153756.386961] sd 1:0:0:0: [sdb] Write > cache: disabled, read cache: enabled, doesn't support DPO or FUA > Apr 7 04:02:54 san3 kernel: [153756.406006] tgtd[20545]: segfault at 31 > ip 40c32d sp 75df00c0 error 4 in tgtd[400000+25000] > Apr 7 04:02:55 san3 tgtd: conn_close(100) connection closed, 0x257df38 2 > Apr 7 04:02:55 san3 tgtd: conn_close(106) sesson 0x25906c0 1 To reproduce: 1. On the initiator, start to write (i.e. with dd) 2. On the target, use hdparm -Y to temporarily disable the drive: i=1 while [ $i -ne 100 ] ; do hdparm -Y /dev/sdd i=$((i+1)) done tgtd will segfault after one or two minutes. -- Tomasz Chmielewski http://wpkg.org -- 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 |