On 10/5/07, Christopher D. Clausen <[EMAIL PROTECTED]> wrote: > > Kim Kimball <[EMAIL PROTECTED]> wrote: > > 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" > > I was going to suggest that, but I figured it may not actually clear up > the problem and could potentially just waste a lot of time. > > How does one know that the 127.* IPs really are gone?
vos listvl? ----- > > When specifing server names, DO NOT use "localhost" or "127.0.0.1." Use > the FQDNs of your servers. > > ----- > > Hmm... would vos delent for each volume, then the vos > changeaddr -remove, and then a vos syncvldb do the same thing and not > take as much time for the dump / restores? even if changeaddr -remove fails, you can changeaddr to a bogus address, listvl and delent for the bogus address, then syncvldb. at worst you have an orphan address in the vldb that no one is going to care about.
