From: Tim Walberg <twalberg@comcast.net>
To: Rakesh Sankeshi <rakesh.sankeshi@gmail.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs quota issues
Date: Tue, 16 Aug 2016 19:09:35 -0500 [thread overview]
Message-ID: <20160817000935.GF2367@comcast.net> (raw)
In-Reply-To: <CAGj_d3C9274iWJN4vqPLamsEeO+ndPcnSefD-q-PA63ToeLBrw@mail.gmail.com>
On 08/16/2016 16:33 -0700, Rakesh Sankeshi wrote:
>> also is there any timeframe on when the qgroup / quota issues would be
>> stabilized in btrfs?
>>
>> Thanks!
This may or may not be of interest to you, but for the record, since at least
linux 4.2, I've had pretty good luck with what I'd loosely call "non-enforcing
quotas" with btrfs - i.e. qgroups enabled so that you can actually track usage,
but no limits set, so none of the "deny allocation" logic ever gets hit. It's
understandably not the desired end-state - I still have to use daily reports
and manual enforcement to keep things in balance, but it's better than not
being able to use them at all, especially with the other benefits btrfs brings
to the table. If you really need the enforcement, I'm afraid a different FS
is the best option right now...
--
twalberg@gmail.com
next prev parent reply other threads:[~2016-08-17 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 17:32 btrfs quota issues Rakesh Sankeshi
2016-08-11 19:13 ` Duncan
2016-08-12 15:47 ` Rakesh Sankeshi
2016-08-13 23:05 ` Duncan
2016-08-15 2:11 ` Qu Wenruo
2016-08-15 19:11 ` Rakesh Sankeshi
2016-08-16 1:01 ` Qu Wenruo
2016-08-16 16:05 ` Rakesh Sankeshi
2016-08-16 23:33 ` Rakesh Sankeshi
2016-08-17 0:09 ` Tim Walberg [this message]
2016-08-17 0:56 ` Qu Wenruo
2016-08-23 18:38 ` Rakesh Sankeshi
2016-08-26 1:52 ` Qu Wenruo
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=20160817000935.GF2367@comcast.net \
--to=twalberg@comcast.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=rakesh.sankeshi@gmail.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).