Re: *** Spam *** Re: [OpenAFS] AFS Fileserver Won't Start --> Can't Release root.cell or root.afs

[Kim Kimball]

Thought of two other things you might try. 1. Use "vos delentry" to remove VLDB entries, followed by "vos syncvldb" to recreate entries. 2. Shut down the VLservers, delete the VLDB db files from each DB server (/usr/afs/db/vldb.DB0 & /usr/afs/db/vldb.DBSYS1), start the VLservers again, wait for quorum, and "vos syncvldb" on servers As long as 127.0.0.1 is not the 'primary' IP for any file server the recreated VLDB entries should have no loopback reference. Method 2 is probably the more definitive approach. Kim Kim Kimball wrote: Have you tried changeaddr from 127.0.0.1 to <whatever the IP address of server is> ?? You might also try vos remove <server> <partition> <volumename>.readonly     #for each readonly instance vos backup <volumename> vos dump <volumename>.backup | vos restore <server> <partition> <volumename> -overwrite full Use the same volume name for each instance of <volumename> This will give you a new volumeID for <volumename> which will be reflected in the VLDB. Then "vos addsite" to replace the RO sites. Then "vos release" Kim Christopher D. Clausen wrote: 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 _______________________________________________ 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