From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/7] btrfs-progs: qgroup related enhance.
Date: Tue, 24 Mar 2015 08:36:33 +0800 [thread overview]
Message-ID: <5510B191.1010402@cn.fujitsu.com> (raw)
In-Reply-To: <20150323233803.GP20767@twin.jikos.cz>
-------- Original Message --------
Subject: Re: [PATCH 0/7] btrfs-progs: qgroup related enhance.
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Date: 2015年03月24日 07:38
> On Fri, Feb 27, 2015 at 04:26:32PM +0800, Qu Wenruo wrote:
>> Qu Wenruo (7):
>> btrfs-progs: Update qgroup status flags and replace qgroup
>> level/subvid calculation with inline function.
>> btrfs-progs: Allow btrfs-debug-tree to print human readable qgroup
>> status flag.
>> btrfs-progs: Move parse_qgroupid() to utils.c
>> btrfs-progs: Allow parse_qgroupid() to resolve subvolume path into
>> qgroupid.
>> btrfs-progs: Add stack get/set functions for btrfs_qgroup_status_item.
>> btrfs-progs: Print warning message if qgroup data is inconsistent.
>
> All of the above merged.
>
>> btrfs-progs: Schedule quota rescan if qgroup assign caused
>> inconsistence.
>
> The rescan can be a long running operation and touches a lot of
> metadata, so I'd rather avoid starting the rescan automatically. Right
> now the user may start rescan manually, or please add an commandline
> option (eg. --rescan) to do the rescan in one go with the 'assign'
> command. Thanks.
>
Makes sense, I'll update the last patch soon.
Thanks,
Qu
next prev parent reply other threads:[~2015-03-24 0:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 8:26 [PATCH 0/7] btrfs-progs: qgroup related enhance Qu Wenruo
2015-02-27 8:26 ` [PATCH 1/7] btrfs-progs: Update qgroup status flags and replace qgroup level/subvid calculation with inline function Qu Wenruo
2015-02-27 8:26 ` [PATCH 2/7] btrfs-progs: Allow btrfs-debug-tree to print human readable qgroup status flag Qu Wenruo
2015-02-27 8:26 ` [PATCH 3/7] btrfs-progs: Move parse_qgroupid() to utils.c Qu Wenruo
2015-02-27 8:26 ` [PATCH 4/7] btrfs-progs: Allow parse_qgroupid() to resolve subvolume path into qgroupid Qu Wenruo
[not found] ` <B6A95DD2-413F-4C43-8A9B-048713D62BCC@gmail.com>
2015-02-27 8:51 ` Qu Wenruo
2015-02-27 8:26 ` [PATCH 5/7] btrfs-progs: Add stack get/set functions for btrfs_qgroup_status_item Qu Wenruo
2015-02-27 8:26 ` [PATCH 6/7] btrfs-progs: Print warning message if qgroup data is inconsistent Qu Wenruo
2015-05-30 11:39 ` Filipe David Manana
2015-06-01 0:31 ` Qu Wenruo
2015-06-01 1:25 ` Qu Wenruo
2015-06-01 7:49 ` Filipe David Manana
2015-06-03 7:10 ` [PATCH] xfstests: btrfs: 022: add a quota rescan -w to wait rescan finished Dongsheng Yang
2015-06-03 7:12 ` Dongsheng Yang
2015-06-03 15:53 ` Filipe David Manana
2015-02-27 8:26 ` [PATCH 7/7] btrfs-progs: Schedule quota rescan if qgroup assign caused inconsistence Qu Wenruo
2015-03-23 23:38 ` [PATCH 0/7] btrfs-progs: qgroup related enhance David Sterba
2015-03-24 0:36 ` Qu Wenruo [this message]
2015-07-27 14:35 ` David Sterba
2015-07-28 0:25 ` 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=5510B191.1010402@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--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).