Coda File System

dirty shutdown - what now?

From: Mathias Koerber <>
Date: Tue, 21 Oct 2003 08:44:33 +0800

I am currently testing Coda (5.3.20, could not get 6.0.2 to work
at all!)

yesterday on one of my clients I had a venus crash and on restart I get:

Date: Tue 10/21/2003

08:28:59 /usr/coda/LOG size is 1065472 bytes
08:28:59 /usr/coda/DATA size is 4255928 bytes
08:28:59 Loading RVM data
08:28:59 Last init was Mon Oct 20 10:56:54 2003
08:28:59 Last shutdown was dirty
08:28:59 starting VDB scan
08:28:59        3 volume replicas
08:28:59        2 replicated volumes
08:28:59        2 CML entries allocated
08:28:59        0 CML entries on free-list
08:28:59 starting FSDB scan (1666, 40000) (25, 75, 4)
08:28:59        9 cache files in table (0 blocks)
08:28:59        1657 cache files on free-list
08:28:59 starting HDB scan
08:28:59        0 hdb entries in table
08:28:59        0 hdb entries on free-list
08:28:59 Getting Root Volume information...
08:28:59 Reintegrate SHARE pending tokens for uid = 0
08:28:59 fatal error -- volent::~volent: CML not empty
08:28:59 RecovTerminate: dirty shutdown (1 uncommitted transactions)

what to do in such a case?

a venus -init will lose all changes made on that client

I tried repair, but it always claims the object I name is not
in conflict and refuses to start.

I find the repair documentation very sketchy at best.

a few questions:

1. after doing a 'cfs beginrepair' do I have to say beginrepair again in the
repair tool?
2. what to do if repair claims neither the directory nor the individual 
in them are in conflict? (but I know they are. In my case a renamed file 
did not
get renamed on the server)
3. Is there a complete/good documentation for repair?


Mathias Körber

Lightspeed Technologies
Received on 2003-10-20 20:51:31