Bug 607869

Summary: IO is stuck due to active device that moved to suspend mode and never resumed
Product: Red Hat Enterprise Linux 6 Reporter: Ben Marzinski <bmarzins>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED CURRENTRELEASE QA Contact: Barry Donahue <bdonahue>
Severity: high Docs Contact:
Priority: high    
Version: 6.0CC: abaron, agk, bmarzins, bmr, christophe.varoqui, cpelland, dwysocha, egoggin, heinzm, iheim, junichi.nomura, kueda, lmb, mbroz, mgoldboi, prajnoha, prockai, tranlan, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: device-mapper-multipath-0.4.9-23.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 584742 Environment:
Last Closed: 2010-11-10 20:11:29 UTC Type: ---
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: 584742    
Bug Blocks:    

Comment 1 Ben Marzinski 2010-06-25 04:02:34 UTC
This bug exists on RHEL6 as well. I already have a patch to fix it.

Comment 2 RHEL Program Management 2010-06-25 04:02:53 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Ben Marzinski 2010-06-28 22:42:29 UTC
multipath now uses the resize code that doesn't set noflush for reloads because of changed size.

Comment 4 Ben Marzinski 2010-06-28 23:09:10 UTC
You can pick up packages with this fix at http://people.redhat.com/bmarzins/device-mapper-multipath/rpms/RHEL6/

Comment 6 Barry Donahue 2010-09-13 18:18:34 UTC
Verified on snap-13 on storageqe-04. Upgraded a LUN from 30GB to 40GB.

Comment 7 releng-rhel@redhat.com 2010-11-10 20:11:29 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.