I have the same problem: on # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 10.04.3 LTS Release: 10.04 Codename: lucid
none of the these options worked for me, short: - dbus.conf - K14 links - S31 earlier - a modprobe option http://blog.dhampir.no/content/cifs-vfs-no-response-for-cmd-n-mid the only option that seemed to work i found on http://hardc0l2e.wordpress.com/2011/06/30/ubuntu-11-04-shutdown-and-restart-problem-with-cifs/ in short: " Rename the current shutdown, reboot and restart commands in /sbin. #> mv /sbin/shutdown /sbin/shutdown2 #> mv /sbin/reboot /sbin/reboot2 #> mv /sbin/restart /sbin/restart2 2. Then create scripts with names of the previous commands in /sbin, which contains the following: #!/bin/sh umount -t cifs -a -f -l /sbin/shutdown2 $@ exit 0 3. Make similar script for reboot and restart command which also points to /sbin/reboot2 and /sbin/restart2. " but i also had to change the two links under /sbin, halt and poweroff to point to reboot2 instead of reboot, otherwise my machine would shutdown when isuing a shutdown -h now, but just rebooted instead. Could this be related to cifs getting mounted twice (when present in fstab)? It took me quiet some time, to test, and find a solution. more output: i use cifs mount with a vpn connection (cisco), after mount -a i then get $mount .. /dev/sdb1 on /media/terra type ext4 (rw,nosuid,nodev,uhelper=udisks) //fas-gt-01/rt on /mnt/rt type cifs (rw,mand) //fas-gt-02/brt on /mnt/brt_gt type cifs (rw,mand) //fas-gt-02/EX on /mnt/Ex type cifs (ro,mand) //fas-gt-02/EX on /mnt/Ex type cifs (ro,mand) //fas-gt-02/GR on /mnt/gr type cifs (ro,mand) //fas-gt-02/GR on /mnt/gr type cifs (ro,mand) So the ro mount are mounted twide..? While the rw get mounted once.. fstab options rw mount: cifs rw,noserverinfo,uid=1000,gid=1000,file_mode=0750,dir_mode=0750,credentials=/home/user/config/scripts/.cifs.credentials fstab options rw mount: cifs ro,noserverinfo,uid=1000,gid=1000,file_mode=0440,dir_mode=0440,credentials=/home/user/config/scripts/.cifs.credentials i have attached cifs entries in syslog hth, G ** Attachment added: "cifs.syslog.grep" https://bugs.launchpad.net/network-manager/+bug/211631/+attachment/2569695/+files/cifs.syslog.grep -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) Status in NetworkManager: New Status in NULL Project: Invalid Status in “dbus” package in Ubuntu: Fix Released Status in “dhcdbd” package in Ubuntu: Invalid Status in “netbase” package in Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Confirmed Status in “samba” package in Ubuntu: Invalid Status in “sysvinit” package in Ubuntu: Invalid Status in “wpasupplicant” package in Ubuntu: Confirmed Status in “dbus” source package in Lucid: New Status in “dhcdbd” source package in Lucid: Invalid Status in “netbase” source package in Lucid: New Status in “network-manager” source package in Lucid: New Status in “samba” source package in Lucid: New Status in “sysvinit” source package in Lucid: New Status in “wpasupplicant” source package in Lucid: New Status in “dbus” source package in Natty: New Status in “dhcdbd” source package in Natty: Invalid Status in “netbase” source package in Natty: New Status in “network-manager” source package in Natty: New Status in “samba” source package in Natty: New Status in “sysvinit” source package in Natty: New Status in “wpasupplicant” source package in Natty: New Status in “sysvinit” package in Debian: New Bug description: IMPORTANT: this bug has enough information; please don't post _anything_ unless a developer asks for specific feedback! By posting to this bug you only make it harder for a developer to spot the gem comments. Please use the "me too feature" of launchpad to signal that you are affected and would like to see this fixed. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/211631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
