linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Timofey Titovets <nefelim4ag@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: True size of btrfs data chunk
Date: Tue, 29 Nov 2016 09:58:50 -0500	[thread overview]
Message-ID: <44a745cd-ebb0-e62b-371c-8a37edd951fb@gmail.com> (raw)
In-Reply-To: <CAGqmi74qK2v0JCtAjan8aju+sK3LWPWwMgnJOP3i2srrqnLHSA@mail.gmail.com>

On 2016-11-29 09:32, Timofey Titovets wrote:
> Hi, as wiki say https://btrfs.wiki.kernel.org/index.php/Glossary:
> A part of a block group. Chunks are either 1 GiB in size (for data) or
> 256 MiB (for metadata).
This is only about the normal case.  Chunks are variable in size.  In 
most cases, data chunks will be 1GB and metadata 256MB.  They will 
however be smaller if there isn't enough space left for a full chunk, 
and will get larger as well once you get past a certain filesystem size 
(I don't remember the exact size, but I've seen people talking about big 
(double digit TB sized) filesystems with 5GB+ sized data chunks).
>
> Btrfs tools show me that allocated size is not 1GiB aligned, things
> are changes? I miss something?
>
> # btrfs fi df /; btrfs fi usage /;
> Data, single: total=1.41GiB, used=704.47MiB
> System, single: total=32.00MiB, used=16.00KiB
> Metadata, single: total=256.00MiB, used=54.30MiB
> GlobalReserve, single: total=32.00MiB, used=0.00B
> Overall:
>    Device size:                   4.00GiB
>    Device allocated:              1.69GiB
>    Device unallocated:            2.31GiB
>    Device missing:                  0.00B
>    Used:                        758.79MiB
>    Free (estimated):              3.03GiB      (min: 3.03GiB)
>    Data ratio:                       1.00
>    Metadata ratio:                   1.00
>    Global reserve:               32.00MiB      (used: 0.00B)
>
> Data,single: Size:1.41GiB, Used:704.47MiB
>   /dev/sda1       1.41GiB
>
> Metadata,single: Size:256.00MiB, Used:54.30MiB
>   /dev/sda1     256.00MiB
>
> System,single: Size:32.00MiB, Used:16.00KiB
>   /dev/sda1      32.00MiB
>
> Unallocated:
>   /dev/sda1       2.31GiB
>
> Thanks.
>


  reply	other threads:[~2016-11-29 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 14:32 True size of btrfs data chunk Timofey Titovets
2016-11-29 14:58 ` Austin S. Hemmelgarn [this message]
2016-11-30  2:13   ` Duncan

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=44a745cd-ebb0-e62b-371c-8a37edd951fb@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nefelim4ag@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).