Date: Wed, 08 Feb 2017 08:42:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 216906] [iSCSI] Bad CRC may not be correctly handled Message-ID: <bug-216906-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216906 Bug ID: 216906 Summary: [iSCSI] Bad CRC may not be correctly handled Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ben.rubson@gmail.com Hello, Adding hardware CRC32C support to FreeBSD (#216467), we found that iSCSI CRC errors may not be correctly handled. When one of the patch #216467 versions generated bad CRC, here is how the i= SCSI test disk behaved : disk connected successfully (here the CRC were certainly right), but as soo= n as there were some trafic, disk hung, and it was not possible to recover it, reboot needed. >From /var/log/messages : kernel: WARNING: 192.168.2.1 (iqn.2012-06.srv1:rT1): no ping reply (NOP-In) after 5 seconds; reconnecting srv1 last message repeated 31 times srv1 last message repeated 42 times No digest failed message. Should we try to reproduce / investigate on this ? Many thanks ! Ben --=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-216906-8>