This bug was fixed in the package mountall - 2.52
---
mountall (2.52) unstable; urgency=low
* Don't emit extra 'mounting' events for mounts already in progress; this
will cause double triggering of some jobs for remote filesystems, and
can also cause us to miss 'mounted'
pat@Pats-Main:~$ sudo initctl status mountall
[sudo] password for pat:
mountall start/running, process 266
pat@Pats-Main:~$ ps 266
PID TTY STAT TIME COMMAND
I moved ~/.smbcredentials to /.smbcredentials and chown'ed it to
root:pat 0777.
It's still not automounting on login. Let me know
Oh, already well past frustrated, here. :) But the latest results at
least confirm one thing, the mountall process is dying before mountall-
net signals it (and before it successfully mounts the network mounts,
either). This doesn't make it any less confusing - if mountall died,
upstart should
OK, I accuired a wild hair and downgraded mountall to
v2.48build1(raring) and now everything is alright. I still get the flood
of cifs errors on boot, but once I log on, my cifs shares are mounted. I
looked for my mountall.log, but it appears to have gone MIA... :$
--
You received this bug
Ah, and now I'm able to reproduce this problem here... and have pinned
down which change of mine caused it. Apparently mountall-net was broken
for everyone, and I just managed to not notice. Sorry about that. I'll
push a fix ASAP for 13.10.
** Changed in: cifs-utils (Ubuntu)
Status: New
** Branch linked: lp:ubuntu/mountall
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235013
Title:
13.10-Network (cifs) drives do not load.
To manage notifications about this bug go to:
So I've just debugged bug #1233610 regarding a similar issue with NFS
mounts. Do you have a hostname for 192.168.1.13 that's resolvable via
DNS (*not* via /etc/hosts)? If so, perhaps you could try mounting by
name instead of IP to work around the kernel's behavior when asked to
mount from an
OK, just so I didn't misunderstand, I made these changes in fstab:
//www.buddlespit.org/Shares /mnt/Shares cifs
guest,uid=1000,iocharset=utf8,sec=ntlmv2 00
//Server/Homes /mnt/Homes cifs
In the latest log I do see the network mounts being attempted several
times, but with no trigger shown in the log. That seems to be
consistent with the mountall-net.log, which shows mountall isn't there
to be signalled. What does the network configuration for this machine
look like? Are you
apport information
** Tags added: apport-collected saucy
** Description changed:
Description:Ubuntu Saucy Salamander (development branch)
Release:13.10
cifs-utils:
Installed: 2:6.0-1ubuntu2
upstart:
Installed: 1.10-0ubuntu3
Since the release of beta2,
Sorry, ran it twice because of an error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235013
Title:
13.10-Network (cifs) drives do not load.
To manage notifications about this bug go to:
pat@Pats-Main:~$ sudo initctl status mountall
[sudo] password for pat:
mountall start/running, process 266
I believe I'm running the default NetworkManager installed by Kubuntu. I
haven't changed it.
/etc/network/interfaces:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo
pat@Pats-Main:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 8c:89:a5:32:34:31
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8e89:a5ff:fe32:3431/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX
Ok, so no modified conffiles.
//Server/Homes /mnt/Homes cifs
auto,_netdev,credentials=/home/pat/.smbcredentials,iocharset=utf8,sec=ntlmv2
00
This is a potential source of boot-time unreliability, fwiw; /mnt/Homes
can't be mounted until /home/pat/.smbcredentials is available, but
** Also affects: upstart
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235013
Title:
13.10-Network (cifs) drives do not load.
To manage notifications
from mountall-net.log:
/proc/self/fd/9: 3: kill: No such process
/proc/self/fd/9: 3: kill: No such process
And what is the output of /var/log/upstart/mountall.log? Please boot
with '--verbose' added to the kernel commandline and attach the
resulting log file.
** Project changed: upstart =
** Attachment added: Attached mountall.log
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1235013/+attachment/3863369/+files/mountall.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mountall (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235013
Title:
13.10-Network (cifs) drives do not load.
To manage notifications about
So the logs together show that the filesystems are not being mounted
because the mount is attempted before the network is up, and that
mountall has for some reason exited before the network comes up and the
mountall-net job has a chance to signal mountall with SIGUSR1. I'm not
sure what's causing
On previous releases, I usually got the cifs error when the drives were
mounted, but they were mounted once I logged in and opened Dolphin. So,
something between 13.04 and 13.10 changed. I should also note that I
upgraded to 13.10. It's not a clean install.
--
You received this bug notification
I should also point out that I can mount the drives manually and I can
mout the drives with 'sudo mount -a'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235013
Title:
13.10-Network (cifs) drives
21 matches
Mail list logo
