[Bug 219866] [iscsi] ctld crashes inside ctl_datamove()
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Jun 8 16:48:42 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219866
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 at FreeBSD.org
Reporter: emz at norma.perm.ru
System info
===========
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
emz at 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 at 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 increased)
and also for increasing the target limit beyond 512.
I have a bunch of crashdumps from this system indicating that the crash happens
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/freebsd/
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list