All of lore.kernel.org
 help / color / mirror / Atom feed
* Indirect multi-mount map sometimes needs client reboot after update
@ 2010-05-21 20:12 Andrew Klaassen
  2010-05-24  1:36 ` Ian Kent
  0 siblings, 1 reply; 2+ messages in thread
From: Andrew Klaassen @ 2010-05-21 20:12 UTC (permalink / raw)
  To: autofs

I've got indirect multi-mount and single-mount maps set up in NIS like so:

auto.master:

/test auto.test --ghost

auto.test:

foo /    -tcp,intr server1:/foo \
    /bar -tcp,intr server2:/bar
abc      -tcp,intr server1:/abc

Changes to single-mount maps are picked up immediately by clients.

Changes to multi-mount maps are picked up:

1. Immediately if nothing under the key is currently mounted.

2. Only after an autofs restart - or sometimes even a reboot - after anything has been mounted under the key.

Is it possible to make #2 go away?  Having to reboot every single one of hundreds of client machines after a single change is a downer.

I'm running Centos 5.2 to 5.4 with autofs-5.0.1-0.rc2.88 to autofs-5.0.1-0.rc2.143.

Thanks.

Andrew

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Indirect multi-mount map sometimes needs client reboot after update
  2010-05-21 20:12 Indirect multi-mount map sometimes needs client reboot after update Andrew Klaassen
@ 2010-05-24  1:36 ` Ian Kent
  0 siblings, 0 replies; 2+ messages in thread
From: Ian Kent @ 2010-05-24  1:36 UTC (permalink / raw)
  To: Andrew Klaassen; +Cc: autofs

On Fri, 2010-05-21 at 13:12 -0700, Andrew Klaassen wrote:
> I've got indirect multi-mount and single-mount maps set up in NIS like
> so:
> 
> auto.master:
> 
> /test auto.test --ghost
> 
> auto.test:
> 
> foo /    -tcp,intr server1:/foo \
>     /bar -tcp,intr server2:/bar
> abc      -tcp,intr server1:/abc
> 
> Changes to single-mount maps are picked up immediately by clients.
> 
> Changes to multi-mount maps are picked up:
> 
> 1. Immediately if nothing under the key is currently mounted.
> 
> 2. Only after an autofs restart - or sometimes even a reboot - after
> anything has been mounted under the key.
> 
> Is it possible to make #2 go away?  Having to reboot every single one
> of hundreds of client machines after a single change is a downer.

These multi-mount map entry keys should be updated, if they have
changed, after all the dependent mounts in the tree have been umounted.
They can't be updated while subordinate mounts are active because the
information about the mount tree (and dependencies within the tree) is
used during operation.

Are you sure the mount tree goes away and isn't updated at the next
mount?

Ian

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-05-24  1:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-21 20:12 Indirect multi-mount map sometimes needs client reboot after update Andrew Klaassen
2010-05-24  1:36 ` Ian Kent

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.