On Jul 31, 2011, at 8:54 PM, Andrew Deason <adea...@sinenomine.net> wrote:
> On Sun, 31 Jul 2011 16:09:36 -0400 > Aaron Knister <aar...@umbc.edu> wrote: > >> Something I did just now was change the address of the non-existent >> server on the subnet we no-loner use to a temporary afs file server on >> a subnet we are using: >> >> vos changeaddr -oldaddr 130.85.60.43 -newaddr 130.85.24.58 >> >> I did read the caveats in the man page before running the above >> command. This at least points references to the non-existent >> fileserver to an existing server. I was hoping I could do a syncvldb >> and it would clean up the reference to the invalid volume but to no >> avail. > > Please never do this. I don't know how to be more clear about it: do not > use 'vos changeaddr' to change a fileserver address. There are _no_ > situations where there is any reason to use it in that manner, unless > you are dealing with very old fileservers that predate the multihoming > mechanism. My thought process was this: there was one volume (the un deletable volume) associated with the oldaddr and no volumes with the newaddr. There were also no protection groups containing either machine address. The oldaddr is on a subnet that I can't get access to so by changing oldaddr to newaddr which us on a reachable subnet I was hoping to do a syncserv to clear out the phantom entry. > When you use it to deal with server addresses for servers > that actually still exist (either new or old addr), you may (depending > on the versions in play) duplicate server entries in the VLDB, making it > somewhat difficult to get the VLDB back into its original state. This wasn't one of the caveats mentioned in the man page. Had I known that I likely wouldn't have proceeded. > I don't > know if you've done that and I don't have time to look at it now, but if > you don't notice any problems then you're probably fine. > > As Simon indicates, what you want 'vos delentry', for the entry that > 'vos listvldb' showed you. vos delentry doesn't work-- I tried that a bunch of times before I posted to the list. Heres the error I get: Could not delete entry for volume 536988828 You must specify a RW volume name or ID (the entire VLDB entry will be deleted) VLDB: no such entry Deleted 0 VLDB entries Thanks! > > -- > Andrew Deason > adea...@sinenomine.net > > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
