On Mar 1, 2006, at 8:05 AM, Juha Jäykkä wrote:
Hi!
I hit a strange error this morning. I did a little mass-resync of our
read-only replicas this morning (it was a bos cron job, ran at 5:30
in the
morning with absolutely no users around). Vos release reported
success for
all volumes, but VolserLog of the fileserver in question says
(these are
from the RW & RO site; there are equivalent lines in the RO fileserver
logs as well; each is just 12 seconds later)
Wed Mar 1 05:38:57 2006 trans 472 on volume 536870933 is older
than 300 seconds
Wed Mar 1 05:39:27 2006 trans 472 on volume 536870933 is older
than 330 seconds
Wed Mar 1 05:39:57 2006 trans 472 on volume 536870933 is older
than 360 seconds
Wed Mar 1 05:40:27 2006 trans 472 on volume 536870933 is older
than 390 seconds
Wed Mar 1 05:40:57 2006 trans 472 on volume 536870933 is older
than 420 seconds
What's going on? I found some mails in the archive with the same log
entries but they all had had their vos release return with an
error! What
concerns me most here is that vos actually told me the volume was
released
successfully. We are doing regular resyncs of the RO volumes
automatically
and not getting an error message from something automatic goes awry is
quite bad.
AFAIK, that's just an informative log entry.
It's telling you that the volume release took longer than X seconds.
It's nothing wrong with that.
Horst_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
