Bug 108640 (udev)
| Summary: | RHEL4: Support Persistent Device Naming (udev) kernel portion | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Matt Webbink <mattwebb> | ||||
| Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Jenner <mjenner> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.0 | CC: | bjohnson, dkl, harald, katzj, nobody+wcheng, notting, rperkins, sdenham, tao | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| URL: | IT_11384 | ||||||
| Whiteboard: | Kernel | ||||||
| Fixed In Version: | 2.6.9-5 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-02-27 18:11:15 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 113838 | ||||||
| Attachments: |
|
||||||
|
Description
Matt Webbink
2003-10-30 20:49:47 UTC
Does sysfs provide persistent device naming in 2.6? *** Bug 108795 has been marked as a duplicate of this bug. *** *** Bug 109110 has been marked as a duplicate of this bug. *** *** Bug 109031 has been marked as a duplicate of this bug. *** From Fujitsu's slides Oct 2003: Name Space Stability Feature Keep hardware name consistent beyond reboot Even after hardware is removed because of failure or is added, all hardware names required persistent. After failed hardware is replaced, replaced hardware can be used as a same name as failed one. Focus to NIC / FC and Disks (FC/SCSI connected) Benefit / Need Stability at operation: Many scripts to operate and configurations should not be modified because of adding new hardware, removing old hardware and replacing failed hardware. Key for large scale server: If this feature would be lacked, data corruption and data-leak will be happen. Name Space Stability Activities udev Name space stability in /dev http://linux-hotplug.sourceforge.net nameif Name space stability in network card name space http://linux-hotplug.sourceforge.net nif (Hot Device Identify) PCI-card Name space stability http://sourceforge.net/projects/hdi/ Dependency / Assumption sysfs : fundamental function for name space stability Name Space Stability FJâs TODO Enhance udev at hot-plug community Support LUN/SCSI-id based naming in /dev Enhance nif Stabilize nif Support PCI-slot / PCI-bus# based naming Schedule / What expected to be included in RHEL4 All patches will be available at hot-plug and nif community by end of Mar. 2004. Created attachment 97184 [details]
Fujitsu Oct 2003 Slides
NIF is completely superflous in the presence of nameif; it's not needed, the feature is already in RHEL3. Adding NEC request for udev/USDE- vague request that must be further defined. Amazon is also keenly interested in persistent device naming in the RHEL4 context. NEC would like an example of a sample confiuration that is suggested by red hat. What is the forum for discussing this issue within red hat? Who should we involve internally within the discussion. There has been created a mailing list to discuss this matter: http://lists.osdl.org/mailman/listinfo/device_naming udev is under heavy development... *** Bug 113399 has been marked as a duplicate of this bug. *** Setting state to MODIFIED as Arjan says all the kernel portion is done. Note, the user level portion of the udev feature is separately noted in bug #113838 |