On Sun, Nov 25, 2012 at 2:10 AM, Staffan Hämälä <[email protected]> wrote:
> I happened to have a record of the location of the volume, where I saw > that the volume used to be in partition a, not c. > > On the file server, I've checked: > $ ls -l /vicepc/*537689471* > -rw-r--r-- 1 root root 76 21 okt 19.19 /vicepc/V0537689471.vol > $ ls -l /vicepa/*537689471* > -rw-r--r-- 1 root root 76 21 okt 16.26 /vicepa/V0537689471.vol > This is a broken situation: you can have replicas of a volume on different servers, but not on different partitions of the same server. This is why you're getting the error messages you reported. Figure out which one of these is the correct volume; then I think you "vos zap" the other and then resync the VLDB. FileLog on the server has these errors: > Sat Nov 24 16:02:26 2012 Warning: Duplicate volume id 537689471 detected. > Sat Nov 24 16:34:06 2012 Volume 537689471 offline: not in service > -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix/linux, openafs, kerberos, infrastructure http://sinenomine.net
