Hello,
It's me again. So with today I've checked with three different hosts.
All running Xenial with autofs 5.1.1-1ubuntu3.1 and Kernel
4.4.0-116-generic. The host are a Thinkpad T410, X201 and a VirtualBox
guest system.
While the VirtualBox guest system works just fine, the autofs on the
Thinkpads did not work directly after boot. The autofs.service needs to
be restarted first in order to get autofs to work.
I have used tcpdump an strace to get some better look on what is
happening on the Thinkpads. So I did the following:
1. Boot Thinkpad
2. Setup tcpdump/wireshark snoop
3. Check that autofs is running with `sudo systemctl status autofs.service`
4. Run `strace ls -ld $MOUNTPOINT` where $MOUNTPOINT is the automounter share
from automounter map
In strace I see:
lstat("$MOUNTPOINT", 0x14861a0) = -1 ENOENT (No such file or directory)
The snoop shows that no single packet goes over the network to the NAS.
Next step:
5. Run `sudo systemctl status autofs.service`
6. Run `strace ls -ld $MOUNTPOINT` where $MOUNTPOINT is the automounter share
from automounter map
Now, in strace I see:
lstat("$MOUNTPOINT", {st_mode=S_IFDIR|0777, st_size=0, ...}) = 0
And in the snoop I see the expected packages crossing the network.
That's it. I do not know what else I could do to help with this matter.
If you need additional information tell me what you need, please.
Regards,
Tronde
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/40189
Title:
[SRU] [xenial] autofs needs to be restarted to pick up some shares
Status in autofs package in Ubuntu:
Fix Released
Status in autofs5 package in Ubuntu:
Invalid
Status in upstart package in Ubuntu:
Invalid
Status in autofs source package in Xenial:
Incomplete
Bug description:
I am using autofs to access shares on a Windows XP machine from a
Kubuntu AMD64 machine. The problems applies in both Breezy and
Dapper.
EDIT: confirmed with similar configuration on Intrepid with a NetApp
filer hosting NFS. Server OS removed from summary.
When I first try to access the mount point via cd or in Konqueror it
does not exist. However, if I then restart autofs
(/etc/init.d/autofs restart) everythin then works OK. My config files
are:
auto.master
#
# $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc /etc/auto.misc --timeout=60
#/misc /etc/auto.misc
#/net /etc/auto.net
/petunia /etc/petunia.misc --timeout=60
petunia.misc
#
# $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
#
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# Details may be found in the autofs(5) manpage
cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/tony
chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/chris
shared -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/SharedDocs
linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/linuxbackups
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
