NFS file xfer of size of client memory = bad scene

[Jeff Blaine <jblaine@mitre.org>]

I have a box with 4GB.  It's running 2.6.10.

I am trying to run Iozone with -g and an argument to it
that is larger than the physical memory in the NFSv3
client machine.

For instance, on this 4GB box, I am trying '-g 4224m'.
More specifically, the entire command line is:

     ./iozone -a -g 4224m -f /sol9box/testfile

As soon as it finally gets to trying a file size of
4194304, oom-killer steps in and starts blasting
processes off my machine (WTF?  Great.)

Brings up 'oom-killer' instances under 2.6.10 and the
whole benchmark run dies, sometimes along with my
shell, my X session, ANY net services at all (can't
SSH into the box... can't get console to wake up...),
etc.

Exact same command line worked in Linux 2.4.21 loaded
on this same exact machine with the same NFSv3 server
being talked to.



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs