Andrew Bacchi wrote:
After adding the NetRestrict file and waiting for a scheduled fileserver restart, the two interface addresses are still listed in the VLDB. I suppose this is normal, since I did not explicitly issue a 'vos changeaddr -remove'.However, when I do try to remove them, the VLDB refuses, saying there are still volume listings. Clearly the process does not see a difference between the address of the fileserver and the interface cards. This behavior is the same when trying to remove by name, afsfs12-iscsi0, or by IP address.
The VLDB contains IP addresses not names. When you remove by name, the name is resolved into an IP address. There is no knowledge of interfaces.
vos changea -remove 123.456.789.100 Could not remove server 123.456.789.100 from the VLDB VLDB: volume Id exists in the vldbThe only way I can see to make it happen is to move all 5K volumes to another server, remove the listing from the VLDB and return the volumes. Does anyone else have a suggestion on how to safely remove these addresses? Or am I overlooking something?
You can use vos delentry to remove the entries from the VLDB without moving the volumes and then use vos syncvldb to generate new entries for the deleted volumes. http://www.openafs.org/pages/manpages/1/vos_delentry.html http://www.openafs.org/pages/manpages/1/vos_syncvldb.html Of course, only do this after you have NetRestricted the file server. Then you can remove the extraneous server entries from the VLDB. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
