mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roy Keene <rkeene@psislidell.com>
To: linux-kernel@vger.kernel.org
Subject: Problem with 2.6 kernel and lots of I/O
Date: Tue, 31 May 2005 10:55:53 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0505311042470.7546@hammer.psislidell.com> (raw)

Hello,

 	I have a (well, at least one) show-stopping problems with the 2.6 
kernel while doing heavy I/O.  I have a (software) RAID1 of network block 
devices (nbd0 and nbd1) set up on two identical machines in an 
active-passive HA cluster configuration.  When the "primary" node goes 
down and comes back up it recovers the RAID as follows:

 	Start RAID in degraded mode with remote device (nbd1)
 	Hot-add local device (nbd0)

This all works.  Hot-adding the local device causes a resync and that is 
where the problems begin.  Once the resync begins the system becomes 
unusable.  Anything that wants to write something to the syslog socket 
("/dev/log") syncronously hangs until the resync completes.  The system 
load goes up to 18 or so.  Writing stuff to the local disk ("/etc" for 
example, which is not part of the RAID) sometimes hangs.  When the resync 
is complete everything is happy again.  Resyncing takes about 25 minutes 
(20GB over a dedicated network interface to the client at 1000Mbps) and 
makes the recovery time unacceptable.  Also, during this recovery the OOM 
killer will occasionally be invoked and kill something randomly even 
though there is typically plenty of unused swap lying around before 
(though perhaps "java" just decides to eat all of that VERY quickly and I 
don't notice this, since that is what the OOM killer choses to kill.)

Does anyone have any ideas ?


Information about the systems:

Info: Linux cog1 2.6.9-5.0.5.ELsmp #1 SMP Fri Apr 8 14:29:47 EDT 2005 i686 i686 i386 GNU/Linux
Dist: RedHat Enterprise Linux 4
Spec:
     2 x 3.2GHz Xeon (each system, with hyperthreading so 4 logical processors)
     4GB of physical RAM
     2GB of configured swap (partition, contigious)
     2 x 1000Mbps (Intel 82546GB) network cards (HA cluster link is
               provided by a cross over cable between the two nodes)

             reply	other threads:[~2005-05-31 15:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 15:55 Roy Keene [this message]
     [not found] ` <200505312040.30812.bernd-schubert@web.de>
2005-05-31 19:00   ` Roy Keene
2005-06-01  1:16     ` Kyle Moffett
2005-06-01 19:59 ` Pavel Machek
2005-06-05 10:11   ` Erik Slagter
2005-06-06  5:46     ` Kyle Moffett
2005-06-20 22:19       ` Roy Keene
2005-06-20 23:18         ` Kyle Moffett
2005-06-20 23:54           ` Roy Keene
2005-06-21  2:47             ` Kyle Moffett
2005-06-21  7:41             ` Pavel Machek
2005-06-21 14:23               ` Roy Keene
2005-05-31 16:12 Parag Warudkar

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=Pine.LNX.4.62.0505311042470.7546@hammer.psislidell.com \
    --to=rkeene@psislidell.com \
    --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

all inboxes | Powered by JetHome®