On Thu, Sep 1, 2016 at 7:21 AM, Austin S. Hemmelgarn <ahferro...@gmail.com> wrote:
> Yes, you can just run `btrfs quota disable /` and it should work. This > ironically reiterates that one of the bigger problems with BTRFS is that > distros are enabling unstable and known broken features by default on > install. I was pretty much dumbfounded when I first learned that OpenSUSE > is enabling BTRFS qgroups by default since they are known to not work > reliably and cause all kinds of issues. Yes, I've just confirmed this on the OpenSUSE Factory mailing list. [1] This is default on Tumbleweed (devel) and Leap (stable), and also SLE 12 SP2. The feature that depends on it, that's actually enabling it is snapper: http://snapper.io/2016/05/18/space-aware-cleanup.html That feature says "btrfs quota support looks mature enough" which is big news to me. If it's that mature, why not make it the mkfs default? Just turn it on for everyone out of the gate? And if it isn't that mature, is it really appropriate for broad, by default, silent deployment for opensuse stable, and SUSE enterprise? I'm surprised no one said on this list that qgroups were stable enough for widespread testing for list regulars first. It just suddenly ends up enabled across three major distro outputs? Even the fucking error messages were misleading. It wasn't until the most recent call trace that qgroups was even considered as possibly being related to this. How is it that busting a quota limit doesn't cause a very explicit quota related message, rather than a generic enospc? [1] https://lists.opensuse.org/opensuse-factory/2016-09/msg00033.html -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
