From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs kernel warning
Date: Wed, 16 Sep 2015 04:09:02 +0000 (UTC) [thread overview]
Message-ID: <pan$35c0$ee8bc3de$636c8076$39ddea5d@cox.net> (raw)
In-Reply-To: 55F86784.6060707@gmail.com
Austin S Hemmelgarn posted on Tue, 15 Sep 2015 14:46:28 -0400 as
excerpted:
> On 2015-09-15 14:42, Tyler Williams wrote:
>> So I only had qgroups enabled because at some point it seemed like it
>> gave me the size of individual snapshots. Would it be likely that if I
>> just removed qgroups from that volume that would prevent that message
>> in the future?
>>
> Maybe, I'm not entirely certain if disabling qgroups on a volume removes
> the qgroup metadata, and if the metadata is still there, it might still
> cause issues. It's worth trying though because it shouldn't make
> anything worse than it already is.
Confirming the two-step, disabling unlikely to do it without removal...
I'm not a quota/qgroup user either, but FWIW, after someone else reported
problems (in that case, performance related) that I suspected were quota
related, as they ultimately turned out to be, he did say that simply
disabling quotas wasn't enough, he had to delete the quota tracking
metadata to eliminate the issue. Without personal btrfs quota feature
experience I can't supply details as to what that involves, but he did
specifically mention that simply disabling them didn't solve the problem,
while removing them did.
--
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
prev parent reply other threads:[~2015-09-16 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 18:13 btrfs kernel warning Tyler Williams
2015-09-15 18:32 ` Austin S Hemmelgarn
[not found] ` <CALq_kZGHM2D7-XhrMbkhik2Hn=CWJGPBjbGrJWqS32k7nQEZ3g@mail.gmail.com>
2015-09-15 18:46 ` Austin S Hemmelgarn
[not found] ` <CALq_kZEf9q9Lrbk32qKhdeuE4B=X2nah9Db9YmD6Y5Xk_Fg32w@mail.gmail.com>
2015-09-15 19:03 ` Austin S Hemmelgarn
2015-09-15 19:12 ` Tyler Williams
2015-09-16 4:09 ` Duncan [this message]
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$35c0$ee8bc3de$636c8076$39ddea5d@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).