From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Wang Shilong <wangshilong1991@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs qgroup assign -> "ERROR: bad relation requested"
Date: Wed, 31 Jul 2013 12:19:36 +0800 [thread overview]
Message-ID: <51F89058.6080101@cn.fujitsu.com> (raw)
In-Reply-To: <20130731104624.163d07d7@wpkg.org>
On 07/31/2013 11:46 AM, Tomasz Chmielewski wrote:
> On Tue, 30 Jul 2013 21:06:32 +0800
> Wang Shilong <wangshilong1991@gmail.com> wrote:
>
>> 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>
>
> Hmm, is it correct git URL?
I have tried it and it works, you can do like the following to try it.
#git clone http://github.com/miaoxie/btrfs-progs.git
#cd btrfs-progs
#git pull origin master
#make && make install
Thanks,
Wang
>
> # btrfs qgroup show -p /mnt/lxc2
> btrfs qgroup show: too many arguments
> usage: btrfs qgroup show <path>
>
> Show all subvolume quota groups.
>
>
>
next prev parent reply other threads:[~2013-07-31 4:20 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
2013-07-31 3:46 ` Tomasz Chmielewski
2013-07-31 4:19 ` Wang Shilong [this message]
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=51F89058.6080101@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=wangshilong1991@gmail.com \
/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).