From: Tomasz Chmielewski <tch@virtall.com>
To: Arne Jansen <sensille@gmx.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs quota examples?
Date: Mon, 10 Jun 2013 16:47:31 +0900 [thread overview]
Message-ID: <20130610164731.29b2d6c6@virtall.com> (raw)
In-Reply-To: <51B58333.3050901@gmx.net>
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.
Both numbers are bytes, correct?
--
Tomasz Chmielewski
htp://wpkg.org
next prev parent reply other threads:[~2013-06-10 7:47 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 [this message]
2013-06-10 9:24 ` Wang Shilong
2013-07-29 8:05 ` Tomasz Chmielewski
2013-08-02 6:23 ` 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=20130610164731.29b2d6c6@virtall.com \
--to=tch@virtall.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sensille@gmx.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 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).