From: Jan Bruvoll <jan@bruvoll.com>
To: Ian Thurlbeck <ian@stams.strath.ac.uk>
Cc: Olaf Kirch <okir@suse.de>, nfs@lists.sourceforge.net
Subject: Re: Strange delays on NFS server
Date: Tue, 24 Aug 2004 11:27:02 +0100 [thread overview]
Message-ID: <412B17F6.3030700@bruvoll.com> (raw)
In-Reply-To: <412B0EDE.5010206@stams.strath.ac.uk>
Dear all,
Ian Thurlbeck wrote:
> I have tested the patched kernel - it is no different. In fact
> I'd say it's slightly worse. I've been running "atop" to monitor
> net/disk io and during an "event" I see that the main 3ware raid
> array is writing at 100% (60MB/sec+) for up to 50 seconds. There
> is little network traffic. During this period client machines are
> unusable if they are requesting stuff off the server.
I haven't had the opportunity to test things this thoroughly yet, but I
see the same symptoms on our server here - when the "hick-up" comes, the
server, if under heavy fire, will be completely unresponsive for as long
as it is trying to get out of the mess. After a little while, things
will clear up again (I guess that could have to do with clients just
giving up on things), just to clog up about a minute later.
And as Ian mentions, the clients will be stuck for as long as this goes on.
Thanks very much for your continued efforts - if there is anything I
could do to help debug this issue or otherwise contribute to the fixing
of this problem, I'd happily oblige!
Best regards
Jan
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-24 10:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 10:55 Strange delays on NFS server Ian Thurlbeck
2004-08-11 11:58 ` Olaf Kirch
2004-08-11 12:58 ` Steve Dickson
2004-08-11 16:08 ` Ian Thurlbeck
2004-08-11 16:41 ` Olaf Kirch
2004-08-11 16:53 ` Phy Prabab
2004-08-11 16:57 ` Christoph Hellwig
2004-08-11 19:42 ` Norman Weathers
2004-08-12 8:04 ` Ian Thurlbeck
2004-08-12 15:15 ` Ian Thurlbeck
2004-08-13 14:53 ` Steve Dickson
2004-08-16 12:40 ` Ian Thurlbeck
[not found] ` <20040816131434.GL3510@suse.de>
[not found] ` <4120C8D5.3040606@stams.strath.ac.uk>
[not found] ` <20040816145435.GQ3510@suse.de>
[not found] ` <4124CD95.7020007@stams.strath.ac.uk>
[not found] ` <20040820095854.GC23176@suse.de>
2004-08-24 9:48 ` Ian Thurlbeck
2004-08-24 10:27 ` Jan Bruvoll [this message]
2004-08-25 2:02 ` Greg Banks
2004-08-25 8:40 ` Ian Thurlbeck
2004-08-25 10:02 ` Greg Banks
2004-08-25 10:36 ` Ian Thurlbeck
2004-08-24 11:07 ` Neil Brown
2004-08-24 14:22 ` Ian Thurlbeck
2004-08-24 23:54 ` Neil Brown
2004-08-26 11:01 ` Strange delays on NFS server (with piccies) Ian Thurlbeck
2004-08-27 1:22 ` Neil Brown
2004-08-27 4:10 ` Greg Banks
2004-08-11 19:07 ` Strange delays on NFS server Steve Dickson
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=412B17F6.3030700@bruvoll.com \
--to=jan@bruvoll.com \
--cc=ian@stams.strath.ac.uk \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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