All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Summers <jsummers@bachman.cs.ou.edu>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: autofs@linux.kernel.org
Subject: Re: AutoFS5
Date: Tue, 14 Aug 2007 15:39:22 -0500	[thread overview]
Message-ID: <46C212FA.7030201@cs.ou.edu> (raw)
In-Reply-To: <x49vebh98nd.fsf@segfault.boston.devel.redhat.com>

Jeff Moyer wrote:
> Jeff Moyer <jmoyer@redhat.com> writes:
> 
>> Jim Summers <jsummers@bachman.cs.ou.edu> writes:
>>
>>> Hello All,
>>>
>>> Just hit a hiccup with autofs5.  Everything was going along fine and then had 
>>> a user call and say they could not get their home on a machine.  I did some 
>>> quick checking and some mounts were working and others not.  below is a bit of 
>>> the debug log and some other info.  the user, gerardo is the one who called 
>>> me.  entries in the debug log for him are the same as the tmac user.  in that 
>>> it get his ldap info tries to mount but then says it is already mounted and 
>>> then fails????
>>>
>>> client machine is FC6 hand compiled autofs version:
>>> autofs-5.0.1-20
>>> autofs-debuginfo-5.0.1-20
>>> with a patch from Ian.
>> What is the kernel version on the client?

2.6.22.1-32.fc6

> 
> I'm guessing that you have 2.6.22.1-13.fc6 or later installed.  These
> kernels include the "nosharecache" patch for NFS.  This patch can
> cause some mounts to fail with -EBUSY.  You can revert the
> nosharecache patch to get the old behaviour back.

is this accomplished with boot option similar to 'noacpi' or something like that?

> 
> Could you let us know what nfs mount options are used for your maps,
> though, as this should only bite you if you try to mount from the same
> server file system with different sets of mount options.  In other
> words, your first mount from the server should succeed, successive
> mount attempts of the same file system with differring options will
> fail.

options:

amarak:
-rw,rsize=4096,wsize=4096
here is tmac:
  -rw,actimeo=60,rsize=32768,wsize=32768,nocto
here is gerardo:
-rw,rsize=8192,wsize=8192
here is granville:
-rw,rsize=4096,wsize=4096
jsummers:
-rw,actimeo=60,rsize=32768,wsize=32768,nocto

some results:
[root@saturn ~]# su - jsummers
[jsummers@saturn ~]$ exit
logout
[root@saturn ~]# su - tmac
su: warning: cannot change directory to /home/tmac: No such file or directory
-bash-3.1$ exit
logout
[root@saturn ~]# su - granville
saturn@~> logout
[root@saturn ~]# su - amarack
saturn@~> logout
[root@saturn ~]# su - gerardo
su: warning: cannot change directory to /home/gerardo: No such file or directory
-bash-3.1$ logout

weird, huh?

thanks again

> 
> -Jeff
> 
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs

  reply	other threads:[~2007-08-14 20:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 19:19 AutoFS5 Jim Summers
2007-08-14 19:35 ` AutoFS5 Jim Summers
2007-08-14 19:37 ` AutoFS5 Jeff Moyer
2007-08-14 20:13   ` AutoFS5 Jeff Moyer
2007-08-14 20:39     ` Jim Summers [this message]
2007-08-14 20:48       ` AutoFS5 Jeff Moyer
2007-08-15  5:18       ` AutoFS5 Ian Kent
2007-08-15  5:31         ` AutoFS5 Ian Kent
2007-08-15 13:48         ` AutoFS5 Jim Summers
2007-08-15 14:14           ` AutoFS5 Ian Kent

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=46C212FA.7030201@cs.ou.edu \
    --to=jsummers@bachman.cs.ou.edu \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.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.