Karl M. Davis <[EMAIL PROTECTED]> wrote: > I then tried running "vos changeaddr -oldaddr 127.0.0.1 -remove", but > it looks like some of my volumes are still "stuck" on the old IP: > > [EMAIL PROTECTED]:~$ sudo vos changeaddr -oldaddr 127.0.0.1 -remove > -localauth -verbose > Could not remove server 127.0.0.1 from the VLDB > VLDB: volume Id exists in the vldb
I'd say to try and get a good vos dump of each volume that you care about so that you can at least restore to a new cell if things go bad from here. Usually I'd fix this finding the volume that is listed as being on that IP and moving it to another server :-) But it would seem that you have already done that. I guess its possible that the vldb still thinks that 127.0.0.1 is one of the servers somehow. Did you try restarting your file servers? Does vos syncvldb/syncserv do anything useful for you? If not, it should be safe to shutdown the AFS server and delete the VL db files and have them get recreated at server startup. (Might need to delete the sysid file as well.) Or, vos dumping, deleting, and recreate each volume via vos restore may fix it, assuming you have fixed all 127.0.0.1 problems. > How would I go about resolving this? By the way, thanks very much > for all of your help so far; you've really saved my ass on this. No problem. I'm glad it helped. <<CDC _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info