From: Wang Shilong <wangsl-fnst@cn.fujitsu.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [PATCH 1/2] Btrfs: rescan for qgroups
Date: Mon, 15 Apr 2013 14:08:40 +0800 [thread overview]
Message-ID: <516B9968.90701@cn.fujitsu.com> (raw)
In-Reply-To: <516B9701.9040409@jan-o-sch.net>
Hello Jan,
> On Mon, April 15, 2013 at 07:44 (+0200), Jan Schmidt wrote:
>> Thanks, v2 to come.
>
> Uh, but not immediately. I didn't get tracking of "exclusive" right. That will
> need some time to fix and test.
'exclusive' adds the complexity of btrfs qgroup.
So if you send V2. I'd like you add more lines in changelog.
Besides, i have a question in my mind.(I have not seen you code)..
When qgroup rescan will happen?
1> when quota is enabled
2> if a new qgroup relations is created, rescan should happen?
2> user call qgroup rescan..
Thanks,
Wang
>
> -Jan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2013-04-15 6:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 11:38 [PATCH 0/2] Btrfs: quota rescan for 3.10 Jan Schmidt
2013-04-05 11:38 ` [PATCH 1/2] Btrfs: rescan for qgroups Jan Schmidt
2013-04-05 13:05 ` Josef Bacik
2013-04-10 16:14 ` David Sterba
2013-04-10 16:47 ` David Sterba
2013-04-15 5:44 ` Jan Schmidt
2013-04-15 5:58 ` Jan Schmidt
2013-04-15 6:08 ` Wang Shilong [this message]
2013-04-15 6:56 ` Jan Schmidt
2013-04-15 7:19 ` Wang Shilong
2013-04-15 10:53 ` Arne Jansen
2013-04-05 11:38 ` [PATCH 2/2] Btrfs: automatic rescan after "quota enable" command Jan Schmidt
2013-04-05 12:30 ` Wang Shilong
2013-04-06 6:20 ` [PATCH 0/2] Btrfs: quota rescan for 3.10 Wang Shilong
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=516B9968.90701@cn.fujitsu.com \
--to=wangsl-fnst@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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.