All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henry <henry@borg.metroweb.co.za>
To: linux-kernel@vger.kernel.org
Subject: Re: OOPS (kswapd) in 2.4.5 and 2.4.6
Date: Fri, 6 Jul 2001 07:59:22 +0200	[thread overview]
Message-ID: <01070608100801.13482@borg> (raw)
In-Reply-To: <01070516412506.06182@borg> <200107051653.f65GrC400989@adsl-209-76-109-63.dsl.snfc21.pacbell.net> <01070519204000.13482@borg>
In-Reply-To: <01070519204000.13482@borg>

> > 
> > FYI, I see a similar problem under 2.4.5, also SMP, although only
> > intermittently.  Two oopses are below, from two different, although
> > similarly configured, machines.
> 
> [snip]
> 
> Sounds very similar.  Our servers are all identical (except for RAM).
> 
> What's unusual is that the machines we *expect* to fail sooner - don't
> (not even an oops).  Those are very busy cache servers (several of them
> in a sibling cluster) which do a lot of swapping.  The machines which
> *do* fail (or oops without any further catastrophe) are typically
> web/mail hosting servers (reasonably busy with about 25% swap being
> used).  Increasing swap did not help on 2.4.5.  We're still waiting for
> something to happen on 2.4.6 (ie, oops already appeared - waiting for
> meltdown, which, hopefully, will not occur).  We used to auto-reboot
> every morning at 2am or something to keep things stable - which I
> *hate* because I remember having a 2.0.35/6 workstation that had an
> uptime of 6 months a couple of years ago.  God, I loved that box.
> 

It's happened again.  The server which previously failed with memory
errors, has failed again and required a reboot.  It was using 26% swap,
and apache would fail to start with 'semget: No space left on device'. 
What we also noticed was that the kswapd process showed 'defunct' on
ps...  mean anything to anyone?

Regards
Henry


  reply	other threads:[~2001-07-06  6:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05 14:03 OOPS (kswapd) in 2.4.5 and 2.4.6 Henry
2001-07-05 16:53 ` Wayne Whitney
2001-07-05 17:09   ` Henry
2001-07-06  5:59     ` Henry [this message]
2001-07-06  8:35 ` Andrew Morton
2001-07-06 10:31   ` Henry
2001-07-07  6:03   ` Henry
2001-07-07  8:07     ` Andrew Morton
2001-07-07  9:33       ` Henry
2001-07-07  9:54         ` Andrew Morton
2001-07-08 11:08           ` Henry

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=01070608100801.13482@borg \
    --to=henry@borg.metroweb.co.za \
    --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 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.