[OpenAFS-devel] A few questions about the current Linux implementation of the AFS client

[Derrick J Brashear]

On Mon, 21 Jan 2002, Matt Peterson wrote:

> I was not clear in the previous email, but it is not only afsd that will 
> become tied up in syscalls, but any process that happens to be using afs.  A 
> very common example is interruption of cp command via SIGINT.  Lets say that 
> I am copying a very large file from a local device to somewhere on /afs.  If 
> I use bash so if I press ctrl-c the cp process will be send SIGINT.  As soon 
> as this happens, cp will begin to take 100% of the CPU.  

Is this on the same kernel you previously mentioned was not suitably
matched to OpenAFS? Or rather, what kernel version?