From: Rich <rich@hq.vsaa.lv>
To: nfs@lists.sourceforge.net
Subject: poor nfs performance & hangs with latest kernels
Date: Mon, 19 Feb 2007 16:49:57 +0200 [thread overview]
Message-ID: <45D9B915.2010305@hq.vsaa.lv> (raw)
hi. i am having a pretty weird nfs performance problems.
(please, cc me, as i am not on the list).
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).
when the problem appears, access to the same data both locally and even
over ssh is happening without any slowdown, but nfs access is sometimes
slowed down significantly, in some cases even being unable to list a
directory for 30 minutes.
in some cases, not only nfs slowdown happens, but whole system hangs.
i have tried nfstools 1.0.10 and 1.0.7 & portmap 5.0 (though their
versions seem to have no impact).
there is one scenario where it is very easy to reproduce the problem
(note : don't try this on a remote system or one you can not afford to
hard reboot) :
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
depending on machine, i jave managed to get from 32mb (my workstation)
to ~ 880mb (server) files. then, either nfs becomes unaccessible (for
all hosts and all disks/exported filesystems), or machine hangs
completely. if machine does not hang, it's load increases steadily, and
all cpus are shown to have very high iowait load.
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.
in this case, stopping nfs server seems to lower the load and return the
system to normal state.
this seems to be very similar to already reported bug,
http://bugme.osdl.org/show_bug.cgi?id=7943
has anybody else seen such a behaviour ?
i would appreciate if somebody could test this or provide additional
things to test. flips on #linux-nfs noted that "it would be good to get
a sysrq-t listing". if required, i could try this on my workstation with
either 16.21, 19.1 or .20 - though, if really needed, probably with any
kernel version :)
in such a case i would be glad to receive some guidance how to best
perform this activity and gather output.
thanks.
--
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
next reply other threads:[~2007-02-19 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 14:49 Rich [this message]
2007-02-20 9:45 ` poor nfs performance & hangs with latest kernels Neil Brown
2007-02-20 12:45 ` Rich
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=45D9B915.2010305@hq.vsaa.lv \
--to=rich@hq.vsaa.lv \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.