From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs quota issues
Date: Thu, 11 Aug 2016 19:13:35 +0000 (UTC) [thread overview]
Message-ID: <pan$302f2$7d1c6375$718b454d$bb3a6a2@cox.net> (raw)
In-Reply-To: CAGj_d3D2OZt2nY622rp9NzxgAfKZ2iN1kLSQ2Ras-0fM+1+-ig@mail.gmail.com
Rakesh Sankeshi posted on Thu, 11 Aug 2016 10:32:03 -0700 as excerpted:
> I set 200GB limit to one user and 100GB to another user.
>
> as soon as I reached 139GB and 53GB each, hitting the quota errors.
> anyway to workaround quota functionality on btrfs LZO compressed
> filesystem?
The btrfs quota subsystem remains somewhat buggy and unstable. A lot of
work has gone into it to fix the problems, including rewrites of the
entire subsystem, and it's much better than it used to be, but it's still
a feature that I would recommend not using on btrfs.
My general position is this. Either you need quotas for your use-case or
you don't. If you truly need them, you're far better off using a more
mature filesystem with proven quota subsystem reliability. If you don't
really need them, simply keep the feature off for now, and for however
long it takes to stabilize the feature, which could be some time.
Of course if you're specifically testing quotas in ordered to report
issues and test bugfixes, that's a specific case of needing quota
functionality, and your work is greatly appreciated as it'll help to
eventually make that feature stable and workable for all. =:^)
--
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:[~2016-08-11 19:13 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 [this message]
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
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='pan$302f2$7d1c6375$718b454d$bb3a6a2@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).