From: Marc MERLIN <marc@merlins.org>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: "Andrew E. Mileski" <andrewm@isoar.ca>,
Duncan <1i5t5.duncan@cox.net>,
Russell Coker <russell@coker.com.au>,
Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs quotas related to OOM death problems on my 8GB server with both 3.15.1 and 3.14?
Date: Sun, 13 Jul 2014 19:43:02 -0700 [thread overview]
Message-ID: <20140714024302.GD17968@merlins.org> (raw)
In-Reply-To: <53C3341C.5090504@cn.fujitsu.com>
On Mon, Jul 14, 2014 at 09:36:28AM +0800, Qu Wenruo wrote:
> When you enable quota and create a subvolume, a qgroup(0/<subvol
> id>) will be created and bind to the newly created subvolume.
> But on the other hand, when you delete the subvolume, the qgroup
> will *not* be deleted automatically.
> So you need to remove the qgroup manually.
>
> More info can be found in the btrfs wiki:
> https://btrfs.wiki.kernel.org/index.php/Quota_support#Known_issues
This was updated since I last looked at it, thanks for pointing that
out.
So there must be a leak that is related to how many qtrees you have.
Because even if I had 1600 qtrees, that shouldn't slowly eat up 6GB of
RAM, correct?
That said, I'll try the memleak detector you pointed me to, and read up
on how it's supposed to work.
Thanks for your help,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-07-14 2:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 1:19 Is btrfs related to OOM death problems on my 8GB server with both 3.15.1 and 3.14? Marc MERLIN
2014-07-04 4:33 ` Russell Coker
2014-07-04 6:04 ` Marc MERLIN
2014-07-04 6:23 ` Satoru Takeuchi
2014-07-04 14:24 ` Marc MERLIN
2014-07-04 14:45 ` Russell Coker
2014-07-04 15:07 ` Marc MERLIN
2014-07-04 22:13 ` Duncan
2014-07-05 13:47 ` Andrew E. Mileski
2014-07-05 14:43 ` Marc MERLIN
2014-07-05 15:17 ` Andrew E. Mileski
2014-07-06 14:58 ` Marc MERLIN
2014-07-13 14:29 ` btrfs is " Marc MERLIN
2014-07-13 15:37 ` Marc MERLIN
2014-07-13 15:45 ` btrfs quotas " Marc MERLIN
2014-07-14 1:36 ` Qu Wenruo
2014-07-14 2:43 ` Marc MERLIN [this message]
2014-07-14 1:24 ` btrfs is " Qu Wenruo
2014-07-16 0:36 ` Jérôme Poulin
2014-07-16 15:55 ` Marc MERLIN
2014-07-17 2:22 ` Marc MERLIN
2014-07-16 0:45 ` Is btrfs " Jérôme Poulin
2014-07-05 14:27 ` Andrew E. Mileski
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=20140714024302.GD17968@merlins.org \
--to=marc@merlins.org \
--cc=1i5t5.duncan@cox.net \
--cc=andrewm@isoar.ca \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=russell@coker.com.au \
--cc=takeuchi_satoru@jp.fujitsu.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).