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.

+++ This bug was initially created as a clone of Bug #910831 +++

Description of problem:
Write in the configuration file a path that don't exist:

<target iqn.2010-12.org.trasno:iscsi.lvm>
backing-store /dev/trasno/windows
backing-store /path/not/exist
</target>

First path exist, and the second one don't exist.  If you start tgtd 
with this configuration it will start correctly without giving a single warning.  Neither it writes anything in /var/log/messages

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


How reproducible:

Allways.


Steps to Reproduce:
1. Create a config file like the one showed, with one existing path and another that don't exist.
2.
3.
  
Actual results:

tgtd is launched without any error/warning, and the backing store that don't exist just don't show up.

Expected results:
At least give a warning somewhere saying that the device don't exist.  Notice that if the file exist, but tgtd is not able to access to it, it already gives an error on /var/log/messages:

Feb 13 17:23:31 trasno tgtd[27313]: tgtd: backed_file_open(92) Could not open /mnt/images/iscsi/f14_64.img, Permission denied



Additional info:

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/