Hello, I have a FreeBSD 10.2 server running as iSCSI target. Another FreeBSD 10.2 is an initiator and has several targets used. When I add a target and reload its config with 'service ctld reload', the FreeBSD initiator server panics. It's reproducable (I have a coredump, but I think it's clear what the problem is) How can I have the target reloads it config, without all initiators crashing? Right before the crash the iscsi session drops and reinits Regards, Frank de Bot Related dmesg from the initiator: Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): WRITE(10). CDB: 2a 00 00 29 93 c0 00 00 08 00 Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): CAM status: SCSI Status Error Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): SCSI status: Check Condition Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): SCSI sense: UNIT ATTENTION asc:3f,e (Reported LUNs data has changed) Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): Retrying command (per sense data) Oct 14 20:59:49 host004 kernel: da0 at iscsi1 bus 0 scbus7 target 0 lun 0 Oct 14 20:59:49 host004 kernel: da0: <FREEBSD CTLDISK 0001> s/n MYSERIAL 2 detached Oct 14 20:59:49 host004 kernel: (da0:iscsi1:0:0:0): Periph destroyed Oct 14 20:59:49 host004 kernel: da0 at iscsi1 bus 0 scbus7 target 0 lun 0 Oct 14 20:59:49 host004 kernel: da0: <FREEBSD CTLDISK 0001> Fixed Direct Access SPC-4 SCSI device Oct 14 20:59:49 host004 kernel: da0: Serial Number MYSERIAL 2 Oct 14 20:59:49 host004 kernel: da0: 150.000MB/s transfers Oct 14 20:59:49 host004 kernel: da0: Command Queueing enabled Oct 14 20:59:49 host004 kernel: da0: 20480MB (5242880 4096 byte sectors: 255H 63S/T 326C)
Edward Tomasz Napierała
2015-Oct-15 11:34 UTC
Reloading iscsi target, iscsi initiator panics
On 1014T2316, Frank de Bot (lists) wrote:> Hello, > > I have a FreeBSD 10.2 server running as iSCSI target. Another FreeBSD > 10.2 is an initiator and has several targets used. > > When I add a target and reload its config with 'service ctld reload', > the FreeBSD initiator server panics. It's reproducable (I have a > coredump, but I think it's clear what the problem is)How easy it is to reproduce, eg. does it happen about every time? Could you paste the backtrace?