Back to bug 1322532

Who When What Removed Added
Lin Li 2016-03-31 08:50:34 UTC QA Contact storage-qe lilin
Ben Marzinski 2016-08-12 17:58:21 UTC Blocks 1324930
Zhang Yi 2016-08-16 03:06:17 UTC CC yizhan
Zhang Yi 2016-08-16 03:11:18 UTC QA Contact lilin yizhan
Ben Marzinski 2016-10-15 19:15:02 UTC Status ASSIGNED MODIFIED
Fixed In Version device-mapper-multipath-0.4.9-94.el6
Doc Text Cause: Multipathd automatically reinstated Implicit ALUA devices in the GHOST state, which were not usable.

Consequence: Multipath would continuously retry unusable devices, if they were the only ones present, instead of fail IO

Fix: Multipathd no longer reinstates unusable Implicit ALUA ghost paths.

Result: Multipath no longer continuously reties IO when only unusable Implicit ALUA paths are available.
Milan Navratil 2016-10-17 10:47:47 UTC Docs Contact mnavrati
errata-xmlrpc 2016-10-17 18:08:28 UTC Status MODIFIED ON_QA
Zhang Yi 2016-12-08 03:49:16 UTC QA Contact yizhan lilin
Lin Li 2016-12-14 08:15:16 UTC Keywords OtherQA
Lin Li 2017-01-05 06:49:59 UTC Flags needinfo?(shiva.krishna)
Milan Navratil 2017-01-06 16:29:50 UTC Doc Text Cause: Multipathd automatically reinstated Implicit ALUA devices in the GHOST state, which were not usable.

Consequence: Multipath would continuously retry unusable devices, if they were the only ones present, instead of fail IO

Fix: Multipathd no longer reinstates unusable Implicit ALUA ghost paths.

Result: Multipath no longer continuously reties IO when only unusable Implicit ALUA paths are available.
*device-mapper-multipath* no longer continuously retries I/O when only unusable Implicit ALUA paths are available

Previously, the *multipathd* service automatically reinstated unusable Implicit ALUA devices in the GHOST state. As a consequence, multipath continuously retried unusable devices, if they were the only ones present, instead of failing I/O. With this update, *multipathd* no longer reinstates unusable Implicit ALUA ghost paths. As a result, *multipathd* fails I/O as expected in the described situation.
Flags needinfo?(bmarzins)
Milan Navratil 2017-01-11 13:36:12 UTC Doc Text *device-mapper-multipath* no longer continuously retries I/O when only unusable Implicit ALUA paths are available

Previously, the *multipathd* service automatically reinstated unusable Implicit ALUA devices in the GHOST state. As a consequence, multipath continuously retried unusable devices, if they were the only ones present, instead of failing I/O. With this update, *multipathd* no longer reinstates unusable Implicit ALUA ghost paths. As a result, *multipathd* fails I/O as expected in the described situation.
*device-mapper-multipath* now supports the `max_sectors_kb` configuration parameter

With this update, *device-mapper-multipath* provides a new `max_sectors_kb` parameter in the defaults, devices, and multipaths sections of the `multipath.conf` configuration file. This parameter allows you to set the 'max_sectors_kb` device queue parameter to the specified value on all underlying paths of a multipath device before the multipath device is first activated.

When a multipath device is created, the device inherits the `max_sectors_kb` value from the path devices. Manually raising this value for the multipath device or lowering this value for the path devices can cause multipath to create I/O operations larger than the path devices allow.

Using the `max_sectors_kb` `multipath.conf` parameter is an easy way to set these values before a multipath device is created on top of the path devices, and prevent invalid-sized I/O operations from being passed down.
Ben Marzinski 2017-01-11 17:15:57 UTC Flags needinfo?(shiva.krishna) needinfo?(bmarzins)
Steven J. Levine 2017-01-17 20:39:58 UTC Blocks 1414128
Hanns-Joachim Uhl 2017-01-22 09:03:15 UTC Target Release --- 6.9
CC hannsj_uhl
Lin Li 2017-02-06 06:21:33 UTC Flags needinfo?(shiva.krishna)
Lin Li 2017-02-17 03:21:14 UTC Status ON_QA VERIFIED
Milan Navratil 2017-03-20 08:44:51 UTC Doc Type Bug Fix No Doc Update
errata-xmlrpc 2017-03-21 01:09:49 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-03-21 10:49:51 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-03-21 06:49:51 UTC

Back to bug 1322532