[OpenAFS] iSCSI disk in vos listaddr
Tue, 24 Jun 2008 09:41:40 -0400
You are correct, the restart corrected the VLDB without 'delentry'.
I'm testing all of this on a brand new server without any volumes on
it. I tried it after adding a volume to the server and the iSCSI
listing disappeared also. Thanks for your advice.
Here's the listaddr without the Net* files.
>bos shutdown afsfs14 -wait -local
I added the /usr/afs/local/Net* files.
>bos start afsfs14 fs -local
Tue Jun 24 09:15:08 2008 File server starting
Tue Jun 24 09:15:08 2008 afs_krb_get_lrealm failed, using rpi.edu.
Tue Jun 24 09:15:08 2008 Set thread id 16 for FSYNC_sync
Tue Jun 24 09:15:08 2008 FSYNC_sync: bind failed with (98), removed
Tue Jun 24 09:15:08 2008 Partition /vicepa: attaching volumes
Tue Jun 24 09:15:08 2008 Partition /vicepa: attached 2 volumes; 0
volumes not attached
Tue Jun 24 09:15:08 2008 Getting FileServer name...
Tue Jun 24 09:15:08 2008 FileServer host name is 'afsfs14.server.rpi.edu'
Tue Jun 24 09:15:08 2008 Getting FileServer address...
Tue Jun 24 09:15:08 2008 FileServer afsfs14.server.rpi.edu has address
126.96.36.199 (0x4c167180 or 0x8071164c in host byte order)
Tue Jun 24 09:15:08 2008 File Server started Tue Jun 24 09:15:08 2008
Tue Jun 24 09:15:08 2008 Set thread id 18 for 'FiveMinuteCheckLWP'
Tue Jun 24 09:15:08 2008 Set thread id 19 for 'HostCheckLWP'
Tue Jun 24 09:15:08 2008 Set thread id 20 for 'FsyncCheckLWP'
Chaskiel Grundman wrote:
> On Mon, 16 Jun 2008, 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'.
> That should not be needed. If the netrestrict file was correct, and
> the fileserver actually restarted, it should have corrected the
> addresses in the vldb.
> Can we see your NetRestrict file and the FileLog? Are you sure the
> netrestrict file is in the right place? (/usr/afs/local or equivalent,
> NOT /usr/afs/etc where CellServDB/ThisCell/KeyFile/Userlist are)
>> The 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?
> If you do this (or the delentry trick) and the fileserver isn't
> correctly configured yet, the bad addresses will just come back.
veritatas simplex oratio est
Rensselaer Polytechnic Institute
phone: 518.276.6415 fax: 518.276.2809