Problems with Autofs and .hidden files
Hello!
We are using autofs in order to mount the user's home drive via NFS after a successfull login authenticated by ldap.
/etc/auto.master looks like this:
# AUOTOFS-MAPPING/home/schueler /etc/auto.schueler/home/lehrer /etc/auto.lehrer/home/maerkte /etc/auto.maerkte
/etc/auto.schueler has the following content (the same also applies for the other files):
* -fstype=nfs,rw,hard,intr,nodev,nosuid,exec,acl server.domain.de:/home/schueler/&
Generally speaking this setup works like a charm but from time to time we encounter the following messages in syslog:
Sep 24 16:46:57 server mountd[8818]: authenticated mount request from client.domain.de:559 for /home/schueler/.directory (/home/schueler) Sep 24 16:46:57 server mountd[8818]: can't stat exported
dir /home/schueler/.directory: No such file or directory
Our investigations show that these messages are probably to be created whenever a user tries to access /home/schueler by using Konqueror or Nautilus. The file .directory doesn't exist, however, and that's why these messages appaer. Normalley, this wouldn't be a severe problem but the entire is completely slowed down so that another kind of error occurs:
Sep 24 16:47:00 server mountd[8818]: refused mount request from
client.domain.de for /home/schueler/.directory (/home/schueler): illegal port 48337
Does anybody know this issue and could provide any hints how to solve it?
Cheers,
Fabian
Quoted 32 lines · Fabian Steiner
Hello!
We are using autofs in order to mount the user's home drive via NFS after a successfull login authenticated by ldap.
/etc/auto.masterlooks like this:# AUOTOFS-MAPPING
/home/schueler/etc/auto.schueler/home/lehrer/etc/auto.lehrer/home/maerkte/etc/auto.maerkte
/etc/auto.schuelerhas the following content (the same also applies for the other files):* -fstype=nfs,rw,hard,intr,nodev,nosuid,exec,acl server.domain.de:/home/schueler/&
Generally speaking this setup works like a charm but from time to time we encounter the following messages in syslog:
Sep 24 16:46:57 server mountd[8818]: authenticated mount request from client.domain.de:559 for /home/schueler/.directory (/home/schueler) Sep 24 16:46:57 server mountd[8818]: can't stat exporteddir
/home/schueler/.directory: No such file or directoryOur investigations show that these messages are probably to be created whenever a user tries to access
/home/schuelerby using Konqueror or Nautilus. The file .directory doesn't exist, however, and that's why these messages appaer. Normalley, this wouldn't be a severe problem but the entire is completely slowed down so that another kind of error occurs:
Quoted 5 lines
Sep 24 16:47:00 server mountd[8818]: refused mount request fromclient.domain.de for
/home/schueler/.directory(/home/schueler): illegal port 48337Does anybody know this issue and could provide any hints how to solve it?
Negative lookup caching will help this. I'm not sure whether/when that went into the kernel. Ian?
-Jeff
Ian Kent
maintainerQuoted 34 lines · Jeff Moyer
Quoted 32 lines · Fabian Steiner
Hello!
We are using autofs in order to mount the user's home drive via NFS after a successfull login authenticated by ldap.
/etc/auto.masterlooks like this:# AUOTOFS-MAPPING
/home/schueler /etc/auto.schueler /home/lehrer /etc/auto.lehrer /home/maerkte /etc/auto.maerkte
/etc/auto.schuelerhas the following content (the same also applies for the other files):* -fstype=nfs,rw,hard,intr,nodev,nosuid,exec,acl
server.domain.de:/home/schueler/&Generally speaking this setup works like a charm but from time to time we encounter the following messages in syslog:
Sep 24 16:46:57 server mountd[8818]: authenticated mount request from client.domain.de:559 for /home/schueler/.directory (/home/schueler) Sep 24 16:46:57 server mountd[8818]: can't stat exporteddir
/home/schueler/.directory: No such file or directoryOur investigations show that these messages are probably to be created whenever a user tries to access
/home/schuelerby using Konqueror or Nautilus. The file .directory doesn't exist, however, and that's why these messages appaer. Normalley, this wouldn't be a severe problem but the entire is completely slowed down so that another kind of error occurs:
Quoted 8 lines
Quoted 5 lines
Sep 24 16:47:00 server mountd[8818]: refused mount request fromclient.domain.de for
/home/schueler/.directory(/home/schueler): illegal port 48337Does anybody know this issue and could provide any hints how to solve it?
Negative lookup caching will help this. I'm not sure whether/when that went into the kernel. Ian?
There was a report of the patch causing a kernel panic which I've still not been able to duplicate. I need to return to this real soon.
Ian
Ian Kent
maintainerQuoted 32 lines · Fabian Steiner
Hello!
We are using autofs in order to mount the user's home drive via NFS after a successfull login authenticated by ldap.
/etc/auto.masterlooks like this:# AUOTOFS-MAPPING
/home/schueler /etc/auto.schueler /home/lehrer /etc/auto.lehrer /home/maerkte /etc/auto.maerkte
/etc/auto.schuelerhas the following content (the same also applies for the other files):* -fstype=nfs,rw,hard,intr,nodev,nosuid,exec,acl
server.domain.de:/home/schueler/&Generally speaking this setup works like a charm but from time to time we encounter the following messages in syslog:
Sep 24 16:46:57 server mountd[8818]: authenticated mount request from client.domain.de:559 for /home/schueler/.directory (/home/schueler) Sep 24 16:46:57 server mountd[8818]: can't stat exporteddir
/home/schueler/.directory: No such file or directoryOur investigations show that these messages are probably to be created whenever a user tries to access
/home/schuelerby using Konqueror or Nautilus. The file .directory doesn't exist, however, and that's why these messages appaer. Normalley, this wouldn't be a severe problem but the entire is completely slowed down so that another kind of error occurs:
Quoted 5 lines
Sep 24 16:47:00 server mountd[8818]: refused mount request fromclient.domain.de for
/home/schueler/.directory(/home/schueler): illegal port 48337Does anybody know this issue and could provide any hints how to solve it?
What is the setup in terms of server and client, OS, export options etc. What is the version of autofs and the kernel on the clients?
If your you're happy to allow the use of client ports above 1024 then use the "insecure" export option and see how it goes.
Ian