All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Summers <jsummers@bachman.cs.ou.edu>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: AutoFS5
Date: Wed, 15 Aug 2007 08:48:48 -0500	[thread overview]
Message-ID: <46C30440.6040808@cs.ou.edu> (raw)
In-Reply-To: <1187155104.3249.14.camel@raven.themaw.net>

Ian Kent wrote:
> On Tue, 2007-08-14 at 15:39 -0500, Jim Summers wrote:
>> 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?
> 
> It's a mount option.
> Check your nfs-utils. I believe that revision 14 and above will
> understand the "nosharecache" option.
> 
> Add this as a global option by changing:
> 
> #OPTIONS=""
> 
> to
> 
> OPTIONS="-O nosharecache"
> 
> in /etc/sysconfig/autofs, near the bottom and let us know if this helps.
> 

seems to have resolved the problem.  i added the nosharecache option and 
restarted the daemon.  then was able to su to the affected and unaffected 
accounts and get the mounts.

the really cool thing was, i was able to do, "/etc/init.d/autofs restart" 
while a couple of users were logged in and it actually restarted.  I was not 
able to do that with autofs4, it would pretty much hang.

i will monitor it for a few days to verify all is well.

many thanks





> Ian
> 

-- 
Jim Summers
School of Computer Science-University of Oklahoma
-------------------------------------------------

  parent reply	other threads:[~2007-08-15 13:48 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     ` AutoFS5 Jim Summers
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         ` Jim Summers [this message]
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=46C30440.6040808@cs.ou.edu \
    --to=jsummers@bachman.cs.ou.edu \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.net \
    /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.