Bug 1307035 - tgtd crash detected via abrtd
tgtd crash detected via abrtd
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: scsi-target-utils (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Andy Grover
Martin Hoyer
: TestBlocker
Depends On:
  Show dependency treegraph
Reported: 2016-02-12 09:20 EST by michal novacek
Modified: 2016-03-14 14:12 EDT (History)
6 users (show)

See Also:
Fixed In Version: scsi-target-utils-1.0.24-18.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-03-14 14:12:54 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
sosreport from abrtd (733.89 KB, text/plain)
2016-02-12 09:22 EST, michal novacek
no flags Details

  None (edit)
Description michal novacek 2016-02-12 09:20:12 EST
Description of problem:
tgtd daemon crasheshes from time to time. We are having workaround for that
which starts it again once it is detected but it sometimes times out after

We use tgtd to serve as a target host of about 300 hundreds of lvs from remotely
connected disk array on a machine that has 250GB of ram.

Version-Release number of selected component (if applicable):

How reproducible: randomly about once in a three weeks

Steps to Reproduce:
1. tgtd crashes in normal operation and takes much longer to start then (sometimes over two minutes)

Actual results: random crashes from time to time, longer start time than before 6.7

Expected results: no random crashes, short start time
Comment 2 michal novacek 2016-02-12 09:22 EST
Created attachment 1123512 [details]
sosreport from abrtd
Comment 3 Chris Leech 2016-02-12 13:03:13 EST
# from the sosreport
segfault at 1e4fdc0 ip 0000000000409bb0 sp 00007ffdbdae3fc0 error 4 in tgtd[400000+3e000]

# addr2line -e `which tgtd` 409bb0

which is a list_for_each_entry_safe loop in iscsi_target_destroy()

Note You need to log in before you can comment on or make changes to this bug.