From: Olaf Kirch <okir@suse.de>
To: Ian Thurlbeck <ian@stams.strath.ac.uk>
Cc: Steve Dickson <SteveD@redhat.com>, nfs@lists.sourceforge.net
Subject: Re: Strange delays on NFS server
Date: Wed, 11 Aug 2004 18:41:35 +0200 [thread overview]
Message-ID: <20040811164135.GA11101@suse.de> (raw)
In-Reply-To: <411A448D.3080205@stams.strath.ac.uk>
On Wed, Aug 11, 2004 at 05:08:45PM +0100, Ian Thurlbeck wrote:
> OK, I've been running "top -d 1 -i" and trying to see what comes up when
> the server freezes. I caught one instance where a delay coincided
> with about 15 nfsd + 1 kjournald process appearing in the top
> display. I'm simultaneously looking at a graphical network tool to try
> and see the traffic going to the server - anyone got a better suggestion?
This sounds exactly like the COMMIT stall problem for which I submitted
the early-writeout patch to this list about a week ago.
I've been thinking about this a little more. It may be that one reason
the problem is more pronounced in in 2.6 than in 2.4 is the new io
barrier code. In 2.6 ext3 uses barriers by default; Suse's 2.6 has reiserfs
patches that add barriers (and enables them by default). We've reports of
this problem on both file systems.
JFS does i/o barriers while XFS does not; and this also fits the pattern
of what Ian reports. I dimly remember there's a kernel command line
option to turn off barriers at the block io level. Can you try if
that helps, Ian?
The more I think about this, the more I believe the early-writeout patch
is the right way to address this problem (short of turning off barriers).
When data hits the NFS server, it is supposed to go to disk rather
soonishly. This also covers most of the rewrite case, at least as long
as you have just one application writing to the file - all rewriting
happens in the client cache.
The crucial question is, what is a good heursitic to choose when to
initiate a write-out. Sequential writes to the end of file are easy
enough to detect.
I have a somewhat updated version of my patch that covers just this
case, and exports a sysctl to let you tune how often it initiates
an early write-out.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
-------------------------------------------------------
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-11 16:41 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 [this message]
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
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=20040811164135.GA11101@suse.de \
--to=okir@suse.de \
--cc=SteveD@redhat.com \
--cc=ian@stams.strath.ac.uk \
--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.