All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe Ducom <jducom@nd.edu>
To: nfs@lists.sourceforge.net
Subject: NFS clients hang
Date: Fri, 11 Jul 2003 09:49:27 -0500	[thread overview]
Message-ID: <3F0ECE77.1050703@nd.edu> (raw)

Hardware:
Dell Precision 530 Dual Xeon1.7GHz 1GB RDRAM

Redhat 7.2 distribution is used with kernel 2.4.21 patched with IngoMolnar IRQ 
balancing as there is a 'bug' with Xeon processors (only one would take care of 
all interrupts), configured with CONFIG_HIGHMEM option. nfs-utils-1.0.3-1 is used.
The mount option for the client is: 
rw,nosuid,nodev,hard,intr,bg,rsize=8192,wsize=8192,nfsvers=3,lock,udp

Sometimes the NFS client was hanging for no reason (usually when a medium size 
file (30MB+) was handled over NFS or a lot files were moved around).
The machine was then completely locked (no access at all to it, even thru serial 
console, no display on the monitor anymore). tcpdump files didn't show anything 
wrong but just stop to report traffic until the lock.
I reconfigured the kernel with CONFIG_DEBUG_SPINLOCK and CONFIG_SOFT_WATCHDOG to 
have access to some debug info. The client was still completely locked up and 
couldn't get out of the locked state.

I finally read in Chuck Lever's technical report "Customers that use 2.4 kernels 
on hardware with more than 896MB shoould know that a special kernel option, 
known as CONFIG_HIGHMEM, is required to access and use memory above 896M. The 
linux NFS client has a known problem in these configurations where an 
application or the whole client system can hang at random. This issue has been 
addressed in the 2.4.20 kernel, but still haunts kernels contained in 
distribution from RedHat and SUSE that are based on earlier kernels".

So I recompiled 2.4.21 without CONFIG_HIGHMEM and since the NFS clients have 
been rock solid. Not a single hang since but of course 100+MB of memory are 
'lost' now.
So is this problem still around or is it specific to Xeons?
Thanks

	JC



-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-07-11 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 14:49 Jean-Christophe Ducom [this message]
2003-07-11 18:26 ` NFS clients hang Trond Myklebust

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=3F0ECE77.1050703@nd.edu \
    --to=jducom@nd.edu \
    --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.