From owner-freebsd-current Tue Oct 26 1: 5:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id 971241531B for ; Tue, 26 Oct 1999 01:05:17 -0700 (PDT) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id MAA38461; Tue, 26 Oct 1999 12:04:31 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id MAA02726; Tue, 26 Oct 1999 12:10:57 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Message-Id: <199910260810.MAA02726@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG From: Dmitrij Tejblum Subject: Re: freefall hangs w/ nfs In-reply-to: Your message of "Mon, 25 Oct 1999 10:26:04 PDT." <199910251726.KAA07728@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Oct 1999 12:10:57 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Actually, what I meant was that AMD itself is equivalent to a loopback > mount, whether or not you make loopback mounts through it. No. The loopback deadlock happen when the nfs server handle a write operation. But there cannot be any writes in the amd filesystem. The filesystem only contains symlinks to outside. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message