From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Arne Jansen <sensille@gmx.net>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Heavy memory leak when using quota groups
Date: Wed, 7 Aug 2013 00:42:27 +0800 [thread overview]
Message-ID: <20130807004227.6b2b688e@wpkg.org> (raw)
In-Reply-To: <5200888A.4030109@gmx.net>
On Tue, 06 Aug 2013 07:24:26 +0200
Arne Jansen <sensille@gmx.net> wrote:
> On 05.08.2013 18:35, Tomasz Chmielewski wrote:
> >> I am trying to use qgroups
> >> functionality & with a basic random-write workload, it constantly
> >> keeps leaking memory & within few minutes of IO, there is either
> >> out-of-memory killer trying to kill some tasks or there are
> >> page-allocation failures that btrfs or other kernel module
> >> experiences.
> >
> > FYI, I just saw something similar with 3.10 on a server with 32 GB
> > RAM:
> >
> > The result was a frozen server and a need to hard reset.
> >
>
> What do I have to do to reproduce it here? How do you generate the
> load? What is the disk setup, what the qgroups setup?
Unfortunately I don't have a way to reproduce, as the issue
happened to me only once.
Server uptime was about 2 weeks, and there were millions of files with
multiple hardlinks on disk (backuppc archive copied from ext4 to
btrfs). Then, "rm" command was running for many days, about 5 times in
parallel, and many other rsync commands, with snapshots being added and
removed.
When I saw the issue I looked up in btrfs list archives that there was
a similar report in the past - but I doubt I will be able to find a
reliable way to reproduce this.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2013-08-06 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 16:35 Heavy memory leak when using quota groups Tomasz Chmielewski
2013-08-05 23:29 ` Wang Shilong
2013-08-06 2:57 ` Tomasz Chmielewski
2013-08-06 5:24 ` Arne Jansen
2013-08-06 16:42 ` Tomasz Chmielewski [this message]
2013-08-07 8:00 ` Tomasz Chmielewski
2013-08-08 3:52 ` Jérôme Poulin
[not found] <CAGEjNMfpTD3wMsagrFYinuJj0ieT8+g66uVz_hFpgp=1j4hYFQ@mail.gmail.com>
2013-02-12 7:31 ` shyam btrfs
2013-02-13 8:49 ` Arne Jansen
2013-02-13 9:10 ` shyam btrfs
2013-02-13 9:41 ` Arne Jansen
2013-02-13 11:22 ` Arne Jansen
2013-02-15 4:34 ` shyam btrfs
2013-02-27 7:42 ` Arne Jansen
2013-02-28 10:10 ` shyam btrfs
2013-02-13 8:40 ` Arne Jansen
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=20130807004227.6b2b688e@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=sensille@gmx.net \
/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).