Coda File System

Re: okay, what am I doing wrong?

From: Stephen J. Turnbull <>
Date: Fri, 10 Jan 2003 14:24:45 +0900
>>>>> "Rod" == Rod Van Meter <> writes:

On Thu, 2003-01-09 at 14:08, ext Jan Harkes wrote:

    >> So the laptop is disconnnected, and probably has a conflict
    >> that is blocking reintegration.

> > [root_at_localhost rdv]# 16:10:37 Checkpointing developers:rdv
> > 16:10:37 to /usr/coda/spool/500/developers_rdv@_coda_rdv.tar
> > 16:10:37 and /usr/coda/spool/500/developers_rdv@_coda_rdv.cml
> > 16:10:37 Reintegrate: developers:rdv, 100/114 records, result = Unknown
> > error 198

    >> Not sure what 198 is, but reintegration failed. The first entry
    >> in /usr/coda/spool/500/developers_rdv@_coda_rdv.cml should be
    >> the operation that is causing the problem.

I'm seeing this, too, with CVS workspaces in coda (CVS server is
remote).  (All of Rod's description applies except for the details of
file naming, including a few files with spaces in the name.  I don't
think there are any commas.)  I sent you a coda log a week ago or so
which probably has this problem in it.  Didn't you get it?

BTW, things have stabilized substantially with an upgrade from Linux
kernel 2.2.18 (and the coda module distributed with that kernel) and
kernel 2.4.20.  But I'm still seeing error 198s and even venus crashes.

    >> No conflicts in the codaroot volume, but developers:rdv seems
    >> to be the problematic one. You can try to search for it with,

    >> find /coda/rdv -lname '@*'

    Rod> Returns nothing.

Yup, me too.

Sometimes the symlink shows up later, after restarting Venus.  Other
times I have to venus -init to get anywhere.

Institute of Policy and Planning Sciences
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.
Received on 2003-01-10 00:27:20