[8628] in Info-AFS_Redistribution
Re: automating 'vos release'
daemon@ATHENA.MIT.EDU (Jim Barlow)
Mon Apr 16 11:29:27 2001
X-Envelope-From: jbarlow@ncsa.uiuc.edu
Date: Mon, 16 Apr 2001 10:23:03 -0500
From: Jim Barlow <jbarlow@ncsa.uiuc.edu>
To: David R Boldt <dboldt@usgs.gov>
Cc: info-afs@transarc.com
Message-ID: <20010416102303.A10112@osage.ncsa.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF70E57C71.A2F61CE4-ON85256A30.0051CC41@er.usgs.gov>; from dboldt@usgs.gov on Mon, Apr 16, 2001 at 11:02:37AM -0400
On Mon, Apr 16, 2001 at 11:02:37AM -0400, David R Boldt wrote:
>
> * if the read/write version of a volume has not changed since
> the last release, will "vos release" no-op, or will it try to
> synchronize anyway.
It will try to sync with the RO copies. However, it will only update the
modified information.
> * would it make sense to attempt to determine whether a volume
> has changed before doing a release? --I don't have a very good
> sense for how resource expensive "vos release" is.
>
> if it would be a good idea to only release when necessary, is there
> a more efficient way to discover whether a read/write volume has
> changed since the last release other than comparing the mtimes
> of all directories in the volumes?
> Is anyone else doing this sort of thing?
We do this very thing with a perl script with a large number of our
volumes. However, you can check the "Last Update" time of a read-write
volume against one of it's corresponding read-only volumes to determine
if a vos release needs to be done (done with a vos exam). You can check
just one read-only copy, or all of them.
--
James J. Barlow <jbarlow@ncsa.uiuc.edu>
Senior System Engineer
National Center for Supercomputing Applications Voice : (217)244-6403
605 East Springfield Avenue Champaign, IL 61820 Cell : (217)840-0601
http://www.ncsa.uiuc.edu/People/jbarlow Fax : (217)244-1987
