[OpenAFS] Re: How to remove a bogus ( server entry for readonly volume?

Harald Barth haba@kth.se
Fri, 13 Dec 2013 15:16:14 +0100 (CET)

My test:

# cat /etc/hosts       localhost       bananshake.stacken.kth.se       bananshake

# bos restart bananshake -local -all

# cat FileLog
Fri Dec 13 14:38:18 2013 Getting FileServer address...
Fri Dec 13 14:38:18 2013 FileServer bananshake.stacken.kth.se has address (0x101007f or 0x7f000101 in host byte order)
Fri Dec 13 14:38:18 2013 File Server started Fri Dec 13 14:38:18 2013

So the server thinks somewhere it is, but is this message
bogus as it would be more interresting to know which addresses the
file server actually registered in the db.

When I check, it has not registered it in the address list, bananshake
is still with only one IP under UUID 007cadf8-b425-124e-91-2e-e8eded82aa77:

# vos listaddr -local -printuuid -nores -noauth -c stacken.kth.se
UUID: 000a40c4-cfeb-1228-b1-12-0101007faa77

UUID: 00230816-42a1-1361-ae-c3-2ceaed82aa77

UUID: 00438a50-e3e5-115d-8f-56-d8eaed82aa77

UUID: 0047a130-223f-1244-9b-0b-0101007faa77

UUID: 003f1f1a-0189-106e-b6-45-0101007faa77

UUID: 007cadf8-b425-124e-91-2e-e8eded82aa77

Nevertheless you can create volumes:

# vos create bananshake a -name broken.volume -local -verbose 
Volume broken.volume 536911797 created and brought online
Created the VLDB entry for the volume broken.volume 536911797
Volume 536911797 created on partition /vicepa of bananshake

# vos listvldb -server bananshake.stacken.kth.se -nores
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
VLDB entries for server bananshake.stacken.kth.se 

    RWrite: 536911797 
    number of sites -> 1
       server partition /vicepa RW Site 

Total entries: 1

To clean up I did a vos remove -id 536911797 -local as I knew that it
was a throwaway volume which makes it easier than if you want only to
remove one replica.

Btw, this is
# rxdebug localhost -v
Trying (port 7000):
AFS version:  OpenAFS 1.6.1-3+deb7u1-debian built  2013-07-25 

And I have not found where this filtering of 127/something actually
takes place. Pointers welcome.