Bug 1447328

Summary: Core was generated by `mpathpersist -o -G -S 1AA00C5202 /dev/mapper/mpathf'
Product: Red Hat Enterprise Linux 6 Reporter: Achilles Gaikwad <agaikwad>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Lin Li <lilin>
Severity: low Docs Contact:
Priority: high    
Version: 6.8CC: agaikwad, agk, bmarzins, heinzm, jbrassow, jmagrini, jreznik, lilin, mkolaja, msnitzer, mthacker, nkshirsa, prajnoha, rbalakri, toneata, zkabelac
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: device-mapper-multipath-0.4.9-101.el6 Doc Type: Bug Fix
Doc Text:
Prior to this update, the mpathpersist utility sometimes attempted to wait on threads that it did not create. As a consequence, mpathpersist terminated unexpectedly if there was a registration conflict on one of the paths. With this update, mpathpersist now waits only for threads that it creates. As a result, mpathpersist no longer crashes in this situation.
 Story Points: ---
Clone Of:
: 1448562 1497059 1497083 (view as bug list) Environment:
Last Closed: 2018-06-19 05:17:52 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:    
Bug Blocks: 1448562, 1497059, 1497083    
Attachments:
Description Flags
new core none

Comment 16 nikhil kshirsagar 2017-05-11 04:24:34 UTC 
Created attachment 1277742 [details]
new core
Comment 24 Ben Marzinski 2017-09-27 18:33:47 UTC 
I've made a build with my fix from Comment 18
Comment 26 Oneata Mircea Teodor 2017-09-29 07:19:27 UTC 
This bug has been copied as 6.9 z-stream (EUS) bug #1497083 and now must be
resolved in the current update release, set blocker flag.
Comment 27 Oneata Mircea Teodor 2017-09-29 07:29:14 UTC 
Investigating an issue, I cannot clone for rhel 6.8z.
Comment 35 errata-xmlrpc 2018-06-19 05:17:52 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-2018:1893