| Summary: | udevadm can not handle cciss driver's device file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | masanari iida <masanari_iida> | ||||
| Component: | udev | Assignee: | Harald Hoyer <harald> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-daemons | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0 | ||||||
| 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: | 2011-04-01 09:30:31 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
what's the output of: # udevadm info --query=all --name=cciss/c0d0 (In reply to comment #0) > Good example (See attached file for full output) > # udevadm info --query=all --name=/dev/cciss/c0d0 > N: cciss/c0d0 Here you see the name... "cciss/c0d0" ! For example, if it is a scsi device, both sda and /dev/sda returns same result. But in cciss case, c0d0 returns "device node not found", and /dev/cciss/c0d0 returns correct result. I thought udevadm can not handle cciss case, because cciss driver have one more path depth than other devices. Confirmed -name=cciss/c0d0 works.
Thanks.
If you think this is not a bug, would you agree to modify the man page?
Current:
--name=file
The name of the device node or a symlink to query
Proposed:
--name=file
The name of the device node specified by a path from /dev or a symlink to query.
|
Created attachment 489329 [details] udevadm full output Description of problem: udevadm can not handle cciss driver's device file without full path Version-Release number of selected component (if applicable): udev-147-2.29.el6.i686 How reproducible: Always Steps to Reproduce: If you want to reproduce this symptom, you need to use a system with SmartArray (cciss) is installed. Bad examples # udevadm info --query=all --name=c0d0 device node not found # udevadm info --query=all --name=c0d0p1 device node not found Good example (See attached file for full output) # udevadm info --query=all --name=/dev/cciss/c0d0 P: /devices/pci0000:40/0000:40:11.0/0000:48:00.0/cciss0/c0d0/block/cciss!c0d0 N: cciss/c0d0 W: 37 S: block/104:0 S: disk/by-id/cciss-3600508b100105039565759303555002a S: disk/by-path/pci-0000:48:00.0 S: disk/by-id/wwn-0x600508b100105039565759303555002a E: UDEV_LOG=3 E: DEVPATH=/devices/pci0000:40/0000:40:11.0/0000:48:00.0/cciss0/c0d0/block/cciss!c0d0 E: MAJOR=104 E: MINOR=0 E: DEVNAME=/dev/cciss/c0d0 E: DEVTYPE=disk E: SUBSYSTEM=block E: ID_SCSI=1 E: ID_VENDOR=HP E: ID_VENDOR_ENC=HP\x20\x20\x20\x20\x20\x20 E: ID_MODEL=LOGICAL_VOLUME E: ID_MODEL_ENC=LOGICAL\x20VOLUME\x20\x20 E: ID_REVISION=7.22 E: ID_TYPE=disk (snip)