FW: [OpenAFS] Turning interfaces off

[ted creedon]

afs seems to have renamed the primary R/W server after the external iP 
address c-24-10-22-222.hsd1.mn.comcast.net from its hostname address of 
10.1.1.194 and won't release teh volumes.... This was working for a long 
time, what's changed? junk.vol only has 3 replication sites nanook, 
redcloud and nome (changed to server c-24-10-22-222.hsd1.mn.comcast.net).

*nome:/usr/afs/logs # vos examine junk.vol*
+ vos examine junk.vol
junk.vol 536870972 RW 3202602 K On-line
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
RWrite 536870972 ROnly 536870973 Backup 0
MaxQuota 8000000 K
Creation Wed Aug 17 16:13:54 2005
Copy Wed Aug 17 16:13:54 2005
Backup Never
Last Update Wed May 9 17:50:13 2007
10 accesses in the past day (i.e., vnode references)

RWrite: 536870972 ROnly: 536870973 RClone: 536870973
number of sites -> 8
server c-24-10-22-222.hsd1.mn.comcast.net partition /vicepa RW Site -- 
New release
server nanook.home.ted-doris.fa partition /vicepa RO Site -- New release
server c-24-10-22-222.hsd1.mn.comcast.net partition /vicepa RO Site -- 
New release
server redcloud.ted-doris.fam partition /vicepa RO Site -- New release
server c-24-10-22-222.hsd1.mn.comcast.net partition /vicepa RO Site -- 
Old release
server c-24-10-22-222.hsd1.mn.comcast.net partition /vicepa RO Site -- 
Old release
server c-24-10-22-222.hsd1.mn.comcast.net partition /vicepa RO Site -- 
Old release
server c-24-10-22-222.hsd1.mn.comcast.net partition /vicepa RO Site -- 
Old release

*nome:/usr/afs/logs # vos release junk.vol*
+ vos release junk.vol
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
The volume 536870972 could not be released to the following 4 sites:
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
VOLSER: release could not be completed
Error in vos release command.
VOLSER: release could not be completed
nome:/usr/afs/logs # vos release junk.vol
+ vos release junk.vol
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
The volume 536870972 could not be released to the following 4 sites:
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
c-24-22-2-105.hsd1.mn.comcast.net /vicepa
VOLSER: release could not be completed
Error in vos release command.
VOLSER: release could not be completed



ted creedon wrote:
>-----Original Message-----
>From: openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs.org]
>On Behalf Of Lars Wilke
>Sent: Sunday, May 20, 2007 3:59 PM
>To: openafs-info@openafs.org
>Subject: Re: [OpenAFS] Turning interfaces off
>
>* Andrew Deason wrote:
>  
>>ted creedon <tcreedon@easystreet.com> wrote:
>>
>>    
>>>I thought that afs listened only to the interface that carried the
>>>host address and additional addresses could be added via the NetInfo
>>>file.
>>>      
>>NetInfo/NetRestrict only affects the addresses that are advertised to
>>clients, as I recall, not what addresses/interfaces we listen on.
>>
>>Search the archives for the '-rxbind' switch for what you want.
>>    
>
>Basically it boils down to setting the interfaces you want the AFS
>services listen on to be listed in the NetInfo file and everything
>else in the NetRestrict file. Then add -rxbind to the services
>in the BosConfig file.
>
>Add the option to the fileserver, volserver, ptserver and vlserver
>or whatever services you want to restrict.
>The AFS clients have their own Net* files and the afsd also knows
>about the -rxbind option.
>
>hth
>   --lars
>_______________________________________________
>OpenAFS-info mailing list
>OpenAFS-info@openafs.org
>https://lists.openafs.org/mailman/listinfo/openafs-info
>
>
>