From owner-freebsd-current Sun Aug 1 20:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B258D14D88 for ; Sun, 1 Aug 1999 20:36:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA07214; Sun, 1 Aug 1999 20:19:50 -0700 (PDT) (envelope-from dillon) Date: Sun, 1 Aug 1999 20:19:50 -0700 (PDT) From: Matthew Dillon Message-Id: <199908020319.UAA07214@apollo.backplane.com> To: Martin Blapp Cc: freebsd-current@FreeBSD.ORG Subject: Re: mountpoint locking with fbsd-nfs References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm a little bit astonished that's now possible to mount via nfs :several times at the same mountpoint with freebsd nfs clients: : :normal behaviour (Linux 2.2, Solaris): :-------------------------------------- : :magma:/ # mount magma:/cdrom /mnt :magma:/ # mount magma:/cdrom /mnt :mount: magma:/cdrom already mounted or /mnt busy : :freebsd behaviour (stable and current): :--------------------------------------- : :# mount magma:/cdrom /mnt :# mount magma:/cdrom /mnt :# mount magma:/cdrom /mnt : :#mount :/dev/sd0s2a on / (NFS exported, local, soft-updates, writes: sync 9 async 1508) :/dev/sd0s2e on /var (local, soft-updates, writes: sync 160 async 1695) :procfs on /proc (local) :magma:/cdrom on /mnt :magma:/cdrom on /mnt :magma:/cdrom on /mnt : :I think this is a very strange behaviour ... any ideas ? And as I know :loopback mounts are not possible with fbsd. Am I mistaken ? : :Martin Well, theoretically there is nothing wrong going on since you can mount things on top of an NFS directory. Mount only complains about duplicate normal partition mounts because it can't open the buffered block device the second time. NFS doesn't care how many times a directory is imported or exported. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message