>Number:         20291
>Category:       bin
>Synopsis:       amd -r tries to remount already mounted filesystems.
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 10 15:51:00 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Adam Prato
>Release:        NetBSD 1.6K - Approxmiately 12/10/02
>Organization:
>Environment:
System: NetBSD shelly.metachar.net 1.6K NetBSD 1.6K (GW-GENERIC) #0: Fri Dec 13 11:28:32 EST 2002 root@luscious:/net/luscious/s0/NetBSD/src/sys/arch/i386/compile/GW-GENERIC i386
Architecture: i386
Machine: i386
>Description:
from amd.conf:
[ /proj ]
map_name =              /etc/amd/proj

from /etc/amd/proj
/defaults       type:=nfs;sublink:="${key}";\
                opts:=rw,hard,grpid,intr,nodevs,nosuid
www             rhost:=shelly;\
                rfs:=${autodir}/${rhost}${path/}-2;fs:=${rfs}

from /etc/rc.conf
amd=YES
amd_flags="-r -l syslog -x error,noinfo,nostats"
amd_dir=/net                    # mount dir

from /etc/fstab
/dev/wd1f /net/shelly/proj-2    ffs     rw,nodev,nosuid                  7 2

Since /net/shelly/proj-2 is already mounted, amd -r is supposed to not try 
to mount the filesystem. When amd is started, it hangs when the filesystem
is referenced. This situation has been confirmed by Kimmo Suominen.

>How-To-Repeat:
See above.
>Fix:
I backed out the amutils binaries to the version supplied in 1.6 release, and
amd is mostly functional, though it froze up once in the past 2 months.
>Release-Note:
>Audit-Trail:
>Unformatted: