linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suman Chakravartula <suman@rockstor.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: WARNING: quotas may be inconsistent, rescan needed
Date: Sun, 20 Mar 2016 09:58:11 -0700	[thread overview]
Message-ID: <CAPF83mscZt5SZMbweptCc_s5Fe6w9T=3Via0UZsoCiL-=ApbDg@mail.gmail.com> (raw)

Hello my dear upstream heroes,

We are using progs v4.4.1 and kernel 4.4.5 in Rockstor and sometimes
this warning is displayed while assigning a qgroup. Here's a sample
output.

/sbin/btrfs qgroup assign 0/408 2015/6 /mnt2/<btrfs_pool>
WARNING: quotas may be inconsistent, rescan needed

2015/6 is the qgroup of a subvolume(/mnt2/<btrfs_name>/<subvol_name>)
created much earlier.

This started happening since progs v4.2. There are three scenarios I've tested.

1. Just ignore the warning and check if the qgroup assignment
succeeded with a "qgroup show" command. In most cases, the assignment
shows up immediately. But it could take a bit in some cases. Is there
any self/auto consistency check that is triggered by default? If so
can someone explain how that works?

2. Add a --rescan option to to the "qgroup assign" command above to
auto schedule a rescan as per the man page. Is this safe to do? What
are pros and cons?

3. Execute a "quata rescan" separately if the warning is displayed. Is
this any different from (2)?

Thanks for reading!

-- 
Suman Chakravartula
Founder @ Rockstor

http://rockstor.com
http://rockstor.com/blog
http://forum.rockstor.com

                 reply	other threads:[~2016-03-20 16:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPF83mscZt5SZMbweptCc_s5Fe6w9T=3Via0UZsoCiL-=ApbDg@mail.gmail.com' \
    --to=suman@rockstor.com \
    --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).