I thought we had fixed the problem where a client ignores an rx abort from a fileserver, but now I'm seeing it on a client built from cvs head yesterday. Shouldn't the client tear down the connection and start a new one? Or does abort just apply to that call, not the entire connection? Trace is here: /afs/citi.umich.edu/user/rees/www/fs-abort.bin The server is some kind of 1.2.x.