mount.cifs is not part of util-linux, and it also is not supposed to
ignore unknown options. This is only a feature of util-linux mount
since it is generic, and not expected to understand every possible
option supported by every possible filesystem.
--
You received this bug notification because
However, mount.cifs ignores the options passed to it by the util-linux
mount when it is not invoked by root. In that case, mount.cifs obtains
the options from the fstab file and does not do any processing to ignore
comments. So the status of this bug should not be invalid, unless
mount.cifs is not
I don't think that is a bug in mount.cifs then. The util-linux mount
treats x-* options as comments or application specific options.
mount.cifs is the specific application, and it expects to be able to
recognize all mount options.
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
After further investigation, it turns out that mount is actually
handling the options correctly and passing the options (with x-* options
removed) to mount.cifs. The problem is that mount.cifs ignores those
passed options if the user running the mount command is not root, and
just grabs the
output from "mount -v /mnt/mybook":
mount.cifs kernel mount options:
ip=192.168.1.3,unc=\\192.168.1.3\Public,noauto,x-
test.opt,noperm,soft,cache=none,sec=none,uid=1000,gid=1000,user=,pass=
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
--
5 matches
Mail list logo
