bin/38103: automounter (amd) failed to unmount busy filesystems on reboot - reboot will hang

[Wolfgang.Stukenbrock%nagler-company.com@localhost]

>Number:         38103
>Category:       bin
>Synopsis:       automounter (amd) failed to unmount busy filesystems on reboot 
>- reboot will hang
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 25 15:05:00 +0000 2008
>Originator:     Wolfgang Stukenbrock
>Release:        NetBSD 4.0
>Organization:
Dr. Nagler & Company GmbH
        
>Environment:
        
        
System: NetBSD s010 4.0 NetBSD 4.0 (NSW-S010) #16: Wed Feb 20 12:51:34 CET 2008 
wgstuken@s012:/export/NetBSD-4.0/N+C-build/.OBJDIR_amd64/export/NetBSD-4.0/src/sys/arch/amd64/compile/NSW-S010
 amd64
Architecture: x86_64
Machine: amd64
>Description:
        On reboot the automounter amd fails to unmount busy filesystems and 
does not terminate.
        The rc-script will wait for an infinite time for amd to quit, but this 
will not happen - at least not
        within 30 minutes ...  You must kill the automounter by hand to reboot 
the system.
        The problem is, that if the home directory is mounted via amd, than 
only one user needs to be logged in in order
        to hangup the reboot.
        This problem is new in 4.0. We've had had no problems with that in 3.1.
>How-To-Repeat:
        Start amd, login as a second user and chdir to a remote filesystem 
mounted via amd.
        Then try to reboot the machine with "shutdown -r now".
        The reboot will start and wait for an infinite time for amd to quit.
>Fix:
        Not known up to now.
        Perhaps a timeout in the rc-scripts may be usefull.
        Perhaps this is a new bug in amd that needs to be fixed.
        As workaround you can edit the amd rc-script to send SIGTERM, wait 10 
seconds and than continue with
        normal processing with termination signal set to SIGQUIT.

>Unformatted: