Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1448970 - pvresize hangs, seemingly due to changes made by multipathd 'resize map' failure
pvresize hangs, seemingly due to changes made by multipathd 'resize map' failure
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-multipath (Show other bugs)
7.4
x86_64 Linux
unspecified Severity high
: rc
: ---
Assigned To: Ben Marzinski
Lin Li
:
Depends On: 1444193
Blocks: 1469559
  Show dependency treegraph
 
Reported: 2017-05-08 18:48 EDT by Ben Marzinski
Modified: 2018-04-10 12:10 EDT (History)
9 users (show)

See Also:
Fixed In Version: device-mapper-multipath-0.4.9-112.el7
Doc Type: Bug Fix
Doc Text:
Cause: If multipath failed to resize a multipath device, the device would be left in the SUSPENDED state. Consequence: multipath devices would become unusable if a resize on them fails. Fix: If a resize fails, multipath will now resume using the device with the previous size. Result: When resizing a multipath device fails, the device is still usable.
Story Points: ---
Clone Of: 1444193
Environment:
Last Closed: 2018-04-10 12:10:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0884 normal SHIPPED_LIVE device-mapper-multipath bug fix and enhancement update 2018-04-10 09:47:14 EDT

  None (edit)
Comment 1 Ben Marzinski 2017-09-19 20:08:10 EDT
When multipath can't resize a map because both of the paths are not the same size, it will end up stuck in the suspended state.  The best solution here is to simply try to resume the device with the original size again.
Comment 8 errata-xmlrpc 2018-04-10 12:10:28 EDT
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/RHEA-2018:0884

Note You need to log in before you can comment on or make changes to this bug.