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

Neulinger, Nathan nneul@umr.edu
Wed, 23 Oct 2002 13:12:33 -0500


I'm not sure it's a reference count for the vnode, I think it would be
for the underlying inode on the server vice partition, but I'll admit,
I'm not that up on the real low level internals. Maybe one of the core
developers has some input here.=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 1:02 PM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] vos dump busying out the volume=20
> while dumping...
>=20
>=20
> > 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,=20
> or move the
> > clone, it would cease to be a clone.  I don't think=20
> anything actually
> > cares if a clone exists, since it all does CopyOnWrite for all
> > changes.
>=20
> So would it be possible to do perform 'vos backup' and 'vos
> addsite,release' on such a differently named clone and end up with 5
> clones of the same clone (plus any dynamic clones during 'vos move' or
> 'vos copy'). Would it be possible to perform multiple 'vos copy' and
> end up with an essentially unlimited number of clones? I guess there
> must be something like a reference count for a vnode that can=20
> overflow,
> at which point it will look as if it were zero and make your data
> disappear altogether. At which number of clones would that happen - 8,
> 256, 64K ?
>=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