[OpenAFS] AFS Fileserver Won't Start --> Can't Release root.cell or root.afs
Derrick Brashear
shadow@gmail.com
Fri, 5 Oct 2007 09:23:30 -0400
------=_Part_13769_6516903.1191590610052
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
There was a bug in some older OpenAFS that would let 127.0.0.1 be
advertised. If you're not running something modern, upgrade.
Anyway, you can also put 127.0.0.1 in the NetRestrict file and restart,
masking it out from the list of advertised addresses.
On 10/5/07, Christopher D. Clausen <cclausen@acm.org> wrote:
>
> Karl M. Davis <karl@ridgetop-group.com> 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:
> >
> > karl@picacho:~$ 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
>
------=_Part_13769_6516903.1191590610052
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
There was a bug in some older OpenAFS that would let <a href="http://127.0.0.1">127.0.0.1</a> be advertised. If you're not running something modern, upgrade.<br><br>Anyway, you can also put <a href="http://127.0.0.1">127.0.0.1
</a> in the NetRestrict file and restart, masking it out from the list of advertised addresses.<br><br><br><br><div><span class="gmail_quote">On 10/5/07, <b class="gmail_sendername">Christopher D. Clausen</b> <<a href="mailto:cclausen@acm.org">
cclausen@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Karl M. Davis <<a href="mailto:karl@ridgetop-group.com">
karl@ridgetop-group.com</a>> wrote:<br>> I then tried running "vos changeaddr -oldaddr <a href="http://127.0.0.1">127.0.0.1</a> -remove", but<br>> it looks like some of my volumes are still "stuck" on the old IP:
<br>><br>> karl@picacho:~$ sudo vos changeaddr -oldaddr <a href="http://127.0.0.1">127.0.0.1</a> -remove<br>> -localauth -verbose<br>> Could not remove server <a href="http://127.0.0.1">127.0.0.1</a> from the VLDB
<br>> VLDB: volume Id exists in the vldb<br><br>I'd say to try and get a good vos dump of each volume that you care<br>about so that you can at least restore to a new cell if things go bad<br>from here.<br><br>Usually I'd fix this finding the volume that is listed as being on that
<br>IP and moving it to another server :-) But it would seem that you have<br>already done that. I guess its possible that the vldb still thinks that<br><a href="http://127.0.0.1">127.0.0.1</a> is one of the servers somehow. Did you try restarting your
<br>file servers?<br><br>Does vos syncvldb/syncserv do anything useful for you? If not, it<br>should be safe to shutdown the AFS server and delete the VL db files and<br>have them get recreated at server startup. (Might need to delete the
<br>sysid file as well.)<br><br>Or, vos dumping, deleting, and recreate each volume via vos restore may<br>fix it, assuming you have fixed all <a href="http://127.0.0.1">127.0.0.1</a> problems.<br><br>> How would I go about resolving this? By the way, thanks very much
<br>> for all of your help so far; you've really saved my ass on this.<br><br>No problem. I'm glad it helped.<br><br><<CDC<br><br><br>_______________________________________________<br>OpenAFS-info mailing list
<br><a href="mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a><br><a href="https://lists.openafs.org/mailman/listinfo/openafs-info">https://lists.openafs.org/mailman/listinfo/openafs-info</a><br></blockquote></div>
<br>
------=_Part_13769_6516903.1191590610052--