From owner-freebsd-fs Tue Oct 9 12:48: 2 2001 Delivered-To: freebsd-fs@freebsd.org Received: from localnet.sh (www.localnet.sh [216.40.195.67]) by hub.freebsd.org (Postfix) with ESMTP id 23C8A37B406 for ; Tue, 9 Oct 2001 12:47:59 -0700 (PDT) Received: (from offe@localhost) by localnet.sh (8.10.2/8.10.2) id f99JisY18618; Tue, 9 Oct 2001 14:44:54 -0500 Date: Tue, 9 Oct 2001 14:44:54 -0500 From: Olof Johansson Message-Id: <200110091944.f99JisY18618@localnet.sh> To: tlambert2@mindspring.com Cc: freebsd-fs@freebsd.org Subject: Re: NFS sharing an NFS Mount In-Reply-To: <3BC3511C.736F595A@mindspring.com> References: <20011008231240.99429505@stiggy.masaclaw.co.nz> <3BC3511C.736F595A@mindspring.com> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In muc.lists.freebsd.fs, you wrote: >Tom Peck wrote: >> Is it possible to nfs share a mount that has been mounted using nfs? > >Not without violating safety guarantees in the protocol as >regars not returning writes until they have been committed >to stable storage. Not entirely true. NFS version 3 has the option of unstable writes, which are usually used by the ONC+-derived clients (Solaris, AIX, ...). On the other hand, then the commit calls must not return until the data is on stable storage. Also, one could technically write a NFS gateway that simply relays the RPC calls and makes sure they are not returned to the "real" client until a reply has been received from the server. However, I am not aware of any such gateway in existance. Regards, Olof To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message