Bug 144537
Summary: | devlabel not automounting when run by hotplug | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Tom Parris <parris> |
Component: | devlabel | Assignee: | Karel Zak <kzak> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | crunge, gary_lerhaupt, notting |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-11 12:09:59 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
Tom Parris
2005-01-07 22:35:50 UTC
Do the fixes in bug 144241 work for you? Thanks for the quick response. I tried the patch. Unfortunately, it did not appear to change the behavior reported above. *** Bug 102056 has been marked as a duplicate of this bug. *** Yes, it seems like timing problem, but I have no idea how we can decide when we should wait for device and when it's correct that the device doesn't exist. Any idea? I'm far from an expert on the internals of hotplug and devlabel. But it seems that when hotplug detects the new device, it should wait until the device (/dev/sda1 in the example above) is ready before calling devlabel to mount it. Isn't this as simple as a loop waiting for the device to show up in the file system? The delay between checks could be fairly long (1 second) since this is not a time sensitive task. This could also be done in usb.agent, but I think it better done in hotplug since this would be a common issue across all buses. My two bits. I think hotplug doesn't detect any device. It calls modprobe and all depends on kernel modules. I'm really not sure that kernel must always create /dev/something. It depends on type of USB/PCMCIA/etc. Add CC: to hotplug maintainer. Realistically, it should probably be running from the SCSI hotplug event, not the USB one. However, the 2.4 kernel doesn't generate SCSI hotplug events. That makes this awfully hard to fix. Sorry, it seems like WONTFIX. Closing. |