From: Martin Knoblauch <knobi@knobisoft.de>
To: linux-kernel@vger.kernel.org
Subject: File-locking problems with RHEL4 kernel (2.6.9-42.0.3.ELsmp) under high load
Date: Mon, 27 Nov 2006 04:45:55 -0800 (PST) [thread overview]
Message-ID: <892617.7429.qm@web32615.mail.mud.yahoo.com> (raw)
Hi,
first of all, yes - I know that this kernel is very old and it is not
an official LKML kernel. No need to tell me, no need to waste bandwidth
by telling me :-) I just post here, because I got no response
"elsewhere".
Second - please CC me on any reply, as I am not subscribed.
OK. Here is the problem. Said RHEL4 kernel seems to have problems with
file-locking when the system is under high, likely network related,
load. The symptoms are things using file locking (rpm, the user-space
automounter amd) fail to obtain locks, usually stating timeout
problems.
The sytem in question is a HP/DL380G4 with dual-single-core EM64T CPUs
and 8GB of Memory. The network interfaces are "tg3".
The high load can be triggered by copying three 3 GB files in parallel
from an NFS server (Solaris10, NFS, TCP, 1GBit) to another NFS server
(RHEL4, NFS, TCP, 100 MBit). The measured network performance is OK.
During this operation the systems goes to Loads around/above 10.
Overall responsiveness feels good, but software doing file-locking or
opening a new ssh connection take extremely long.
So, if anyone has an idea or hint, it will be highly appreciated.
Cheers
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
reply other threads:[~2006-11-27 12:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=892617.7429.qm@web32615.mail.mud.yahoo.com \
--to=knobi@knobisoft.de \
--cc=linux-kernel@vger.kernel.org \
/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