Bug 1723746

Summary: Booting with a large number of multipath devices drops into emergency shell [rhel-8.0.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: Oneata Mircea Teodor <toneata>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Lin Li <lilin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: agk, bmarson, bmarzins, heinzm, jbrassow, lilin, msnitzer, prajnoha, rhandlin, rpeterso, toneata, ttracy, zkabelac
Target Milestone: rcKeywords: ZStream
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: device-mapper-multipath-0.7.8-7.1 Doc Type: Bug Fix
Doc Text:
Cause: When multipath is determining whether it should claim a block device as a path device in udev, it checks if multipathd is running by openning a socket connection to it. If multipathd hasn't started up yet adn there are a large number of block devics, this can hang, causing udev to hang as well. Consequence: udev processing for block devices can be delayed on bootup, possibly causing the bootup to fail to the emergency shell. Fix: multipath now tries to connect to the multipathd socket in a nonblocking manner. If that fails, it looks at the error to determine if multipathd will be starting up. Result: multipath no longer causes udev processing of block devices to hang in setups with a large number of block devices.
Story Points: ---
Clone Of: 1700451 Environment:
Last Closed: 2019-07-29 08:28:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1700451    
Bug Blocks:    

Comment 7 errata-xmlrpc 2019-07-29 08:28:25 UTC
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, 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-2019:1872