Coda File System

cache expiration / invalidation / something ?

From: Ivan Popov <>
Date: Wed, 31 Mar 2004 13:25:16 +0200 (MEST)

curious about a hardly noticeable but important phenomenon:

a user has got her computer, a Coda client, and uses just that one.
Her home directory is located on Coda.
At login she does one of the following:
 - if the (replicating) servers are available, she runs an explicit clog
(being "failsaved" at '/') and then logs out and in again, normally
 - if the servers are not available - most often they are offline,
intentionally - then she just logs in and can access her files without
problems (as supposed to be)

The client cache is 2.5G and used relatively little, several hundred
megabytes, mostly from another Coda realm (containing all software).
The homedir occupies just a few Mb.

A strangeness is that at some point mozilla refused to start and a
troubleshooting showed that profile data under
~/.mozilla/default/..... was unavalable with "Connection timed out".

Of course, when the servers were brought online and tokens acquired, the
problem disappeared.

My question is - why would Venus ever loose/flush/invalidate the data in
the cache, while it definitely was "produced" locally and still valid?

Received on 2004-03-31 06:31:03