[OpenAFS-devel] vos dump busying out the volume while dumping...

[Neulinger, Nathan]

Biggest problem with the latter is that unless you start creating new
vldb entries with a new volume name, you have no way to keep track of
the clones.=20

With -clone, that doesn't matter, since you don't ever have to keep
track of it beyond the single dump process.=20

Extending the protocol to handle arbitrary numbers of volid's per VLDB
entry might be quite useful, but that's something that requires a lot
more thought and planning to do properly.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Michael Niksch [mailto:nik@zurich.ibm.com]=20
> Sent: Wednesday, October 23, 2002 12:32 PM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] vos dump busying out the volume=20
> while dumping...
>=20
>=20
> To make the story complete, instead of
>=20
>   vos dump myvolume -clone
>=20
> your scenario would then read
>=20
>   vos clone myvolume 1 [-server <server>] [-partition <partition>]
>   vos dump myvolume.clone1 [-server <server>] [-partition <partition>]
>   vos remove -server <server> -partition <partition> myvolume.clone1
>=20
> A few more lines in a script, but a lot more flexible.
>=20
> --=20
> Michael Niksch                     /Zurich/IBM @ IBMCH
> IBM Zurich Research Laboratory     nik@zurich.ibm.com
> Saeumerstrasse 4                   http://www.zurich.ibm.com/~nik/
> CH-8803 Rueschlikon / Switzerland  P: +41-1-724-8913 F: +41-1-724-8080
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20