After doing a lot of testing I discovered extra parameters are needed in the mount command which are not required in Stretch (I have multiple computers and virtual machines running Stretch and none of them have needed these parameters when mounting a Samba share). The host server is also running Stretch.

these extra parameters are uid=xxxx,gid=xxxx

so a mount entry in /etc/fstab would look like

//111.222.33.44/sharename /mountpoint cifs credentials=/homepath/.smbcredentials,uid=1000,gid=1000

at the very minimum

Usually the number will be 1000 on a system with only one user. If you have a different uid for your user account or gid for your group you would presumably use that. If you have a multi user system I have no idea which uid/gid you would use as I have no knowledge of what these parameters do.

The findmnt command will list all the mount points and the default options assumed for each. If the uid and gid are not specified then the output from findmnt shows that these will each be defaulted to 0. It would seem there are enough differences in the cifs mounting for Buster to trip people up if they have not specified enough options.

On 26/11/17 03:48, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 882674: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882674.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   blackwhite...@gmail.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  LaMont Jones <lam...@debian.org>

If you wish to submit further information on this problem, please
send it to 882...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.


Reply via email to