[OpenAFS] Re: advice on troubleshooting blocked cache manager
on MacOS?
Harald Barth
haba@kth.se
Thu, 28 Jan 2010 11:50:49 +0100 (CET)
> vos changeaddr -remove the useless ones.
So what is the procedure to remove a fileserver interface?
Is it possible to do it without a file server restart?
My guess would be as follows:
I was thinking along the following lines:
Identify interface (yes, that one is real and I want to get rid of it)
$ host kelp-le.pdc.kth.se
kelp-le.pdc.kth.se has address 194.132.192.13
# cat /usr/openafs/var/openafs/NetInfo
130.237.232.193
194.132.192.13 <-remove
# /usr/openafs/sbin/vos listaddr -printuuid -noresolve
...
UUID: 00568830-b5fa-1561-96-cc-c1e8ed82aa77
130.237.232.193
194.132.192.13
...
Check that all volumes are on "kelp" and not "kelp-le":
# /usr/openafs/sbin/vos listvldb | grep kelp-le
*empty list*
What to do if the list is non-empty?
Now for the part that I have not done yet...
# /usr/openafs/sbin/vos changeaddr -oldaddr 194.132.192.13 -remove
After that hapens what? How long do the clients remember that there was
an interface 194.132.192.13 on uuid 00568830-b5fa-1561-96-cc-c1e8ed82aa77 ?
When can I safely shutdown that interface and remove that network?
I'd like to do this without needing to move all the volumes on kelp to
another server. I don't want any 30sec client timeouts either as that
probably makes the calculation jobs crash. I can run a command on all
clients to tell them to forget cached uuid to IP mappings if there is
such a command.
The involved versions here are a mix of 1.4.10 and 1.4.11.
Harald.