I am running Coda 5.3.on Red Hat Linux 6.2.  It seems to be installed OK
(after a fair amount of trial and error) and so now I am trying to copy
all my data into the coda store.  I am doing that from the coda server
which is also running venus.  While copying, periodically I will get:

  08:23:22 Cache Overflow: (52, -214828)

I am presuming this is OK, because my venus cache on this machine is
only 20000k, whereas the amount of data I am copying over is much more. 
But then after about five or ten minutes I will get an error about the
device being full (sorry, it had scrolled out of my buffer so I can't
copy it into this email), followed by a message like:

08:23:20 Local inconsistent object at
/coda/programs/distfiles/Windows/fireworks4-TBYB.exe, please check!
...snip...
08:23:38 Cache Overflow: (52, -221652)
cp: preserving permissions for ./dreamweaver4/Dreamweaver
4/Configuration/Objects/Frames/Left Top.gif: No such device
cp: cannot create regular file `./dreamweaver4/Dreamweaver
4/Configuration/Objects/Frames/Left Top.htm': Device not configured
...snip...

The disk is not full, and neither would coda's store be full.  df shows:

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda1              1902904   1563632    242608  87% /
/dev/hdb1              4031900   3047096    779980  80% /usr
/dev/hdb2              4087584   3493232    386712  90% /vicepa
/dev/hdc1              5955545   2172916   3474183  38% /mnt/backup
Coda                     20000 -18446744069414802250 4294768442
22513888% /coda

After I kill the copying process (which is still churning through
"device not configured" lines) the last line changes to:

Coda                   9000000         0   9000000   0% /coda
 
When I try to access the coda mountpoint I get:

  [terminus_at_servalan terminus]$ cd /coda
  bash: /coda: Device not configured

and when I do ls I get:

  ls: /coda: Input/output error

This happens even after I restart venus.  After doing so, venus shows up
as a process, but when I run codacon I get:

  codacon: bind to localhost failed, venus not running?

and when I run clog I get:

  Local login only, could not contact venus

There are no errors in /usr/coda/etc/venus.log, at this stage, however.
In /vice/srv/SrvLog I have lots of messages like this:

  08:27:37 VLDB_Lookup: no more records in VLDB

Interestingly I have another secondary coda server and its venus is
working fine!  I can see the file fireworks4-TBYB.exe (the one that the
copying barfed on) using this other venus.  It is 0 bytes in size.  I
can even delete this file, and that deletion will be reflected on the
main coda server's venus once I (eventually!) get it working again
there.

Even more interestingly it seems to be only when I delete the file on
the other machine that venus finally shuts down on the main server and I
get the following in its venus.log:

[ X(00) : 0000 : 08:39:49 ] E StatsInit()
[ X(00) : 0000 : 08:39:49 ] L StatsInit()
[ X(00) : 0000 : 08:39:49 ] BeginRvmFlush (1, 60, F)
[ X(00) : 0000 : 08:39:49 ] EndRvmFlush
[ X(00) : 0000 : 08:39:49 ] BeginRvmTruncate (1, 220, F)
[ X(00) : 0000 : 08:39:49 ] EndRvmTruncate
[ X(00) : 0000 : 08:39:49 ] fsobj::Recover: invalid fso
(fireworks4-TBYB.exe, (0xffffffff.0xfffffffe.0x2)), attempting to
GC...0x20206b88 : fid = ((0xffffffff.0xfffffffe.0x2)), comp =
fireworks4-TBYB.exe, vol = 20212e88
        state = Normal, stat = { 19373689, 1, 976032000, 99, 0664, 1,
File }, rc rights = 0
        VV = {[ 1 0 0 0 0 0 0 0 ] [ 0x15503ed5 2295 ] [ 0 ]}
        voltype = [1 0 0], fake = 0, fetching = 0 local = 1
        rep = 0, data = 0, owrite = 0, dirty = 1, shadow = 0
        mvstat = Normal
        parent = ((0x0.0x0.0x0), 0), children = 0
        priority = -1 (38422), hoard = [0, -2, 0], lastref = 21234
        mle_bindings = (0, 0), cleanstat = [19373689, 976032000

To finally get coda working again on the main machine, I seem to have to
reboot.  Shutting down and restarting the coda services doesn't cut the
mustard (even if I check with ps that they are all dead.  I also check
if there are any processes still listening on port 370).

This is all intensely annoying.  I have tried to look through the
archives but I can't find anything that really helps.  Can anyone offer
any suggestions?

TIA

-- 
JEREMY MALCOLM <Jeremy@Malcolm.wattle.id.au> http://malcolm.wattle.id.au
Providing online networks of Australian lawyers (http://www.ilaw.com.au)
and Linux experts (http://www.linuxconsultants.com.au) for instant help!
Disclaimer: http://www.terminus.net.au/disclaimer.html. GPG key: finger.