We have a slighty different set of symptoms. Several of our 2.5 AFS
clients have developed 'corrupted' caches. We've been bitten by this
on SS20s, SS1000s, and Ultras.
The corruption takes the form of crashing binaries, symlinks which
suddenly point to new (and non-existent) locations, and being unable
to find ".".
So far, the affected files all seem to have been cached before problems
appear.
Destroying the existing cache and creating a new cache dir has worked
as a temporary fix (sometimes as temporarily as an hour...).
