From: Keith Owens <kaos@sgi.com>
To: James Pearson <james-p@moving-picture.com>
Cc: nfs@lists.sourceforge.net, linux-xfs@oss.sgi.com
Subject: Re: NFS server stalls with 2.4.18 + XFS 1.1
Date: Fri, 05 Jul 2002 08:39:50 +1000 [thread overview]
Message-ID: <ag2j0e$8o4$2@main.gmane.org> (raw)
In-Reply-To: Your message of "Thu, 04 Jul 2002 17:16:06 +0100." <3D2474C6.461E618@moving-picture.com>
On Thu, 04 Jul 2002 17:16:06 +0100,
James Pearson <james-p@moving-picture.com> wrote:
>We have noticed a problem with a couple of our NFS servers (running
>RedHat 7.2 with a stock 2.4.18 kernel with XFS v1.1) whereby NFS access
>slows to a crawl or stalls.
>
>The exported filesystem(s) are XFS with 8 nfsd's running - when we have
>the problem the load average is about 8 - but CPU usage, disk access and
>network traffic are minimal.
>
>I found, by accident, that running the command 'sync' appears to 'fix'
>the situation...
>
>I'm not sure if this is an XFS or NFS related problem (hence posting to
>both lists).
XFS. 2.4.18 would sometimes get into a situation where two XFS
operations were waiting on locks (not deadlocked) and nothing was
moving. Performing some other disk activity such as sync would get
things moving again.
AFAICT this is fixed in the XFS CVS tree, against 2.4.19-rc1.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Caffeinated soap. No kidding.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2002-07-04 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D2474C6.461E618@moving-picture.com>
2002-07-04 22:39 ` Keith Owens [this message]
2002-07-04 16:16 NFS server stalls with 2.4.18 + XFS 1.1 James Pearson
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='ag2j0e$8o4$2@main.gmane.org' \
--to=kaos@sgi.com \
--cc=james-p@moving-picture.com \
--cc=linux-xfs@oss.sgi.com \
--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.