All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Quota limit question
Date: Wed, 17 Dec 2014 11:13:28 +0000 (UTC)	[thread overview]
Message-ID: <pan$d0df9$15eccc0$adce85d2$8664a8de@cox.net> (raw)
In-Reply-To: 20141217011537.GA1114@anthem.async.com.br

Christian Robottom Reis posted on Tue, 16 Dec 2014 23:15:37 -0200 as
excerpted:

>     # btrfs qgroup limit 2000m 0/261 . && touch x
>     touch: cannot touch ‘x’: Disk quota exceeded
> 
> The strange thing is that it doesn't seem to be actually out of space:
> 
>     # btrfs qgroup show -p -r -e /var | grep 261
>     0/261    1111810048  391114752   2097152000  0          ---

>     # btrfs --version Btrfs v3.12
> 
>     # uname -a
>     Linux riff 3.13.0-43-generic #72-Ubuntu SMP
>     Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Does the problem still exist with a current 3.18 series kernel and 3.17 
series btrfs userspace?  The quota code in the versions you appear to be 
running had some (rather severe, quotes could go negative at times!) 
known bugs and was rewritten recently.  I don't use quotas here and don't 
know for sure whether the quota rewrite made it into kernel 3.17, but 
current 3.18 should have it, and current userspace is I believe 3.17.3, 
so you should consider upgrading it as well.

More in general, consider your use-case.  While btrfs is no longer the 
experimental filesystem it once was (tho the warnings weren't removed 
until after the old 3.12/3.13 you're running, AFAIK), it's still 
maturing, and running year-old code still means running code with bugs 
that are known and have been fixed for a year.  There's a place for being 
conservative and running old and known stable code, but btrfs is still 
young and maturing and doesn't match that use-case very well.  Either you 
need stable and mature and an equally stable and mature filesystem is a 
better fit, at least for a couple more years, or you want newer 
technology/code and running year-old stuff is behind the curve.  Either 
way, running year-old btrfs code, both kernel and userspace, doesn't make 
a lot of sense.  Perhaps in a couple years it will, after btrfs is more 
mature and stable and year-old code doesn't mean year-stale bugs, but not 
currently.

-- 
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


  reply	other threads:[~2014-12-17 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  1:15 Quota limit question Christian Robottom Reis
2014-12-17 11:13 ` Duncan [this message]
2014-12-23 20:36 ` Christian Robottom Reis
2014-12-24  3:52   ` Duncan
2015-03-06 21:44     ` Christian Robottom Reis
2015-03-10  8:41       ` Qu Wenruo
2015-03-10 11:03         ` Dongsheng Yang

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$d0df9$15eccc0$adce85d2$8664a8de@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.