[OpenAFS-port-darwin] Client not listing recent files on Intel Mac

Alexander Wetzler awetzler@ikf.uni-frankfurt.de
Fri, 2 Feb 2007 11:21:30 +0100


I mainly access the files using terminal applications, but the  
effects are visible in the Finder as well. Basically after the  
problem appears, it affects every way I use to access the files using  
this particular client. If I do a tcpdump on the udp portrange  
7000-7010 while everything is still running fine, and touch a file  
using another afs client than my mac, I get the following output:

10:19:09.205008 IP (tos 0x0, ttl 242, id 55078, offset 0, flags [DF],  
proto: UDP (17), length: 80) afs31.cern.ch.afs3-fileserver >  
pcikf142.ikf.physik.uni-frankfurt.de.afs3-callback: [udp sum ok]  rx  
data cid 1530d960 call# 3 seq 1 ser 5 <client-init>,<last-pckt> cb  
call callback fid 537107775/121/74576 afsuuid [|cb] (52)
10:19:09.205171 IP (tos 0x0, ttl  64, id 13285, offset 0, flags  
[none], proto: UDP (17), length: 56) pcikf142.ikf.physik.uni- 
frankfurt.de.afs3-callback > afs31.cern.ch.afs3-fileserver: [bad udp  
cksum 24ef!]  rx data cid 1530d960 call# 3 seq 1 ser 3 <last-pckt> (28)
10:19:09.214832 IP (tos 0x0, ttl 242, id 55079, offset 0, flags [DF],  
proto: UDP (17), length: 93) afs31.cern.ch.afs3-fileserver >  
pcikf142.ikf.physik.uni-frankfurt.de.afs3-callback:  rx ack cid  
1530d960 call# 3 seq 0 ser 6 <client-init>,<slow-start> first 2  
serial 0 reason delay ifmtu 5692 (65)

If I do the same after the problem starts to appear, I get nothing at  
all using the tcpdump on the udp portrange 7000-7010. If this is the  
right thing to look at, I guess no callback is coming from the server.

On Feb 1, 2007, at 7:04 PM, Derrick J Brashear wrote:

> On Thu, 1 Feb 2007, Alexander Wetzler wrote:
>
>> I have the openafs client running on an intel Mac (core duo CPU).  
>> It happens regularly that the client seems to lose contact to the  
>> afs server:
>>
>> New files which are created by a different client are not seen on  
>> the Mac client. If files are removed by a different client from a  
>> directory, the directory listing on the Mac client will still show  
>> the file in the directory listing, but will mention that it cannot  
>> be found. If a file is replaced by another client, the Mac client  
>> will often just see the previous, obsolete version of the file.
>
> ls? Finder? Something else? If you get a network trace, is a  
> callback break coming from the fileserver?