Public bug reported:
I installed smbfs, and then put some entries into /etc/fstab, so they automount
on startup. An example of this is here:
//<ip address of nas box>/<share name> /home/hamish/<directory name> cifs
credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000
0 0
** note the use of "cifs" in the lines above **
(The username and password are in the .smbcredentials file)
On startup, for each entry in the /etc/fstab file, I get the following in dmesg:
[ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation
[ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101
But the shares are mounted, and a nautilus session opens up (which is also
annoying...)
Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error
message:
CIFS VFS: server not responding
CIFS VFS: no response for cmd 50 mid <this number changes>
And takes about 2 minutes to timeout. This also happened with Gutsy
Should the timing of the mounting and dismounting be changed so that it
works? It is related to the starting of network-manager and CIFS shares
trying to connect on startup *before* the network is up, and dismounting
the shares *after* network-manager is stopped.
Hamish
PS: note to Chuck Short. I am using cifs.
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
CIFS/SMBFS issue (was not resolved on #207441)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
