From: Wang Shilong <wangshilong1991@gmail.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs qgroup assign -> "ERROR: bad relation requested"
Date: Tue, 30 Jul 2013 21:06:32 +0800 [thread overview]
Message-ID: <3C9EC4DB-0B63-49A8-B53C-24E162CB8FEF@gmail.com> (raw)
In-Reply-To: <20130730192525.42725e74@wpkg.org>
Hello,
> On Sun, 28 Jul 2013 15:36:41 +0800
> Wang Shilong <wangshilong1991@gmail.com> wrote:
>
>> Btrfs group assign requires parent's level > children's level, For
>> your example below, you can do like:
>>
>> btrfs qgroup create 1/1 <mnt>
>> btrfs qgroup assign 1177 1/1 <mnt>
>> btrfs qgroup assign 1178 1/1 <mnt>
>
> Cool, thanks.
>
> And is it possible (i.e. at some later point) to verify that 1177, 1178
> were assigned to 1/1 (or in general, what is assigned to 1/1)?
I have implemented the above function, but they haven't gone into upstream
Btrfs-progs.
You can try this:
http://github.com/miaoxie/btrfs-progs.git qgroup
Maybe i need rebase the patch-set later, But you can try it firstly, if you want to see
every qgroup's parent, you can add option '-p':
btrfs qgroup show -p <mnt>
If you want to see what is assigned to 1/1, you can use:
btrfs group show -c <mnt>
Further, if you want to see a specified path's parent qgroup, you can use it:
btrfs group show -F/-f <path>
Also '-l' and '-e' print limit size of qgroup.
Thanks,
Wang
>
>
> --
> Tomasz Chmielewski
> http://wpkg.org
>
next prev parent reply other threads:[~2013-07-30 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 6:51 btrfs qgroup assign -> "ERROR: bad relation requested" Tomasz Chmielewski
2013-07-28 7:36 ` Wang Shilong
2013-07-30 12:25 ` Tomasz Chmielewski
2013-07-30 13:06 ` Wang Shilong [this message]
2013-07-31 3:46 ` Tomasz Chmielewski
2013-07-31 4:19 ` Wang Shilong
2013-07-31 4:36 ` Tomasz Chmielewski
2013-07-31 5:13 ` Wang Shilong
2013-07-31 5:39 ` Tomasz Chmielewski
2013-07-31 6:08 ` Wang Shilong
2013-08-02 6:32 ` Arne Jansen
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=3C9EC4DB-0B63-49A8-B53C-24E162CB8FEF@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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).