public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Laurent Caron <lcaron@lncsa.fr>
Cc: drbd-user@linbit.com, xfs@oss.sgi.com
Subject: Re: Crash with XFS on top of DRBD (DRBD 8.0.6 svn / Kernel 2.6.22)
Date: Tue, 30 Oct 2007 08:10:22 +1100	[thread overview]
Message-ID: <20071029211021.GK995458@sgi.com> (raw)
In-Reply-To: <20071029101329.ietaisee@trusted.lncsa.com>

On Mon, Oct 29, 2007 at 10:14:19AM +0100, Laurent Caron wrote:
> Hi,
> 
> I'm back with my crash, oomkiller..... problems on my DRBD cluster of 2
> servers.
> 
> I compiled a 2.6.22 kernel with slab/slab debugging turned on.
> 
> Here is the last oom-killer message I got on that server.

You ran out of low memory. Slab didn't use it all, so I'm not
sure what would be using it. You should post OOM invokations
to LKML. Given DRDB is te unusual thing your are using, I'd
be looking there first...

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

      reply	other threads:[~2007-10-29 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29  9:14 Crash with XFS on top of DRBD (DRBD 8.0.6 svn / Kernel 2.6.22) Laurent Caron
2007-10-29 21:10 ` David Chinner [this message]

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=20071029211021.GK995458@sgi.com \
    --to=dgc@sgi.com \
    --cc=drbd-user@linbit.com \
    --cc=lcaron@lncsa.fr \
    --cc=xfs@oss.sgi.com \
    /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