I'm running -current from around 5/10 on FreeBSD 4.5ish.

I have just had two 'local inconsistent object' problems.
I am 'cfs wd -age 30', and connected over a 56K modem.
I am editing a file with emacs 20.7.
emacs is creating autosave files, and also the usual symlink locks.

emacs failed to autosave, and I noticed in the codacon a local
inconsistent object:

Remove .#actions.txt ( 11:42:00 )
Symlink gdt_at_gdt.ir.bbn.com.304:1022240098 ( 11:42:01 )
connection::bandwidth claude.ir.bbn.com 585 722 943 ( 11:42:01 )
COP2 u.gdt ( 11:42:14 )
connection::bandwidth claude.ir.bbn.com 594 713 891 ( 11:42:19 )
reintegrate::u.gdt, 2/2 ( 11:42:44 )
Reintegrate u.gdt, (2, 200) ( 11:42:44 )
BackFetch claude.ir.bbn.com, actions.txt [5] ( 11:42:45 )
connection::bandwidth claude.ir.bbn.com 655 821 1099 ( 11:42:47 )
COP2 u.gdt ( 11:42:47 )
reintegrate::u.gdt, 0/0 ( 11:42:47 )
connection::bandwidth claude.ir.bbn.com 672 812 1027 ( 11:42:49 )
reintegrate::u.gdt, 2/2 ( 11:44:18 )
Reintegrate u.gdt, (2, 228) ( 11:44:18 )
Local inconsistent object at /coda/home/gdt/QUIST/REVIEW-COMMENTS/SDP,
please ch
eck! ( 11:44:18 )
reintegrate::u.gdt, 0/2 ( 11:44:18 )
connection::bandwidth claude.ir.bbn.com 692 826 1025 ( 11:44:23 )
GetAttr project ( 11:45:02 )
GetAttr scratch ( 11:45:02 )
connection::bandwidth claude.ir.bbn.com 727 817 933 ( 11:45:07 )
Local inconsistent object at /coda/home/gdt/QUIST/REVIEW-COMMENTS/SDP,
please ch
eck! ( 11:47:20 )

So the whole directory has gone inconsistent.  I think this is due to
trying to remove a symlink that someone never made it to the server,
or perhaps made it wrong: the server has

lrwxr-xr-x  1 gdt  nobody    13 May 24 11:17 gdt_at_gdt.ir.bbn.com.304:1022240098 -> .#actions.txt

when it should have

lrwxr-xr-x  1 gdt  nobody    33 May 24 11:43 .#actions.txt -> gdt_at_gdt.ir.bbn.com.304:1022240098


The server (singly-replicated volume) had:
11:44:18 CheckSymlinkSemantics: gdt_at_gdt.ir.bbn.com.304:1022240098 already exists in (0x1000002.0x3611.0x73af)

So I am wondering if reintegration of symlinks is broken/backwards
somehow.

Also, I think it is horribly broken that such objects prevent venus
from restarting; this tends to make me blow my cache, and this
combined with the lack of a dump/restore for the cache means a very
long time on a modem to re-hoard.  Sorry I can't be more helpful and
fix the bug instead of complaining, but I haven't found the time to
really dig in to venus.  IMHO fixing reliability issues like this is
really important for Coda to be taken seriously (along with security
and multiple cell support, of course....).