From: Arne Jansen <sensille@gmx.net>
To: Tomasz Chmielewski <tch@virtall.com>
Cc: linux-btrfs@vger.kernel.org, Jan Schmidt <list.btrfs@jan-o-sch.net>
Subject: Re: btrfs quota examples?
Date: Fri, 02 Aug 2013 08:23:21 +0200 [thread overview]
Message-ID: <51FB5059.1080406@gmx.net> (raw)
In-Reply-To: <20130729150510.19e5886a@virtall.com>
On 07/29/13 10:05, Tomasz Chmielewski wrote:
> On Mon, 10 Jun 2013 09:41:39 +0200
> Arne Jansen <sensille@gmx.net> wrote:
>
>>> Now, my questions:
>>>
>>> - what do both 104882176 104882176 numbers represent?
>>
>> The first number represents the amount of data in that subvolume,
>> regardless whether that data is shared with other subvolumes or
>> not.
>> The second number shows the amount of data that is unique to this
>> subvolume and not shared with others, i.e. the amount of space
>> that will get freed if you delete this subvolume.
>
> I've played with qgroups for some time, but the results are rather
> inconsistent.
>
> I.e. here - what does a negative number represent in 0/1181 row?
Either you have turned on qgroups after filling the subvol with
some data, or you've managed to produce a tracking error. In that
case, we would be interested how you did that and how to reproduce
it.
-Arne
>
> # btrfs qgroup show /mnt/lxc2
> 0/260 151490953216 151490953216
> 0/261 180969472 180969472
> 0/262 155557888 983040
> 0/377 180310016 25776128
> 0/378 304088072192 304088072192
> 0/535 571944960 417370112
> 0/536 68550987776 68550987776
> 0/642 247463936 92921856
> 0/1175 617213952 827392
> 0/1181 16112013312 -22184235008
> 0/1268 38296248320 0
> 0/1269 616386560 0
> 0/1270 4096 4096
> 0/1271 4096 4096
>
>
prev parent reply other threads:[~2013-08-02 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 6:21 btrfs quota examples? Tomasz Chmielewski
2013-06-10 7:41 ` Arne Jansen
2013-06-10 7:47 ` Tomasz Chmielewski
2013-06-10 9:24 ` Wang Shilong
2013-07-29 8:05 ` Tomasz Chmielewski
2013-08-02 6:23 ` Arne Jansen [this message]
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=51FB5059.1080406@gmx.net \
--to=sensille@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--cc=tch@virtall.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).