I have Coda set up with a single server and three clients. It is in a state
where files seem not to be getting written back to the server. That is, 
I don't see any reintegration or "backfetches" going on in codacon, and
files written on one machine are not seen on the others. I definitely have
tokens, so that is not the problem. When I try "cfs fr", I get the
message "X CML entries remaining for vulume Y", where X is increasing.
On another machine, I get "Modifications to Y reintegrated to server",
but no files written by this machine appear on other machines, and there
is no apparent writeback activity in codacon.

In the server log, I have the following:

(snip)
18:25:25 File Server started Thu Feb 22 18:25:25 2001

18:26:43 client_GetVenusId: got new host 158.140.90.41:2430
18:26:43 Building callback conn.
18:26:43 No idle WriteBack conns, building new one
18:26:43 Writeback message to 158.140.90.41 port 2430 on conn 2701 succeeded
18:26:43 RevokeWBPermit on conn 2701 returned 0
18:27:08 RevokeWBPermit on conn 2701 returned 0
18:27:08 VGetVnode: vnode 1000002.2274 is not allocated
18:28:11 VGetVnode: vnode 1000002.2274 is not allocated
18:28:57 client_GetVenusId: got new host 158.140.90.33:2430
18:28:57 Building callback conn.
18:28:57 No idle WriteBack conns, building new one
18:28:57 Writeback message to 158.140.90.33 port 2430 on conn 2ea7 succeeded
18:29:04 RevokeWBPermit on conn 2ea7 returned 0
18:29:13 VGetVnode: vnode 1000002.2274 is not allocated
18:30:07 Worker5: Unbinding RPC connection 19373
18:30:15 RevokeWBPermit on conn 2701 returned 0
18:30:15 VGetVnode: vnode 1000002.2274 is not allocated
18:31:18 VGetVnode: vnode 1000002.2274 is not allocated
18:33:00 VGetVnode: vnode 1000002.2274 is not allocated
18:33:21 client_GetVenusId: got new host 139.99.193.241:2430
18:33:21 Building callback conn.
18:33:21 No idle WriteBack conns, building new one
18:33:21 Writeback message to 139.99.193.241 port 2430 on conn 6b5c succeeded
18:34:03 VGetVnode: vnode 1000002.2274 is not allocated
18:35:05 VGetVnode: vnode 1000002.2274 is not allocated
18:36:49 VGetVnode: vnode 1000002.2274 is not allocated
18:38:13 VGetVnode: vnode 1000002.2274 is not allocated

I don't know if any of the above is relevant, but the bit about 
1000002.2274 not being allocated seems suspicious. Shutting down and
restarting the server does not help.

Any clues would be appreciated. Mainly, I would like to get all my file
modifications from the three machines reintegrated, as I have no idea how
long this problem has been going on. 

	Thanks in advance -- Ken McMillan