Bug 427880
| Summary: | ENHANCEMENT - new multipath scheduler - striped | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Burn Alting <burn> |
| Component: | device-mapper-multipath | Assignee: | LVM and device-mapper development team <lvm-team> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | agk, bmarzins, dwysocha, mbroz, prockai |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-09 05:44:08 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: | |||
|
Description
Burn Alting
2008-01-08 00:43:14 UTC
Do you have any code for this? If so, please submit to dm-devel, the external list for upstream inclusion. Thanks. Sorry Dave I don't. I looked at this some time ago and put it into the too hard basket. I seem to remember the difficulty was that by the time the code decides what path to take, it has already committed to a block number for the io. The idea here is to, based on the io, either submit it to a specific path or break the io into 2 (or more if needed) and submit each 'sub-io' to the appropriate pathes. Sorry Burn Do you have something you could test out prototype code and measure any performance difference? Yes. I have full access (programming that is) to dual controller raid systems where I can configure raidsets to be accessed by both raid controllers (active-active) - I only have a dual port FC HBA so I could only test two paths at once at the moment. Sorry I have not had much time to work on this. The best next step is probably posting your design thoughts to dm-devel with a "RFC" subject line. You may find interest there who can help move this along. This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |