Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
120s.
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):
scsi-target-utils-1.0.24-16.el6.x86_64
2.6.32-573.8.1.el6.x86_64
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
# from the sosreport
segfault at 1e4fdc0 ip 0000000000409bb0 sp 00007ffdbdae3fc0 error 4 in tgtd[400000+3e000]
# addr2line -e `which tgtd` 409bb0
/usr/src/debug/fujita-tgt-e039354/usr/iscsi/target.c:410
which is a list_for_each_entry_safe loop in iscsi_target_destroy()