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

Kim Kimball dhk@ccre.com
Mon, 08 Oct 2007 07:38:33 -0600

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
<blockquote type="cite">
  <pre wrap="">How does one know that the 127.* IPs really are gone?</pre>
vos listaddr<br>
>From a client-only machine, 'vos listvl -server'<br>
Christopher D. Clausen wrote:
<blockquote cite="mid:4593279.1191592875751.JavaMail.root@m11"
  <pre wrap="">Kim Kimball <a class="moz-txt-link-rfc2396E" href="mailto:dhk@ccre.com">&lt;dhk@ccre.com&gt;</a> wrote:
  <blockquote type="cite">
    <pre wrap="">You might also try
vos remove &lt;server&gt; &lt;partition&gt; &lt;volumename&gt;.readonly     #for each
readonly instance
vos backup &lt;volumename&gt;
vos dump &lt;volumename&gt;.backup | vos restore &lt;server&gt; &lt;partition&gt;
&lt;volumename&gt; -overwrite full

Use the same volume name for each instance of &lt;volumename&gt;

This will give you a new volumeID for &lt;volumename&gt; which will be
reflected in the VLDB. Then "vos addsite" to replace the RO sites.
Then "vos release"
  <pre wrap=""><!---->
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?


When specifing server names, DO NOT use "localhost" or ""  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?


OpenAFS-info mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openafs.org/mailman/listinfo/openafs-info">https://lists.openafs.org/mailman/listinfo/openafs-info</a>