[OpenAFS] Last Update not updating?
Tue, 10 Jan 2006 20:40:45 -0800
The vos release won't actually do any volume copying
if things are already up-to-date, but it takes a lot
longer to issue a vos release on a set of, say, 10
volumes than to check the dates and release the
one that has been updated.
Any chance of adding a switch to the vos exam command
so that if you do something like
vos exam my.vol -sync -cell pictage -local
you get the old behavior, and without the -sync
you get the new behavior? If I issue the 10
vos release commands, it will have to sync
anyway, and apparently do a lot more stuff.
Since I'm interested in the Last Update
field, it would be helpful to have a way to
make sure it's accurate. For the times when
I don't care, of course the new behavior is
Just a thought.
Horst Birthelmer wrote:
> On Jan 10, 2006, at 3:18 AM, Jeffrey Hutzelman wrote:
>> On Monday, January 09, 2006 04:43:47 PM -0800 Mike Polek
>> <email@example.com> wrote:
>>> Good to know. The reason I'm looking at it is that I have a perl
>>> script that will release a set of volumes, but only if they
>>> need it. It checks the updateDate of the volume and compares
>>> it to the updateDate of the cloneID if there is one to
>>> figure out if the volume needs to be released.
>> Yup; we have that too. It doesn't notice changes made too close
>> before it runs. That's one of the reasons I'm looking at making 'vos
>> examine' go back to the slower, more accurate results.
> Jeff, I remember our talk at the 2004 Hackathon about this.
> The problem was not that the examine took too long.
> The problem was, that you could cause timeouts on file transfers, if
> you do a few 'vos examine' calls, due to the disk operations those
> calls would trigger.
> I think it's trouble to go back.
> BTW, 'vos release' won't do any transfer if the RW volumes didn't change.
Manager of System Operations
This message, together with any attachments, is intended only for the use of
the individual or entity to which it is addressed. It may contain
information that is confidential and prohibited from disclosure. If you are
not the intended recipient, you are hereby notified that any dissemination
or copying of this message or any attachment is strictly prohibited. If you
have received this item in error, please notify the original sender and
destroy this item, along with any attachments.