From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: Arne Jansen <sensille@gmx.net>
Subject: Re: Heavy memory leak when using quota groups
Date: Wed, 7 Aug 2013 16:00:27 +0800 [thread overview]
Message-ID: <20130807160027.188b340b@wpkg.org> (raw)
In-Reply-To: <20130807004227.6b2b688e@wpkg.org>
On Wed, 7 Aug 2013 00:42:27 +0800
Tomasz Chmielewski <mangoo@wpkg.org> wrote:
> > 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.
I keep removing the files, and memory usage has grown to 28 GB (out of
32 GB).
Is there anything I can debug at this point?
# free
total used free shared buffers cached
Mem: 32638512 32476992 161520 0 732 3531152
-/+ buffers/cache: 28945108 3693404
Swap: 16776116 173392 16602724
# cat /proc/meminfo
MemTotal: 32638512 kB
MemFree: 163364 kB
Buffers: 864 kB
Cached: 3531940 kB
SwapCached: 60992 kB
Active: 3599804 kB
Inactive: 2422176 kB
Active(anon): 1860412 kB
Inactive(anon): 629848 kB
Active(file): 1739392 kB
Inactive(file): 1792328 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 16776116 kB
SwapFree: 16602916 kB
Dirty: 85432 kB
Writeback: 10320 kB
AnonPages: 2458792 kB
Mapped: 11068 kB
Shmem: 796 kB
Slab: 3168820 kB
SReclaimable: 3099388 kB
SUnreclaim: 69432 kB
KernelStack: 3408 kB
PageTables: 14764 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 33095372 kB
Committed_AS: 4301988 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 130036 kB
VmallocChunk: 34359595900 kB
HardwareCorrupted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 12520 kB
DirectMap2M: 33220608 kB
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2013-08-07 8:00 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
2013-08-07 8:00 ` Tomasz Chmielewski [this message]
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=20130807160027.188b340b@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 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.