severity 695533 minor thanks On Mon, Dec 10, 2012 at 10:01:50AM +1300, Hugh Davenport wrote: > Package: cifs-utils > Version: 2:4.5-2+squeeze1 > Severity: important
> >From mount(8), under "FILESYSTEM INDEPENDENT MOUNT OPTIONS" > there is a mount option "_netdev" which is meant to require > the network to be up before attempting to mount. Full description > is below. > When the system is booted, I get the following in my error log: > Dec 10 09:42:03 fir kernel: [ 21.068520] CIFS: Unknown mount option _netdev > Dec 10 09:42:03 fir kernel: [ 21.116416] CIFS VFS: Error connecting to > socket. Aborting operation > Dec 10 09:42:03 fir kernel: [ 21.116423] CIFS VFS: cifs_mount failed > w/return code = -111 > Dec 10 09:42:03 fir kernel: [ 21.116459] CIFS: Unknown mount option _netdev > The filesystem is not mounted. Once I get a shell, I can `mount -a` > and the mount comes up correctly. > This has worked on mount.nfs, but not on mount.cifs. A bit of > googling found the following bug report in redhat that has been > resolved. I think this "filesystem-independent mount option" is supposed to be parsed out by mount itself, not passed to mount.cifs. I don't know why that isn't happening, but I suspect this is a util-linux bug. However, there's no reason for you to set _netdev at all here. The boot infrastructure knows that cifs is a network filesystem, and that *all* cifs mounts must wait for the network; so specifying a mount option is redundant. The _netdev option is meant to be used when the filesystem is of a local type, but the *underlying block device* requires the network to be up before it's available (e.g., aoe, nbd, iscsi). -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
