All of lore.kernel.org
 help / color / mirror / Atom feed
From: cwillu <cwillu@cwillu.com>
To: Stephane Chazelas <stephane_chazelas@yahoo.fr>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Memory leak?
Date: Sun, 3 Jul 2011 13:38:57 -0600	[thread overview]
Message-ID: <CAE5mzvhZc4afuBTT0GrDvPXKaSwYeyPdyiQaYPjCTmvzBahr7g@mail.gmail.com> (raw)
In-Reply-To: <20110703190913.GA4474@yahoo.fr>

On Sun, Jul 3, 2011 at 1:09 PM, Stephane Chazelas
<stephane_chazelas@yahoo.fr> wrote:
> Hiya,
>
> I've got a server using brtfs to implement a backup system.
> Basically, every night, for a few machines, I rsync (and other
> methods) their file systems into one btrfs subvolume each and
> then snapshot it.
>
> On that server, the btrfs fs is on 3 3TB drives, mounted with
> compress-force. Every week, I rsync the most recent snapshot of
> a selection of subvolumes onto an encrypted (LUKS) external hard
> drive (3TB as well).
>
> Now, on a few occasions (actually, most of the time), when I
> rsynced the data (about 2.5TB) onto the external drive, the
> system would crash after some time with "Out of memory and no
> killable process". Basically, something in kernel was allocating
> the whole memory, then oom mass killed everybody and crash.
>
> That was with ubuntu 2.6.38. I had then moved to debian and
> 2.6.39 and thought the problem was fixed, but it just happened
> again with 3.0.0rc5 while rsyncing onto an initially empty btrfs
> fs.
>
> I'm going to resume the rsync again, and it's likely to happen
> again. Is there anything simple (as I've got very little time to
> look into that) I could do to help debug the issue (I'm not 100%
> sure it's btrfs fault but that's the most likely culprit).
>
> For a start, I'll switch the console to serial, and watch
> /proc/vmstat. Anything else I could do?
>
> Note that that server has never crashed when doing a lot of IO
> at the same time in a lot of subvolumes with remote hosts. It's
> only when copying data to that external drive on LUKS that it
> seems to crash.

Look at the output of slabtop (should be installed by default, procfs
package), before rsync for comparison, and during.

  reply	other threads:[~2011-07-03 19:38 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03 19:09 Memory leak? Stephane Chazelas
2011-07-03 19:38 ` cwillu [this message]
2011-07-06  8:11   ` Stephane Chazelas
2011-07-07  8:09     ` Stephane Chazelas
2011-07-07  8:20       ` Li Zefan
2011-07-07  8:37         ` Stephane Chazelas
2011-07-08 12:44     ` Stephane Chazelas
2011-07-08 15:06       ` Chris Mason
2011-07-08 15:41         ` Stephane Chazelas
2011-07-08 16:11           ` Stephane Chazelas
2011-07-08 16:17             ` Chris Mason
2011-07-08 16:57               ` Stephane Chazelas
2011-07-09 17:11               ` Stephane Chazelas
2011-07-08 16:15           ` Chris Mason
2011-07-08 17:06             ` Stephane Chazelas
2011-07-08 20:04             ` Stephane Chazelas
2011-07-08 20:12               ` Chris Mason
2011-07-09  7:09                 ` Stephane Chazelas
2011-07-09  7:42                   ` A lot of writing to FS only read (Was: Memory leak?) Stephane Chazelas
2011-07-10  5:58                   ` Memory leak? Stephane Chazelas
2011-07-09 17:09         ` Stephane Chazelas
2011-07-09 19:25           ` cwillu
2011-07-09 20:36             ` Stephane Chazelas
2011-07-10 12:44               ` Chris Mason
2011-07-10 18:37                 ` Stephane Chazelas
2011-07-11  9:01                   ` Stephane Chazelas
2011-07-11 15:00                     ` Chris Mason
2011-07-11 15:35                       ` Stephane Chazelas
2011-07-11 16:25                         ` Chris Mason
2011-07-11 16:34                           ` Stephane Chazelas
2011-07-12 11:40                     ` Stephane Chazelas
2011-07-16 12:12                     ` write(2) taking 4s. (Was: Memory leak?) Stephane Chazelas
2011-07-16 16:22                       ` Stephane Chazelas
2011-07-17  9:17                       ` Stephane Chazelas
2011-07-18 10:39                         ` write(2) taking 4s Stephane Chazelas
2011-07-18 19:37                           ` Stephane Chazelas
2011-07-19  9:32                             ` Stephane Chazelas
  -- strict thread matches above, loose matches on Subject: below --
2015-08-10 12:57 memory leak ? Pankaj Pandey
2015-08-10 13:04 ` Javier Martinez Canillas
2011-01-21 12:39 Memory leak? Damnshock
2011-01-21 12:52 ` Chris Wilson
2011-01-21 14:22   ` Damnshock
2008-02-07 11:44 memory leak? Gergely Gábor
2003-11-04 17:01 Memory leak? Daniel Chemko
     [not found] <20031103142830.14782.87331.Mailman@netfilter-sponsored-by.noris.net>
2003-11-04 14:49 ` Michael Friedhoff
2003-11-04 22:18   ` Alistair Tonner
2003-11-07 16:53   ` Harald Welte
2002-07-21 14:00 memory leak? Måns Rullgård
2002-07-21 14:19 ` Rik van Riel
2002-07-21 14:23   ` Måns Rullgård
2002-07-21 16:33     ` Alan Cox
2002-07-21 20:48       ` Måns Rullgård
2002-07-21 21:08         ` Rik van Riel
2002-07-30 16:08           ` Bill Davidsen
2002-07-30 16:43             ` Rik van Riel
2002-07-22 14:08 ` Andrew Rodland
2002-07-21 14:19   ` Måns Rullgård
2002-07-21 14:20   ` Martin Josefsson
2002-07-21 22:27     ` Stephan Maciej
2002-07-22 14:26     ` Andrew Rodland
2002-07-21 14:50       ` Rik van Riel

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=CAE5mzvhZc4afuBTT0GrDvPXKaSwYeyPdyiQaYPjCTmvzBahr7g@mail.gmail.com \
    --to=cwillu@cwillu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stephane_chazelas@yahoo.fr \
    /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.