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:

Due to storage issue/slowness at boot, usually with multipath or 3rd party storage vendors, it's not rare that customers have to individually add x-systemd.device-timeout=XXX to all his entries in /etc/fstab, which is a real pain and prevents managing the systems easily.

I would hence love to have a DefaultDeviceTimeout property in /etc/systemd/system.conf and corresponding kernel command line parameter systemd.default_device_timeout (or similar, I'm not used to systemd parameters) that would enable to increase the delay waiting for devices.

For now, the only global property is DefaultTimeoutJobStartSec but it's definitely not suitable: we don't want to modify the behaviour for other components in the system.

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

All systemd releases, starting with RHEL7


How reproducible:

N/A

fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/305

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7727