Bug 607309
| Summary: | cifs mount errors out on _netdev option | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Penelope Fudd <bugzilla.redhat.com> |
| Component: | cifs-utils | Assignee: | Jeff Layton <jlayton> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | extras-orphan, jlayton, jonathan, kzak, ssorce, steved |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | cifs-utils-4.6-1.fc13 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-08-06 20:57:19 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
Penelope Fudd
2010-06-23 18:52:13 UTC
Well, -101 is -ENETUNREACH so it does seem like the mount was attempted before networking was up. As best I can tell though, _netdev is ignored by mount.nfs, so I assume this is what we should do in mount.cifs as well. Reassigning this bug to util-linux for now... I reassigned this to util-linux as this seems like a /bin/mount problem. Shouldn't /bin/mount be ensuring that networking is up before trying to mount in this case? Karel, I could use some clarification here. Who is expected to manage the _netdev option? mount.nfs ignores it. mount.cifs passes it to the kernel currently (which we need to fix), but I'd like to know what the expectation with that option actually is. If the mount helpers are expected to handle it, what criteria should be met before allowing the mount to proceed? It really seems like an option that ought to be deprecated -- the situation with networking these days is much more complex than it was when this option was introduced and I'm not sure we can reasonably handle it correctly. (In reply to comment #2) > I reassigned this to util-linux as this seems like a /bin/mount problem. > Shouldn't /bin/mount be ensuring that networking is up before trying to mount > in this case? Oh.. no. The _netdev option is ignored in mount(8) by default. The options is used by initscripts only. The traditional way how we use this option is to call mount(8) with -O option, man mount: -O Used in conjunction with -a, to limit the set of filesystems to which the -a is applied. Like -t in this regard except that it is useless except in the context of -a. For example, the command: mount -a -O no_netdev I think the best solution is to ignore the option in mount helpers. Really. You don't have to care about it. Now mount(8) calls /sbin/mount.<type> helpers with all fstab & command line options. Maybe we can change this policy. BTW, all MS_COMMENTs from mount(8): { "_netdev", 0, 0, MS_COMMENT}, /* Device requires network */ { "comment", 0, 0, MS_COMMENT}, /* fstab comment only (kudzu,_netdev)*/ { "nofail", 0, 0, M S_COMMENT}, /* Do not fail if ENOENT on dev */ Ok, thanks Karel...moving back to cifs-utils. I've pushed some patches to mainline cifs-utils and to the cifs kernel maintainer for this. Updated cifs-utils fedora packages are forthcoming. cifs-utils-4.6-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/cifs-utils-4.6-1.fc13 cifs-utils-4.6-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update cifs-utils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/cifs-utils-4.6-1.fc13 cifs-utils-4.6-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |