We have seen some strangeness with the following sequence (3.4a.patches):
don't touch the read-write volume
add a readonly site on another server
vos release it.
At this point if a user tries to walk down into the volume and their machine
prefers a server (the new one or an old one / never figured it out), they
can not access the volume. In our case it was root.cell... fun fun.
The work-around is to touch a trash file in the volume and release it.
I think it has something to do with volume revision numbers and callbacks.
Of course you can wait a few minutes, delete the trash file, and release the
volume again, if you want to clean up.
Jeff Bartlett
Avant! Corporation
