On Fri, 2008-06-27 at 10:05 +0200, Carsten Aulbert wrote: > Hi all, > > we have a weird problem here and I fear I need to reboot the box > (painful, many users involved), but maybe there is a way out: > > I'm automounting many nodes and usually everything seems to work nicely. > However, I'm seeing this here right now: > > # ps aux|grep auto.node > root 2022 0.0 0.0 30304 1240 ? Ds Jun19 0:21 > /usr/sbin/automount --pid-file=/var/run/autofs/_atlas_node.pid --timeout=5 > /atlas/node yp auto.node_local > root 11489 0.0 0.0 30516 1108 ? D Jun26 0:00 > /usr/sbin/automount --pid-file=/var/run/autofs/_atlas_node.pid --timeout=5 > /atlas/node yp auto.node_local > root 28610 0.0 0.0 2736 656 pts/31 S+ 10:03 0:00 grep > auto.node > > > As you can see there are two automounter processes in D (or Ds) state sitting > there for the same mount point (the PID-file contains 2022). > > My questions: > > Any idea how this happened?
It's been a long time since I've seen this reported. What distro and kernel? > > Any idea how to get this resolved (possibly without a reboot)? There is nothing you can do if the process is stuck in an uninterruptible state in the kernel. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
