Coda File System

Re: Is Coda Right For Me. (file retrieval behavior)

From: Phil Nelson <>
Date: Wed, 16 Oct 2002 08:36:00 -0700 (PDT)
>the data available to the application as it obtains it. If the network goes
>away venus would have to simply remember that the file in question is
>incomplete and not allow changes to the file until the network was
>available again or the file completely retrieved.

The "problem" here is that once the file has been opened, venus is not
contacted for reads and writes.  All coda kernel modules redirect
reads and writes to the local file system on which the cache file is
stored WITHOUT contacting venus.  This makes reads and writes at local
disk speed.  Any kind of "partial file in cache" would require all
kernel modules to be rewritten to communicate with venus to be able
to verify if a read or write was OK before doing the read or write.

Hoard is the tool of choice here.  It makes sure your cache has the
files in the cache so an open() does not have to wait for your file
to be transferred over the network.  It is already in your cache.


Phil Nelson                       NetBSD:
e-mail:           Coda: 
Received on 2002-10-16 11:41:07