[OpenAFS] Automatic move of volumes

[anne salemme]

and to add to what derrick says, 'vos release' when there are very large 
volumes involved and RO sites listed at geographically remote sites (ie, 
many thousands of miles away), or when there are many users involved 
(ie, all users of the cell) must be done in a purposeful, coordinated 
way. and just "always keeping the RWs and ROs in sync" simply cannot or 
should not be done.

anne



Derrick Brashear wrote:
>
>
> On 10/24/07, *Steven Jenkins* <steven.jenkins@gmail.com 
> <mailto:steven.jenkins@gmail.com>> wrote:
>
>     On 10/24/07, Kevin Hildebrand <kevin@umd.edu
>     <mailto:kevin@umd.edu>> wrote:
>     >
>     > We've actually had this need a number of times...  Say for instance,
>     > you've installed a new version of software in volume X for testing
>     > purposes, or as Derrick suggests, using the volume as a web backend.
>     >
>     > Then you run out of disk space, have a failing server, etc, and
>     you need
>     > to move the RO replications - there's no easy way to do so without
>     > releasing the volume.
>     >
>
>     I sort of understand this need, but I suggest that it's caused by poor
>     namespace management, and that the solution should be to improve that
>     rather than try to keep your RWs and ROs out of sync with each other. 
>
>
> not everyone has VMS. it has nothing to do with namespace management. 
> nothing is as easy as "vos release" to copy data around.
>
>