When I check the integrity of my client with rsync, the following
command on the client should not try to copy anything (given SERVER is
the coda server):

    % rsync -vae ssh /coda/ SERVER:/coda/

But I get the following error message:

   ./usr/apache/lib/map_box/RCS/drawerOK.pm,v: No such file or directory

That reveals something is broken somehow. The repair tool doesn't seem
to know about the problem. Trying a repair on either directory or file
leads to

    repair > beginrepair /coda/usr/apache/lib/map_box/RCS/drawerOK.pm,v
    object not in conflict
    repair > beginrepair /coda/usr/apache/lib/map_box/RCS              
    object not in conflict

So I try rsyncing the other direction, from the server to the client:

    % rsync -vae ssh SERVER:/coda/ /coda/  
    receiving file list ... done
    usr/apache/lib/map_box/RCS/drawerOK.pm,v
    rename usr/apache/lib/map_box/RCS/drawerOK.pm,v.a04804 -> 
usr/apache/lib/map_box/RCS/drawerOK.pm,v : Resource temporarily unavailable
    usr/apache/lib/map_box/RCS/


What kind of inconsistency am I facing here? How can I resolve the conflict?

TIA,
-- 
andreas

Reply via email to