Date: Sun, 29 Oct 2017 13:17:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 223238] Persistent iscsi underflow mismatch errors followed by apparent kernel panic Message-ID: <bug-223238-5312-MBikoIauRW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223238-5312@https.bugs.freebsd.org/bugzilla/> References: <bug-223238-5312@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223238 --- Comment #6 from Edward Tomasz Napierala <trasz@FreeBSD.org> --- The warnings on the initiator (FreeBSD) side mean that the NAS doesn't correctly mark underflows. It's a common bug and not something to worry ab= out (though still a protocol error). The "Unsupported SCSI Opcode 0xb7" messages on the target (Synology) side m= ean it doesn't support READ DEFECT DATA command. That's ok too, and shouldn't break anything. I'm not sure what makes FreeBSD send the READ DEFECT DATA command to the target. Do you have some disk monitoring software enabled on the initiator side? As for the panic message - looking at the traceback it looks like panic in mpt(4) driver, unrelated to iscsi(4). It might be triggered by the same software that triggers the READ DEFECT DATA on iSCSI. Can you check which process triggered the panic? Basically, when you see the backtrace and pan= ic messages, press Scroll Lock and use cursor keys to scroll up; there should = be some more information there. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223238-5312-MBikoIauRW>