Red Hat Bugzilla – Bug 208337
[RHEL5 Beta1] anaconda: multipath device name is reverse order of LUN number.
Last modified: 2010-10-22 02:11:51 EDT
Description of problem:
Installer names misleading device name for multipath devices.
It seems to be reverse order of LUN number.
(e.g. In 4 LUN environment, LUN#0 is named as "mpath3",
LUN#1 is named as "mpath2", ..., LUN#3 is name as "mpath0".)
Version-Release number of selected component:
Steps to Reproduce:
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
Is this still a problem? As far as I know this was fixed long, long ago.
Bryn Reeves says this is fixed in the 5.1 nightly trees, but is still dependent
on hardware. Certain systems are forced to initialize devices in a specific
order and that may not coincide with the LUN order.
However, all hardware aside, the software does init devices in LUN order. As
soon as hardware comes in, that order is changed up. Not much we can do about that.
Yes, I confirmed this is fixed on our storages.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.