From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Question about btrfs as root filesystem
Date: Fri, 8 Nov 2013 09:39:18 +0000 (UTC) [thread overview]
Message-ID: <pan$660$fa62c2d3$5e9643e4$83687499@cox.net> (raw)
In-Reply-To: 5eb6a9cbd3a163b70c9cfe4a1b46a1fa@myjm.de
Michael Göhler posted on Fri, 08 Nov 2013 00:45:32 +0100 as excerpted:
> The use case for that is to set quotas for the child subvolumes.
Quite apart from the main thread subject, you're aware that there are
major bugs with btrfs quotas/qgroups ATM, right? I'd certainly be wary
of depending on them for anything at the distribution level you're
discussing.
The known quota bugs appear to be in two areas and may or may not be
related. First, people have been complaining about huge and unaccounted
memory usage on the order of multiple gigabytes while using quotas. I
believe one related memory leak has recently been fixed (tho I'm not sure
the fix is actually in mainline yet, it's that new), but there could well
be more.
Second, people are reporting negative quota numbers. Apparently this is
the result of deleting snapshots or turning off qgroups on some
subvolumes/snapshots but not others and goes away when the quotas are
fully rescanned, but that's a time-intensive process on multi-terabyte
spinning rust partitions. Again, there's work being done to address the
issue, but it's nothing I'd want to rely on at this point.
Given the above situation, I'd strongly suggest leaving the quota feature
off on btrfs at this point, certainly at the distro level. If
individuals want to test it that's fine, as long as they know the risk
(which given that btrfs itself remains officially experimental, is simply
a known stronger area of the risk that continues to apply to testing
btrfs as a whole), but I'd argue it's inappropriate for distro level at
this point. If quotas are dictated by the use-case, there are other more
stable filesystem options available with stable quota support.
--
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-11-08 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 23:45 Question about btrfs as root filesystem Michael Göhler
2013-11-08 1:33 ` Chris Murphy
2013-11-08 13:41 ` Michael Göhler
2013-11-08 19:30 ` Chris Murphy
2013-11-08 9:39 ` Duncan [this message]
2013-11-08 12:55 ` R: " Goffredo Baroncelli <kreijack@libero.it>
2013-11-08 17:44 ` Chris Murphy
2013-11-08 17:59 ` Goffredo Baroncelli
2013-11-08 19:43 ` Chris Murphy
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$660$fa62c2d3$5e9643e4$83687499@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 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.