Linux NFS development
 help / color / mirror / Atom feed
From: Rich <rich@hq.vsaa.lv>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: poor nfs performance & hangs with latest kernels
Date: Tue, 20 Feb 2007 14:45:02 +0200	[thread overview]
Message-ID: <45DAED4E.4050504@hq.vsaa.lv> (raw)
In-Reply-To: <17882.49990.799201.335846@notabene.brown>

Neil Brown wrote:
> On Monday February 19, rich@hq.vsaa.lv wrote:
...
>> when there is some intensive nfs activity (write), all other nfs 
>> operations slow down to crawl or even stop at all during that time.
>>
>> i have been able to reproduce the problem with kernel versions 
>> 2.6.16.40, 2.6.19.2 and 2.6.20 (on  slackware-11.0).
>> another person reproduced the hang with 2.6.19-1.2911.fc6 (fedora core 6).
> 
> Are there any kernels where you cannot reproduce the problem?

well, now that my localhost tests are invalidated, i will have to do 
additional testing :)

...
>> export a local directory. i'm using 
>> localhost(rw,no_root_squash,sync,no_subtree_check).
>> mount it locally and try to perform a write operation :
>> dd if=/dev/zero of=/mounted_nfs/testfile bs=512k count=2048
> 
> This scenario is known to cause problems, is very hard to fix, and is
> a case of "well don't do that then".  The problems here are probably
> unrelated to the problems you are having between separate machines.

there i was, hoping to have found a reliable method to reproduce the 
problem...
btw, what's the main cause for this problem ? could it also be observed 
on fast networks or is it limited to cases when server & client are on 
the same machine ?

>> using 2.6.16.21, i was unable to hang my workstation, but server, even 
>> though it survived the test, is still having excessive load (~ 4). top 
>> lists as most resource hungry processes nfsd, kjournald and
>> kblockd.
> 
> So 2.6.16.21 survives but 2.6.16.40 doesn't?  Is that a reliable
> result?  Is that with separate server and client, or server and client
> on the same machine?

most tests were done on a single machine (3 different ones, though), 
after i observed initial problems between several clients and single 
server. so now i will have to redo all the tests with separate client & 
server machines :)

> NeilBrown
-- 
  Rich

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-02-20 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 14:49 poor nfs performance & hangs with latest kernels Rich
2007-02-20  9:45 ` Neil Brown
2007-02-20 12:45   ` Rich [this message]
2007-02-21 13:40   ` Jean-Noel Bouvier
2007-02-22  2:28     ` Neil Brown
2007-02-22 19:42       ` Norman Weathers
2007-02-22 20:34         ` Trond Myklebust
2007-03-05 13:30       ` Jean-Noel BOUVIER

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45DAED4E.4050504@hq.vsaa.lv \
    --to=rich@hq.vsaa.lv \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox