In message <[EMAIL PROTECTED]>you write:
>I'm trying to track down a possible bug in my Linux-AFS
>implementation. The symptom that people are seeing is that they try
>to talk to a server which really is up but AFS reports it as lost
>contact. Next time the servercheck is done, it comes up and is fine.
I (used to) get this same kind of condition even with SunOS 4.1.3.
Specifically, to make sure we're speaking of the same thing, if one
of our fileservers went down and came back up, it took either:
a) a period of time
b) fs checkservers
before a client host could access anything AFS wise. I haven't
noticed this behavior since we upgraded to AFS 3.3, FWIW.
>(In the process, they sometimes get an error 110 while trying to store
>a file -- error 110 is VBUSY).
>
>I was wondering if AFS depends upon any specific behavior of the
>Kernel Network code. In particular, does it depend on any special
>behavior of the network write function (i.e., blocking, no dropped
>packets, etc).
>
>Linux, it seems, tends to drop packets on the floor alot (at least
>from what I'm told), and when it does this, AFS gets very unhappy.
>Anyone have any insight for me?
>
>Thanks.
>
>-derek
