From owner-freebsd-bugs  Thu Nov 20 01:00:05 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA22462
          for bugs-outgoing; Thu, 20 Nov 1997 01:00:05 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA22439;
          Thu, 20 Nov 1997 01:00:01 -0800 (PST)
          (envelope-from gnats)
Date: Thu, 20 Nov 1997 01:00:01 -0800 (PST)
Message-Id: <199711200900.BAA22439@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: j@uriah.heep.sax.de (J Wunsch)
Subject: Re: bin/5100: Repeated nfs mounts succeed, creating multiple instances in 'df' ; umount -ft nfs doesn't succeed if network is down
Reply-To: j@uriah.heep.sax.de (J Wunsch)
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/5100; it has been noted by GNATS.

From: j@uriah.heep.sax.de (J Wunsch)
To: mburgett@awen.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/5100: Repeated nfs mounts succeed, creating multiple instances in 'df' ; umount -ft nfs doesn't succeed if network is down
Date: Thu, 20 Nov 1997 09:46:55 +0100

 As mburgett@awen.com wrote:
 
 > ... Shouldn't mount_nfs be
 > returning an error if the requested mount is aready in place (like
 > mounting local filesystems do) and refuse to create the second entry in
 > the table?
 
 No, all 4.4BSD mounts can be stacked on the same mountpoint.  UFS
 mounts only don't succeed in this since the resource (partition) is
 busy, and cannot be mounted again anywhere else.  This is not the case
 for MFS mounts, or mounts of other (non-device) resources.
 
 mount -a should, however, be modified to not blindly mount something
 that's already mounted.  This is indeed a bug.  I'm not sure whether
 there's already an existing PR for it, but i think so.  You apparently
 didn't bother to check the open PRs either, did you? :-)
 
 > Conversely, umount -ft nfs won't succeed if the network is down ( error
 > returned is 'nfs send error 50' ) if the network is down.
 
 There's an open PR for it.  Our NFS maintainer is, unfortunately, out
 to lunch.
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)