Bug 595522
Summary: | udev should not restrict /dev/disk/by-path entries for all "virtual" devices | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Robert Love <robert.w.love> |
Component: | udev | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED DUPLICATE | QA Contact: | qe-baseos-daemons |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | ddumas, hdegoede, pknirsch, supreeth.venkataraman, yi.zou |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-08 13:26:28 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
Robert Love
2010-05-24 21:13:48 UTC
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 inclusion. Is there a way to detect if a virtual device is a FCOE device? If so, then it should be fairly easy to do. Thanks & regards, Phil I think the problem is slightly broader than the initial reporting. Any networked storage on a VLAN would have this issue. For example, if iSCSI were run on a VLAN there would be no by-path entry. Sorry to answer your question with another question, but how do I know which path udev is using for its rules in the sysfs tree? With that info I can tell you what the FCoE path looks like. *** Bug 593744 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 601248 *** |