[1093] in SIPB-AFS-requests
Re: releasing of volumes
daemon@ATHENA.MIT.EDU (mhpower@athena.mit.edu)
Mon Aug 2 14:46:50 1993
From: mhpower@athena.mit.edu
To: ckclark@athena.mit.edu
Cc: sipb-afsreq@athena.mit.edu, yandros@athena.mit.edu
In-Reply-To: [1092] in SIPB-AFS-requests
Date: Mon, 02 Aug 93 14:45:22 EDT
>There are a number of read-only volumes in the sipb cell which normally
>only get released when backups are done.
I don't remember any part of the backup procedures doing vos release.
It was always just vos backup. Has this changed recently?
> ... /var/usr/local/sync/release.sh which is run out of crontab at 7AM
>every day. It releases every readonly volume in the sipb cell, except ...
...
> for vol in `$vos listvol $s -c $cell -localauth | grep readonly \
> | sed 's/\.readonly.*$//' | egrep -v '^project.sipb$' `; do
Yeah, this does solve the "never remembering to release" problem, but
still, I don't like it very much. I've sometimes had data in an RW
volume that I was rearranging, and didn't want it to go into the RO
copy until I finished working on it. And the work could very easily
still be in progress across a 7 AM boundary.
Would it be possible for your script to process only a specified set
of volumes, or at least support an exclusion file?
Or is the preferred solution to rsh ronald-ann -l root /bin/ed and put
in more egrep -v's whenever we think we might be about to lose?
Matt
