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.
With -clone, that doesn't matter, since you don't ever have to keep track of it beyond the single dump process. 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: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 > -----Original Message----- > From: Michael Niksch [mailto:nik@;zurich.ibm.com] > Sent: Wednesday, October 23, 2002 12:32 PM > To: [EMAIL PROTECTED] > Subject: Re: [OpenAFS-devel] vos dump busying out the volume > while dumping... > > > To make the story complete, instead of > > vos dump myvolume -clone > > your scenario would then read > > vos clone myvolume 1 [-server <server>] [-partition <partition>] > vos dump myvolume.clone1 [-server <server>] [-partition <partition>] > vos remove -server <server> -partition <partition> myvolume.clone1 > > A few more lines in a script, but a lot more flexible. > > -- > Michael Niksch /Zurich/IBM @ IBMCH > IBM Zurich Research Laboratory [EMAIL PROTECTED] > 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 > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-devel > _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
