[issue1872] nfs stall (fix pushed)

["Thomas Nikolajsen \(via DragonFly issue tracker\)" <sinknull@xxxxxxxxxxxxxxxxxxxxx>]

Thomas Nikolajsen <thomas.nikolajsen@mail.dk> added the comment:

A few questions from IRC:
<dillon> is it basically /usr/src and /usr/obj ?
<dillon> or do you have things like /tmp NFS mounted too ?
I have a bunch of other NFS mounts (e.g. my home dir.), not /tmp or /var/tmp 
though, they are on tmpfs and HAMMER respectively.
The traffic on the other NFS mounts are quite minimal during test.

<dillon> when a program stalls can you still access the mount points(s) ?
This is a bit mixed I think: on some stalls even a new root login stalls, this 
uses no NFS (root home dir. is on local UFS or HAMMER),
on some stall other NFS mounts do respond up to some point, where they also 
stall.
On stall I often (but not always) get console messages; don't remember exact 
wording, it is in core dumps uploaded previously for this issue.
Should I upload some fresh forced core dumps?

<dillon> I also need to know how much memory the client & server have, maybe 
my test box just has too much memory to hit the conditions right
Both client and servers has 2GB RAM.

<dillon> I'm not sure if it is a server-side issue or a client-side issue, 
which is making it difficult to track down
Any hint on how I can help narrow this down?

_____________________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1872>
_____________________________________________________