Comment 59 for bug 40189


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.