From owner-freebsd-current  Sun Oct 20 13:25:33 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA12232
          for current-outgoing; Sun, 20 Oct 1996 13:25:33 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA12227
          for <current@freebsd.org>; Sun, 20 Oct 1996 13:25:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id NAA20723; Sun, 20 Oct 1996 13:26:12 -0700 (PDT)
Message-Id: <199610202026.NAA20723@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: graphix@iastate.edu
cc: current@freebsd.org
Subject: Re: translucent filesystem (was union mounts) 
In-reply-to: Your message of "Sun, 20 Oct 1996 15:13:43 CDT."
             <9610202013.AA22537@spiff.cc.iastate.edu> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 20 Oct 1996 13:26:12 -0700
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>
>>   After searching the mail list archives I have a bad feeling that that
>> translucent filesystems do not work but hoped that perhaps they where
>> fixed in current.
>
>  I have a bad feeling that I spoke too soon...
>
>  After recompiling the world and a kernel from completely new source
>code, the translucent filesystem appears to be working.  Please note
>that I ma using staticly linked version of union and null now however.
>Before I was using the lkm versions of each.  It is possible they where
>out of sync with the kernel I had installed I suppose.

   Out of date LKMs are a sure killer no matter what the filesystem, but both
union and null FS are broken due to interaction problems with the FreeBSD
merged VM/buffer cache. It's a fairly high priority goal to fix this, but it
will require significant changes to these filesystems to fix.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project