Red Hat Bugzilla – Bug 461469
device-mapper changes to support readonly device maps
Last modified: 2010-10-23 00:21:41 EDT
Description of problem:
This bug is to track the kernel changes needed for bug 444421. Device-mapper currently does not propagate EROFS errors from the dm constructor to user space so multipath-tools cannot take appropriate decisions when constructing multipath maps for these devices.
Ben has a proposed patch attached to bug 444421:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Present a readonly device from an array
2. Scan for devices from the host
3. run "multipath -v3"
"domap (0) failure for create/reload map" is observed for the readonly device
and the multipath map is not getting created.
DM devices have to be created for readonly devices also.
Created attachment 316070 [details]
mpath propagate path errors
Propagate path errors to user space from multipath constructor.
Patch in comment#1 is in agk's patch set:
Upstream in 2.6.28.
Author: Benjamin Marzinski <firstname.lastname@example.org>
Date: Fri Oct 10 13:36:57 2008 +0100
dm mpath: use more error codes
This patch allows path errors from the multipath ctr function to
propagate up to userspace as errno values from the ioctl() call.
This is in response to
The patch only lets through the errors that it needs to in order to
get the path errors from parse_path().
Signed-off-by: Benjamin Marzinski <email@example.com>
Signed-off-by: Alasdair G Kergon <firstname.lastname@example.org>
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Updating PM score.
You can download this test kernel from http://people.redhat.com/dzickus/el5
Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so. However feel free
to provide a comment indicating that this fix has been verified.
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
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 therefore 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.