Summary: | sys-apps/openrc-0.18.4: netmount fails to start although all netmounts are correctly mounted | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Till Schäfer <till2.schaefer> |
Component: | [OLD] Core system | Assignee: | OpenRC Team <openrc> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Till Schäfer
2015-12-19 03:29:42 UTC
For cifs file systems, you should not specify _netdev in the mount options; cifs is always a network file system. Try removing cifs from the mount options for the network file systems in fstab and report back whether or not this works. Thanks, William Removing "_netdev" did the trick. THX However, its somewhat unintuitive. I thought that every network share should have the _netdev option, such that netmount knows about which filesystems to mount. Is there any place that explains the _netdev option in more detail? Why does adding this option harm netmount? I was initially confused about the use of the _netdev option as well; however, documenting this is not an issue specifically related to OpenRC. Netmount first mounts all file systems that we know are network file systems. We know this by the type of the file system, cifs or nfs are a couple of examples. Then, netmount mounts all file systems with _netdev in their mount options. The _netdev option is used to delay the mounting of *any* file system until after the network is active. If you use it with a file system that we already know requires a network connection, netmount will mount that file system twice and you will get this failure. The example I am aware of that uses _netdev is iscsi, but I'm sure there are others. The _netdev option is mentioned briefly on the mount man page, but I'm not sure how well it explains this usage. |