linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Jens Axboe <axboe@suse.de>
Cc: Andy Chittenden <AChittenden@bluearc.com>,
	Andrew Morton <akpm@osdl.org>,
	davej@redhat.com, linux-kernel@vger.kernel.org,
	lwoodman@redhat.com
Subject: Re: Out of Memory: Killed process 16498 (java).
Date: Fri, 27 Jan 2006 14:39:57 +0000	[thread overview]
Message-ID: <1138372797.22112.44.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <20060127142146.GN4311@suse.de>

Hi,

On Fri, 2006-01-27 at 15:21 +0100, Jens Axboe wrote:
> On Fri, Jan 27 2006, Andy Chittenden wrote:
> > Any progress on a patch?
> 
> (please don't top post)
> 
> Not yet, sorry, been busy with more critical bugs.

A colleague has a server (which does backups) that is incapable of doing
a backup due to the backup process being killed due to OOM after
anywhere between 30s and a few minutes of running...  And the backup
process is just a simple program that does the equivalent of "dd with
one source but two destinations" where the source is an lvm/dm snapshot
and the two destinations are two different tape drives attached via
scsi.  That is pretty critical, admittedly only to us and that system...

This problem means the system has to sit with an older kernel until such
time as the problem is fixed.

ps. I have no idea if it is the same problem or not but it may well be.
It is a SUSE kernel (SLES9) rather than stock kernel and the problem was
experienced with the 2.6.5-7.202.7 kernel update...  Back to .151 the
system is doing backups just fine, no kernels between .151 and .202.7
have been tried yet on that system and neither has the latest .244
kernel.  We (for a rather all encompassing value of we) pretty much
stopped at .151 due to the e1000 problems in all later kernels although
now we know the magic workaround of disabling TSO people around are
happier to try using more recent kernels (and leaving TSO disabled as
even .244 is badly borked there as soon as you get some traffic load on
any of the e1000s)...

Best regards,

        Anton
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/


  reply	other threads:[~2006-01-27 14:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27 11:53 Out of Memory: Killed process 16498 (java) Andy Chittenden
2006-01-27 14:21 ` Jens Axboe
2006-01-27 14:39   ` Anton Altaparmakov [this message]
2006-02-03  9:20     ` adding swap workarounds oom - was: " Anton Altaparmakov
2006-02-03  9:26       ` Andrew Morton
2006-02-03 11:01         ` Anton Altaparmakov
2006-02-03 13:54           ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2006-01-23 10:03 Andy Chittenden
2006-01-23 10:11 ` Jens Axboe
2006-01-21 21:47 Andy Chittenden
2006-01-23  9:27 ` Jens Axboe
     [not found] <89E85E0168AD994693B574C80EDB9C27035561DE@uk-email.terastack.bluearc.com>
2006-01-20 17:39 ` Jens Axboe
     [not found] <89E85E0168AD994693B574C80EDB9C27035560E4@uk-email.terastack.bluearc.com>
2006-01-20 12:37 ` Larry Woodman
2006-01-19 15:11 Andy Chittenden
2006-01-19 19:48 ` Dave Jones
2006-01-19 22:15   ` Andrew Morton
2006-01-20  8:12     ` Jens Axboe
2006-01-20  8:23       ` Andrew Morton
2006-01-20 12:08         ` Jens Axboe
2006-01-20 12:17           ` Andrew Morton
2006-01-20 12:28             ` Jens Axboe
2006-01-20 12:51               ` Andrew Morton
2006-01-20  1:03   ` Andrew Morton
2006-01-20  1:28     ` Dave Jones
2006-01-20  1:49       ` Andrew Morton
2006-01-21 20:00         ` Dan Aloni
     [not found] <89E85E0168AD994693B574C80EDB9C2703555F8E@uk-email.terastack.bluearc.com>
2006-01-19  9:44 ` Andrew Morton
2006-01-19  9:40 Andy Chittenden
2006-01-19  9:41 ` Con Kolivas
2006-01-19  8:43 Andy Chittenden
2006-01-19  8:56 ` Andrew Morton
2006-01-19  9:36   ` Con Kolivas
2006-01-19 20:54 ` Martin Bligh

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=1138372797.22112.44.camel@imp.csi.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=AChittenden@bluearc.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwoodman@redhat.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;
as well as URLs for NNTP newsgroup(s).