System lockup with recent pull from Bruce's git tree
Frank Filz
ffilzlnx at us.ibm.com
Fri Sep 8 11:58:04 EDT 2006
On Thu, 2006-09-07 at 11:01 -0400, J. Bruce Fields wrote:
> Note that the client and server are not designed to be deadlock-free
> when they're on the same machine. (The client may not be able to write
> out dirty pages until the server gets some memory it needs to handle the
> requests, and the server may not be able to get that memory until the
> client can free those dirty pages.) I run connectathon test and such
> regularly over localhost mounts, but those don't touch a lot of data.
>
> So can you reproduce this with client and server on separate machines?
After an overnight run, this has not re-created when the server is a
separate machine.
One thought though - if the problem is the response coming back before
the client can get into the wait code, the problem might only be visible
when the server is the same machine as the client, with an instantaneous
transmission of the request and response.
Frank
More information about the NFSv4
mailing list