Followup;
Now on the RO server this volume cannot be access at all
service
RWrite: 536870924 ROnly: 536870925 RClone: 536870925
number of sites -> 2
server corvus.umbralservices.com partition /vicepa RW Site -- New release
server raven.umbralservices.com partition /vicepa RO Site -- Old release
corvus:/afs/umbralservices# cd service corvus:/afs/umbralservices/service#
raven:/afs/umbralservices# cd service -bash: cd: service: Connection timed out
Still exact same error on trying to vos release manually
What sort of replication is there automatically? or are we expected to write crontabs for vos release at regular intervals?
Regards Eric
Eric Bennett wrote:
Hi guys,
I'm having some problem with volume replication, can't figure out why, but here's the skinny;
raven:/var/log/openafs# vos release service -verbose
service
RWrite: 536870924
number of sites -> 2
server 216.32.65.66 partition /vicepa RW Site -- New release
server raven.umbralservices.com partition /vicepa RO Site -- Old release
This is a complete release of volume 536870924
Cloning RW volume 0 to temporary RO... done
Getting status of RW volume 536870925... done
Ending cloning transaction on RW volume 536870925... done
Starting transaction on cloned volume 536870925... done
Creating new volume 536870925 on replication site raven.umbralservices.com: done
Starting ForwardMulti from 536870925 to 536870925 on raven.umbralservices.com (full release).
Release failed: VOLSER: Problems encountered in doing the dump !
Could not end transaction on a ro volume: : No such file or directory
The volume 536870924 could not be released to the following 1 sites:
raven.umbralservices.com /vicepa
VOLSER: release could not be completed
Error in vos release command.
VOLSER: release could not be completed
Plenty of room in /vicepa on the destination server.
Regards Eric
smime.p7s
Description: S/MIME Cryptographic Signature
