According to Jan Harkes:
>
>Partial caching just won't work if you want to have any guarantees on
>consistency, just look at the mess AFS3 made of it.
>
Well, there may be a way around having to write back an entire large
file (I may be making some invalid assumptions about the Coda protocol
here
Hi!
On Tue, 9 Oct 2001 15:30:14 -0400
Jan Harkes <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 09, 2001 at 11:53:09AM +0200, Ren? Rebe wrote:
[...]
> It will be extremely fast when they are already in the cache. How do you
> expect work with a file while disconnected from the network if you only
>
On Tue, Oct 09, 2001 at 11:53:09AM +0200, Ren? Rebe wrote:
> As alternative I find CODA quite promissing. But I found problems reading
> through the docu.
>
> The introduction about coda says:
> ..., Venus fetches the entire file from the servers, ...
>
> Err? I have some multi-track wave files
I have a similar question to yours... I set Coda with a cache of 20MB
(manual tells me to do that during tests), but when I copy files of
80-100MB, I get cache errors... and df reports that /coda is only 20MB
big altogether. So when I copy a big file, it says there's a negative
free space left on
