From owner-freebsd-questions Wed Jan 26 18:16: 2 2000 Delivered-To: freebsd-questions@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 07B701543B for ; Wed, 26 Jan 2000 18:15:59 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id SAA19935 for ; Wed, 26 Jan 2000 18:15:56 -0800 (PST) To: freebsd-questions@freebsd.org Subject: NFS oddity -- Bug or feature? Date: Wed, 26 Jan 2000 18:15:56 -0800 Message-ID: <19933.948939356@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excuse my abundant ignorance, but is this a bug or a feature? I just accidently issued a `mount' for a remote NFS volume that, as it turns out, was already mounted. Now, doing `df' I see: ------------------------------------------------------------- Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 4185117 2254686 1595622 59% / procfs 4 4 0 100% /proc coredump:/home 13964232 10623202 2614894 80% /c coredump:/home 13964232 10623202 2614894 80% /c Gee! Maybe this is a feature! Lemme see... I can now access that volume on the local system as either /c or.... ah... /c Color me puzzled. Humm... well at least `umount' seems to do the Right Thing. Doing `umount /c' once got me back to only having one /c mounted, and doing it again got be back to having zero /c's mounted. I guess that I can't complain about any lack of symmetry here. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message