[Bug 40189] Re: autofs needs to be restarted to pick up some shares

[Gergely Katona]

I maintain a 10.04 LTS based cluster of workstations where each node is subject to some stress and need to be restarted once in a while. Autofs maps of nfs shares are communicated via LDAP.  Autofs fails to initialize (or even start in some rare cases)  in its default configuration in about 50% of all boots, making the nodes unusable until autofs is restarted. In addition to this bug  sometimes bind mounts fail to initialize at boot and need a remount. 
After trying out several suggested workarounds unsuccessfully I am using the following not too elegant rc.local script, which  hammers autofs into submission (works 99% of the time). I also advise my users not to restart their computers unless absolutely necessary.

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

sleep 10
service autofs start &
sleep 60
service autofs restart &
sleep 60
service autofs restart &
sleep 60
mount -a


exit 0

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/40189

Title:
  autofs needs to be restarted to pick up some shares

Status in “autofs” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  New

Bug description:
  I am using autofs to access shares on a Windows XP machine from a
  Kubuntu AMD64 machine.  The problems applies in both Breezy and
  Dapper.

  EDIT:  confirmed with similar configuration on Intrepid with a NetApp
  filer hosting NFS.  Server OS removed from summary.

  When I first try to access the mount point via cd or in Konqueror it
  does not exist.  However,  if I then restart autofs
  (/etc/init.d/autofs restart) everythin then works OK.  My config files
  are:

  auto.master

  #
  # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
  #
  # Sample auto.master file
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # For details of the format look at autofs(5).
  #/misc	/etc/auto.misc --timeout=60
  #/misc	/etc/auto.misc
  #/net	/etc/auto.net

  /petunia /etc/petunia.misc --timeout=60

  
  petunia.misc

  #
  # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
  #
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # Details may be found in the autofs(5) manpage

  cd              -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

  tony	-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777	://192.168.1.2/tony
  chris	-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777	://192.168.1.2/chris
  shared	-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777	://192.168.1.2/SharedDocs
  linuxbackups	-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777	://192.168.1.2/linuxbackups

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions