Coda File System

Re: coda does not replicate

From: Ivan Popov <pin_at_math.chalmers.se>
Date: Sat, 31 May 2003 23:03:48 +0200 (MET DST)
Hello Markus,

> > do you mean that replication did work before?
>
> yes, it worked very well and fast :-)

you make me uncertain, how do you define "speed of replication"?

> ok the details:
>
> 1 non-scm(ds10)  1 scm(ds11)
>
> [files]
> 	/vice/db/servers
> 	ds11            11
> 	ds10            10
>
> 	/vice/db/vicetab
> 	ds11   /vicepa   ftree   width=256,depth=3
> 	ds10   /vicepa   ftree   width=256,depth=3
>
> 	/vice/db/VSGDB
> 	E0000100 ds11
> 	E0000102 ds10
> 	E0000104 ds11 ds10
>
> 	/etc/hosts
> 	192.168.0.160	ds10
> 	192.168.0.161	ds11
>
> have created with volrep the last volume E0000104.

Do you mean createvol_rep?

> all was fine. venus has mounted the volume under /coda and had touched some
> files in it. after the touches coda was able to replicate them to the other
> servers. was great :-)

How did you check that the changes are propagated to both servers?

> 16:31:47 VAttachVolumeById: vol b000001 (codaclient.0) attached and online
> 16:31:47 VAttachVolumeById: vol b000002 (codaclient.0) attached and online

> 16:33:40 VAttachVolumeById: vol a000001 (codaclient.1) attached and online
> 16:33:40 VAttachVolumeById: vol a000002 (codaroot.1) attached and online
> 16:33:40 VAttachVolumeById: vol a000003 (codaclient.1) attached and online

Huh, looks like you managed to create two volumes with the same name?

In such situation I would probably begin from the beginning, recreating
the servers from scratch (and documenting my command history).

> thx and i hope you can help me :-)

Unfortunately this advice is about all I can help with.

Best regards,
--
Ivan
Received on 2003-05-31 17:06:03