[OpenAFS-devel] vos dump busying out the volume while dumping...
Neulinger, Nathan
nneul@umr.edu
Wed, 23 Oct 2002 12:47:32 -0500
I think that if you created it as a clone on the same partition, it
would work fine, but whenever you move the parent volume, or move the
clone, it would cease to be a clone. I don't think anything actually
cares if a clone exists, since it all does CopyOnWrite for all changes.
I figured on a "vos copy volname server part volname server part" with
server and partition defaulting reasonably.
Would be nice if there were some reasonable way to do a "vos merge
server part vol1 vol2" that would recombine a couple of volumes.
Unfortunately, that would likely be a fairly expensive operation, since
it would have to compare every file in a pair of volumes. Without that
though, as soon as you had multiple clones, you couldn't move the
volumes to a different server without using X * quotaused.=20
Adding a "vos copy" routine should be relatively easy to do.=20
-- 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:40 PM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] vos dump busying out the volume=20
> while dumping...
>=20
>=20
> So something like
>=20
> vos move ... -copy <new volume name>
>=20
> which would create a copy on the same or some other server:partition,
> but give it a different name and keep the original around?
> Unfortunately, even if it were on the same server:partition, it
> couldn't just be a clone if you cannot track it in the vldb, right?
>=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