> I was just wondering if anyone ran into any strange problems or if
> anyone had any helpful hints, besides what's documented in the
> upgrade guide.
Use 'vldbconvert -showversion' to CHECK THAT YOUR CURRENT DATABASE IS
REALLY VERSION 3, not version 2. I had been running what I thought was
AFS 3.3a for more than a year, but for whatever reason, the database
format was still version 2. While it turned out later that 'vldbconvert
-showversion' was able to report that fact, 'vldbconvert -from 3 -to 4'
was not able to recognize its unability to convert the database.
Instead, it produced a corrupted database without reporting any error.
I have seen a lot of stupid programs, but this one probably qualifies
as the most idiotic bug ever. As a result, the migration of my database
servers appeared to have been done successfully. However, in the very
second the first AFS 3.4 fileserver came up and registered itself with
the VLDB server, the database server's attempt to convert the database
ended up in a disaster. No volumes where accessible anymore, and 'vos
listvldb' reported all volumes on a single server that didn't even
exist at all (actually on the very first IP address that had been used
for a fileserver during my cell's history).
--
Michael Niksch TEL: +41-1-7248-913
IBM Zurich Research Laboratory FAX: +41-1-7240904
Saeumerstrasse 4 [EMAIL PROTECTED] (NIK at ZURICH)
CH-8803 Rueschlikon / Switzerland http://www.zurich.ibm.com/~nik/
