All of lore.kernel.org
 help / color / mirror / Atom feed
From: Filipe Brandenburger <filipe.brandenburger@idilia.com>
To: autofs@linux.kernel.org
Subject: mount: mount point /home/user does not exist
Date: Thu, 02 Jul 2009 17:36:44 -0400	[thread overview]
Message-ID: <4A4D286C.3080401@idilia.com> (raw)

Hello,

I am using autofs-4.1.3-234 on a RHEL 4 machine, using kernel 
2.6.9-78.0.1.ELsmp, getting automount maps from LDAP.

Recently I had failures in some hosts when mounting home directories, in 
some cases more than one host at a time.

I found this on the NFS client's log:

> Jun 30 16:51:21 clnt automount[9458]: >> mount: mount point /home/user does not exist
> Jun 30 16:51:21 clnt automount[9458]: mount(nfs): nfs: mount failure srvr:/export/home/user on /home/user
> Jun 30 16:51:21 clnt automount[9458]: failed to mount /home/user

But on the NFS server, this is all I see:

> Jun 30 16:51:21 srvr rpc.mountd: authenticated mount request from clnt.example.com:731 for /export/home/user (/export/home) 

This is the same log I have when the mount succeeds.

I believe the NFS server might have been overloaded at that time, and 
for that reason the mount request might have taken longer than expected.

 From what I've seen, I believe the ">> mount" message is the message 
returned by the /bin/mount command spawned from automount, and it means 
when it tried to mount the directory, the local /home/user directory was 
no longer there.

I also believe this might have happened because it was previously 
mounted but not used for the timeout period (I am using 5 minutes as 
timeout), so the last mount was expired (and the directory removed) just 
before this /bin/mount process was able to run.

I tried to google for it, but all I found was this message:
http://lkml.indiana.edu/hypermail/linux/kernel/9910.3/1105.html

It looks like the problem I am having, however it is very old, from 
about 10 years ago...

Is this still a known issue in autofs? Is there a patch for it?

I also know that autofs 5 is in many ways different than autofs 4 (I run 
it in my RHEL 5 machines). Now (since RHEL 4.7) I believe autofs 5 is 
available for RHEL 4. Is it possible that upgrading to autofs 5 might 
fix this issue?

Any help trying to figure out what is going on would be very 
appreciated. Also, if you need more logs or for me to execute some 
commands or tests I can do it for sure. I was thinking of a way to 
trying to reproduce this problem (maybe replace /bin/mount with a script 
that does "sleep N" before calling the actual mount) but could not come 
up with something good enough to validate my hypothesis, so I decided to 
ask the list first.

Thanks!
Filipe

             reply	other threads:[~2009-07-02 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 21:36 Filipe Brandenburger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-02 22:26 mount: mount point /home/user does not exist Filipe Brandenburger
2009-07-03  4:38 ` Ian Kent
2009-07-06 14:00   ` Filipe Brandenburger
2009-07-07  1:46     ` Ian Kent
2009-07-09 22:03       ` Steve Linn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A4D286C.3080401@idilia.com \
    --to=filipe.brandenburger@idilia.com \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.