From owner-freebsd-bugs@freebsd.org Thu Jun 8 16:48:42 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9ECC2C0A1F7 for ; Thu, 8 Jun 2017 16:48:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D2BC64574 for ; Thu, 8 Jun 2017 16:48:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v58Gmg2p044216 for ; Thu, 8 Jun 2017 16:48:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219866] [iscsi] ctld crashes inside ctl_datamove() Date: Thu, 08 Jun 2017 16:48:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emz@norma.perm.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2017 16:48:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219866 Bug ID: 219866 Summary: [iscsi] ctld crashes inside ctl_datamove() Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: emz@norma.perm.ru System info =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D FreeBSD san01.bsh-ru.playkey.net 11.0-RELEASE-p7 FreeBSD 11.0-RELEASE-p7 #2 r314026M: Wed Mar 29 06:54:29 UTC 2017=20=20=20=20 emz@san01.bsh-ru.playkey.net:/usr/obj/usr/src/sys/SAN amd64 I have a bunch of FreeBSD's that run ctld and are used as iSCSI target. One= of the started to crash periodically after the load was increased twice. "M" in the uname stands for the patchs that trasz@FreeBSD.org gave me (and it fixes some other issue, and isn't probably related to this one, because the system was running just fine with it for several months until the load has increas= ed) and also for increasing the target limit beyond 512. I have a bunch of crashdumps from this system indicating that the crash hap= pens inside the ctl_datamove() call. This system also complains in dmesg pretty often about [...] ctl_datamove: tag 0x293a4d on (23:34:0) aborted ctl_datamove: tag 0x293a4e on (23:34:0) aborted ctl_datamove: tag 0x1fe2d9 on (7:34:0) aborted ctl_datamove: tag 0x293a50 on (23:34:0) aborted ctl_datamove: tag 0x21e6cd on (15:34:0) aborted ctl_datamove: tag 0x21e6ce on (15:34:0) aborted ctl_datamove: tag 0xe453b on (10:34:0) aborted ctl_datamove: tag 0x21e6cf on (15:34:0) aborted ctl_datamove: tag 0x61c355 on (9:34:0) aborted ctl_datamove: tag 0x10cf20 on (2:34:0) aborted ctl_datamove: tag 0xe453d on (10:34:0) aborted ctl_datamove: tag 0x174e97 on (28:34:0) aborted [...] Don't know if it's related, so I decided to mention it. Since the size of these crashdumps is enormous (several gigabytes each), I'= ve put them on the web-server (not the one hosted on the affected system). They can be found here (autoindexed location): http://files2.enaza.ru/freeb= sd/ --=20 You are receiving this mail because: You are the assignee for the bug.=