This is a minor point, but with afs-3.1a, I get "vmunix: afs: setting
clock ahead 2 seconds ..."
The time setting mis-feature of afs is just a backup system in case you
forgot to run ntp. Here is what you should do. Run ntp (or other time sync
service of your choice) on all clients and servers, and start all afsds with
the -nosettime option.
Depending on afs to set your clock is not a good idea. The resolution is
extremely poor (2 seconds at best) and, as you point out, the clock will
jump rather than slewing.
