[OpenAFS] Automatic move of volumes
Derrick Brashear
shadow@gmail.com
Wed, 24 Oct 2007 10:30:12 -0400
------=_Part_5206_29042462.1193236212495
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 10/24/07, Steven Jenkins <steven.jenkins@gmail.com> wrote:
>
> On 10/24/07, Kevin Hildebrand <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.
------=_Part_5206_29042462.1193236212495
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div><span class="gmail_quote">On 10/24/07, <b class="gmail_sendername">Steven Jenkins</b> <<a href="mailto:steven.jenkins@gmail.com">steven.jenkins@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 10/24/07, Kevin Hildebrand <<a href="mailto:kevin@umd.edu">kevin@umd.edu</a>> wrote:<br>><br>> We've actually had this need a number of times... Say for instance,<br>> you've installed a new version of software in volume X for testing
<br>> purposes, or as Derrick suggests, using the volume as a web backend.<br>><br>> Then you run out of disk space, have a failing server, etc, and you need<br>> to move the RO replications - there's no easy way to do so without
<br>> releasing the volume.<br>><br><br>I sort of understand this need, but I suggest that it's caused by poor<br>namespace management, and that the solution should be to improve that<br>rather than try to keep your RWs and ROs out of sync with each other.
</blockquote><div><br>not everyone has VMS. it has nothing to do with namespace management. nothing is as easy as "vos release" to copy data around.<br></div><br></div><br>
------=_Part_5206_29042462.1193236212495--