linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: True size of btrfs data chunk
Date: Wed, 30 Nov 2016 02:13:38 +0000 (UTC)	[thread overview]
Message-ID: <pan$b11a5$ec6d0e80$982b9cb0$a4cf188b@cox.net> (raw)
In-Reply-To: 44a745cd-ebb0-e62b-371c-8a37edd951fb@gmail.com

Austin S. Hemmelgarn posted on Tue, 29 Nov 2016 09:58:50 -0500 as
excerpted:

> On 2016-11-29 09:32, Timofey Titovets wrote:
>> Hi, as wiki say https://btrfs.wiki.kernel.org/index.php/Glossary:

Bad link.  Without the terminating colon it works, however.

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).

Yes.  The wiki is correct about the _nominal_ size, but it doesn't say 
"nominal", making the overall claim invalid.

If I had a wiki account I'd probably change it right now, but for 
personal reasons I don't fully understand myself, I seem to treat web 
pages, including wikis I could in theory edit, as read-only, even if the 
alternative is replying repeatedly to list threads such as this, vs. a 
single wiki edit.  [shrug]

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


      reply	other threads:[~2016-11-30  2:13 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
2016-11-30  2:13   ` Duncan [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='pan$b11a5$ec6d0e80$982b9cb0$a4cf188b@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.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).