NFS client can mount, fails to automount

automountcentos5nfs

I have /etc/auto.master:

/cpy/users  /etc/auto.users --timeout=90

I have /etc/auto.users:

*   -fstype=nfs4,rw,proto=tcp,port=2049   server:/users/&

On an "ordinary" CentOS 5 machine, these work splendidly. On my virtual machine which has been built using "yum groupinstall core" and some minor adjustments, I get this when user myself logs in:

Apr 14 09:33:29 testing automount[5240]: handle_packet: type = 3
Apr 14 09:33:29 testing automount[5240]: handle_packet_missing_indirect: token 136, name myself, request pid 5249
Apr 14 09:33:29 testing automount[5240]: attempting to mount entry /cpy/users/myself
Apr 14 09:33:29 testing automount[5240]: lookup_mount: lookup(program): looking up myself
Apr 14 09:33:29 testing automount[5240]: lookup(program): lookup for myself failed
Apr 14 09:33:29 testing automount[5240]: ioctl_send_fail: token = 136
Apr 14 09:33:29 testing automount[5240]: handle_packet: type = 3
Apr 14 09:33:29 testing automount[5240]: handle_packet_missing_indirect: token 137, name myself, request pid 5249
Apr 14 09:33:29 testing automount[5240]: failed to mount /cpy/users/myself
Apr 14 09:33:29 testing automount[5240]: attempting to mount entry /cpy/users/myself
Apr 14 09:33:29 testing automount[5240]: ioctl_send_fail: token = 137
Apr 14 09:33:29 testing automount[5240]: failed to mount /cpy/users/myself

There is no network traffic against the NFS server when this occurs.

I realize that it can be a bit difficult to know exactly what is wrong, but any suggestion is welcome.

Best Answer

Gn! Answer to myself:

chmod -x /etc/auto.master /etc/auto.users

Problem solved. How's that for an obscure error message?

Related Solutions

Nfs – Recommended NFS mount options for automount maps

As you can't specify more for autofs then any regular NFS mounts all the caution regarding NFS applies. The rsize and wsize parameters have non-maximum defaults but will be negotiated when you set it to something very large and you have to check /proc/mountsto see what was negotiated. Generally your settings seem fine to me as a NFS service interruption taken care of in your case due to the intr,bg,timeo et al.

Do I understand that correctly, you mount NFS via a WAN?

Linux – Mount to NFS export of autofs mount shows empty contents

I think you have a cart before the horse problem here in that when you export a file system using NFS it locks on to the source direcotory. You are trying to not even have that source directory available at that time and only put something there via a mount later.

This will not work, because once you give NFS a handle on something to share, it will always share that thing, even if it ends up underneath a layer of mounts.

Let's say you setup a directory with a file 'frog' and export it with nfs:

[server] $ mkdir /mnt/test && touch /mnt/test/frog
[server] $ echo '/mnt/test *(ro)' >> /etc/exports
[server] $ exportfs -a

Then you mount it on a client somewhere, you will see the file frog as expected:

[client] $ mkdir /mnt/test
[client] $ mount -t nfs server:/mnt/test /mnt/test
[client] $ ls $/mnt/test
frog

Now let's say you mount something else on top of that folder on the server:

[server] $ mkdir /mnt/test2 && touch /mnt/test2/fish
[server] $ mount -o bind /mnt/test2 /mnt/test
[server] $ ls /mnt/test
fish

Spiffy. But what is nfs serving up?

[client] $ ls /mnt/test
frog

You can't even get to that file frog on the server because it's got a different thing mounted on top of it, but NFS is serving up that under layer!

To make a long story short, if you want to export your file systems via NFS you will need to have them mounted up properly at the time NFS starts up and exports them and they will need to stick around. Exporting file systems that are themselves mounted using autofs will never work quite right. You will need to permanently mount those ISOs in order to export them via NFS.

Related Topic