On 12/5/05, Ryan Charles Underwood <[EMAIL PROTECTED]> wrote:
Nope, they are definitely synced up. Does anyone have any ideas how
I can dig into this further? Right now backups are non-functional
because of it.
We have seen errors probably of a similar origin during AFS backups.
Our TCs were running 1.2.13, and fileservers were already 1.4.0. The
error manifested itself in a loss of token after several successfully
backed up volumes, all subsequent backup operations were failing with
a TExxx message similar to this:
Sun Nov 27 00:38:40: Task 4002: Volume foo.bar (536912108) failed
rxk: sealed data inconsistent
The problem could be cured by "vos remove *.backup" followed by
new "vos backupsys", but it would be reppearing again within 2-3 days.
We have now migrated the TCs to 1.4.0, and made sure that all machines
involved are connected to the same GigE switch. There was not a single
problem since 5 days, we are now monitoring it. But the problem is apparently
there and may show up again. I believe it should have to do something with
timing, sort of a race condition which only pops up on a fast network. Would
it be repeating again, we will try to do some debug of butc/volserver.
Andrei.
