Your message dated Wed, 28 Dec 2011 00:07:43 +0000
with message-id <e1rfh3x-0002pn...@franck.debian.org>
and subject line Bug#653172: Removed package(s) from unstable
has caused the Debian Bug report #520095,
regarding removes the toplevel mountpoint directories and fails to start the 
next time
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
520095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autofs
Version: 4.1.4+debian-2.1
Severity: grave

When the automount daemon exits, it removes the top-level mountpoint
directory.  For example, when auto.master contains
  /net  /etc/auto/net
and the /net dir exists before startup, on shutdown corresponding 
automount process does right before exit (according to strace):

 unlink("/var/run/autofs/_net.pid")      = 0
 rmdir("/net")                           = 0

So it rmdirs the /net directory which were here before it started.
And sure thing, the next time it does not start anymore, *silently*:

 Starting automounter: done.

yet /net isn't mounted, and there are the following entries in syslog
daemon.log:

 automount[12709]: failed to create iautofs directory /net
 automount[12709]: /net: mount failed!

(even with that, there's no error message -- imagine someone who's
trying to debug the issue and who created that directory just a few
minutes ago -- there's no chance to understand the dir is gone!).

The only solution for me was to do a `chattr +i /net' to stop it
from removing the dir (it still tries but fails).

So there are 3 bugs actually, all at once.

 1) grave bug - removing the toplevel dirs -- something it sholdn't do
   in the first place

 2) should say something when failed to mount the thing, insteas of just
   "done.".  For that to work, daemon should wait in parent process 
   while the chile finishes initialization and report status back.
   Given the 1) above, it's not a wishlist anymore

 3) no real error messages (errno) in syslog

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing'), (50, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.28-i686smp (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages autofs depends on:
ii  libc6                         2.7-18     GNU C Library: Shared libraries
ii  ucf                           3.0016     Update Configuration File: preserv

Versions of packages autofs recommends:
ii  module-init-tools           3.4-1        tools for managing Linux kernel mo
ii  nfs-common                  1:1.1.4-1tls NFS support files common to client

autofs suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 4.1.4+debian-3+rm

Dear submitter,

as the package autofs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/653172

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)


--- End Message ---

Reply via email to