On Tue, Dec 10, 2002 at 10:32:35PM -0800, Michael Loftis wrote:
> Not even sure how I ended up with inconsistencies but I did (I've only got 
> one client and one server so...)  Anyway on the client I attempt to doa 
> repair, and get the following output:
> 
> repair > beginrepair
> Pathname of object in conflict? []: /coda/click/click-1.2.4/conf
> VIOCGETVOLSTAT /coda/click/click-1.2.4/conf/global failed
> Could not allocate replica list
> beginrepair failed.
> repair >
> 
> I have a feeling this has to do with the fact that I'm running 
> write-disconnect (cfs wd) and none of the click/* directory actually exists 
> yet on the server.

In that case it is also likely that your shell is preventing us from
turning the /coda/click/click-1.2.4/ directory into a dangling symlink
and you aren't really looking at the conflict that needs to be repaired.

Whenever I hit a conflict and have repair problems, I tend to exit all
shells and programs that are likely to be somewhere in the volume with
the conflict. Then, I 'cd' to /coda, do 'ls', and repeat until I see a
dangling symlink.

Repair only works when you are connected to the servers, but even when
write-disconnected you should be able to see objects on the server.

Jan