From owner-freebsd-stable@FreeBSD.ORG Fri Jan 14 16:28:48 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C31516A4CE for ; Fri, 14 Jan 2005 16:28:48 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ED5F43D4C for ; Fri, 14 Jan 2005 16:28:48 +0000 (GMT) (envelope-from bjmccann@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so510470wri for ; Fri, 14 Jan 2005 08:28:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=LpDDcJ9Y0wQIrEXc1oO+gXFo1Pqnx3brr419KiNAQNu9TNUYAbg+qKHeIK/XS7Vp6wSPRkoWIxyMf5b/3NIC1YCqA9a6j6BuzuCyM8pruYDAl/xztzGLL8sT6cTSbimlJJ3XYHCSz3noZuF7dk9kIzD8/ZDGzA/lptbYX87rGZM= Received: by 10.54.41.78 with SMTP id o78mr62253wro; Fri, 14 Jan 2005 08:28:47 -0800 (PST) Received: by 10.54.33.61 with HTTP; Fri, 14 Jan 2005 08:28:47 -0800 (PST) Message-ID: <2b5f066d05011408282ec9c908@mail.gmail.com> Date: Fri, 14 Jan 2005 11:28:47 -0500 From: Brian McCann To: Holger Kipp In-Reply-To: <20050114152159.GA10608@intserv.int1.b.intern> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <2b5f066d050114070172ac895f@mail.gmail.com> <20050114152159.GA10608@intserv.int1.b.intern> cc: freebsd-stable@freebsd.org Subject: Re: ggatec & ggated question/issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Brian McCann List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 16:28:48 -0000 That's exactly what's happening. I put ggatec and ggated into verbose mode, and tried the same thing. When I cat the file, there appears to be nothing going on in the logs for either ggatec or ggated (or even when I do an ls for that matter). This is definitely different then what I expected, as I thought ggated just exported a raw block device, ggatec creates the "other end" of the mount and a dev node to point to the "tunnel", and mount then would just go accross the tunnel. Thinking the mount was RO and mounted async I thought would get rid of any buffering at the client side. Yes, this is cool none the less, and a huge advancement, but there's got to be a way to have it not buffer and actively read from the virtual-block device on the client to the server. Maybe I just missed something in the man page...guess I'll try reading it again. Thanks! --Brian On Fri, 14 Jan 2005 16:21:59 +0100, Holger Kipp wrote: > On Fri, Jan 14, 2005 at 10:01:10AM -0500, Brian McCann wrote: > > #echo "foo" > /share/bar > > > > Then mounting the client, I see the file. Now I delete the file on > > the server, I can still cat the file on the client. It's like the > > client can still read the old superblock or something. Any ideas on > > why this is doing this, or how to make it work so the client sees what > > the server sees? > > Looking at http://kerneltrap.org/node/3104 should explain this. My > current idea (IANAKH) would be that the client is caching the directory > and file data and is not notified that anything has changed on disk, so > there is no reason to refresh the cached data from disk. > > The behaviour sounds similar to two FreeBSD-Systems accessing the same disk > device via SCSI (without synchronizing disk access). > > Regards, > Holger Kipp >