From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: memory leak in <=3.11.6
Date: Tue, 29 Oct 2013 16:42:23 +0000 (UTC) [thread overview]
Message-ID: <pan$d5444$ef292b25$154f150a$c91a6fe4@cox.net> (raw)
In-Reply-To: CALJXSJr0sjzFwCT=w1WdDX+-CWS-CjDhYBArVpvTeUNBM88Mdw@mail.gmail.com
Jérôme Poulin posted on Mon, 28 Oct 2013 23:24:10 -0400 as excerpted:
> On Mon, Oct 28, 2013 at 6:34 PM, Kai Krakow <hurikhan77+btrfs@gmail.com>
> wrote:
>>
>> If I close all my desktop programs, my system stays at +12 GB RAM usage
>> while after a fresh boot it has 12+ GB free (of 16 GB). Cache stays low
>> at 2 GB while after a few minutes uptime cache is about 5 GB.
>
> I probably have the same problem over here, after about 2 weeks of
> random read/write it seems my memory and swap get almost full and even
> after killing all process and getting in single user mode, memory won't
> free up. Would you happen to have quota enabled too? Kernel is 3.11.4
FWIW, seeing nothing like that here, no quota/qgroups enabled.
But there's definitely something not right with qgroups at this time.
First, a lot of folks with it enabled are reporting negative numbers
which shouldn't be there, and second, all or very nearly all the huge
memory usage issues reported seem to be from qgroups-enabled people.
So I'd call the qgroups feature broken at this time. Don't use it if you
can avoid it (but be aware that turning it off triggers the memory issue
and ultimate crashing for some, so preferably turn it off when you're
rebooting anyway), and if you really do need quotas for your use-case,
you may be better off on a non-btrfs filesystem for the time being.
(Of course btrfs is still listed as experimental in any case, so one
shouldn't be surprised if this sort of thing happens from time to time or
with some features.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-10-29 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 22:34 memory leak in <=3.11.6 Kai Krakow
2013-10-29 3:24 ` Jérôme Poulin
2013-10-29 16:42 ` Duncan [this message]
2013-10-29 22:46 ` Jérôme Poulin
2013-10-30 1:55 ` Wang Shilong
2013-10-29 23:26 ` Kai Krakow
-- strict thread matches above, loose matches on Subject: below --
2013-10-29 4:22 Tomasz Chmielewski
2013-10-29 23:30 ` Kai Krakow
2013-10-30 7:58 ` Duncan
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='pan$d5444$ef292b25$154f150a$c91a6fe4@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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 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).