|
Bugzilla – Full Text Bug Listing |
| Summary: | filesystems mounted twice | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Marcus Meissner <meissner> |
| Component: | Basesystem | Assignee: | Ruediger Oertel <ro> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | hare, rw, werner |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
boot.msg
fstab |
||
|
Description
Marcus Meissner
2006-01-24 17:56:24 UTC
Created attachment 64834 [details]
boot.msg
Please attach the /etc/fstab Created attachment 64835 [details]
fstab
'udev' and 'boot.localfs' are racing for 'fsck' and 'mount'... See bug #145400 -- but I don't think it's a simple duplicate. Does anybody know, what happens if 'fsck.*' is halfway through a filesystem, while somebody else blindly triggers a 'mount' ? (on every "supported" file-system?) Shouldn't happen. boot.localfs has a dependency on boot.udev. boot.udev waits for all events to finish, ie also all fsck / mount calls triggered by events will be done once boot.udev finishes. The only instance where this _might_ happen is when using USB disks, as USB detects devices asynchronously. boot.localfs mounts with "-noopts=hotplug", udev will only touch the hotplug devices now. |