Coda File System

Re: Can' write back files

From: Jan Harkes <>
Date: Fri, 23 Feb 2001 14:45:37 -0500
On Fri, Feb 23, 2001 at 11:10:32AM -0800, Ken McMillan wrote:
> On Fri, 23 Feb 2001, Jan Harkes wrote:
> > Are you authenticated? Use `ctokens' to see whether you have tokens,
> > `clog' to obtain them. This is the most common problem that blocks
> > reintegration.
> > 
> > Jan
> > 
> Thanks for the quick reply. Yes, as my mail indicates, I do have tokens
> (which ctokens confirms). I also thought that the problem might be caused
> by a conflict, but "beginrepair" says "object not in conflict". Also,
> "cfs cs" says "All servers up".

Ahm, didn't notice that, sorry. I would say that the "vnode is not
allocated" could occur when there is a server-server conflict, but that
it kind of hard to get when there is only one server ;)

> Can you give me a clue as to what the "CML entries remaining" message means,

The X CML entries remaining indicates that the client was unable to
sends all updates back to the server. There is possibly an associated
error message in /usr/coda/etc/console. The object/operation that failed
reintegration is the first one in /vice/spool/<uid>/<volumeY>.cml.

Sometimes the kernel is quite persistent in keeping stale directory
contents around, especially if an application is still holding a
reference to a dentry. Try to stop all programs/shells that might be
running with their current working directory somewhere in /coda.

Then walk back up the tree to where you were working, one of the parent
directories might be marked in-conflict, but wasn't expanded because of
those refcounts.

Received on 2001-02-23 14:47:49