All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Filipe Brandenburger <lists.filbranden@idilia.com>
Cc: autofs@linux.kernel.org
Subject: Re: mount: mount point /home/user does not exist
Date: Fri, 03 Jul 2009 12:38:24 +0800	[thread overview]
Message-ID: <4A4D8B40.9020402@themaw.net> (raw)
In-Reply-To: <4A4D3408.40103@idilia.com>

Filipe Brandenburger wrote:
> 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 does sound a bit like a known problem.
A bunch of patches have gone into RHEL-4 U8 which resolved almost all
reported problems. You will need to log a bug or update to U8 to check.

Ian

  reply	other threads:[~2009-07-03  4:38 UTC|newest]

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

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=4A4D8B40.9020402@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=lists.filbranden@idilia.com \
    /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.