From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs might be gradually slowing the boot process
Date: Sun, 10 Nov 2013 11:14:08 +0000 (UTC) [thread overview]
Message-ID: <pan$4dd5e$f5631722$5803e40a$fdc51295@cox.net> (raw)
In-Reply-To: 04B39B7F-24A2-42E0-8C4A-31D710A844E6@colorremedies.com
Chris Murphy posted on Sat, 09 Nov 2013 21:53:10 -0700 as excerpted:
> What's leafsize was used when making the file system? The default is now
> (as of yesterday) 16KB to avoid metadata fragmentation.
I saw the discussion of that, but two questions it didn't answer -- (1)
what was the default size before, and (2) how do I check what I actually
have?
The wiki mkfs.btrfs page answers the first question: 4KiB, standard page-
size. (Of course that needs updated now.)
The same page says nodesize defaults to the same as leafsize. Is that
still true, or does it remain 4KiB? Also, sectorsize defaults to 4KiB,
but the wiki doesn't note whether it always defaults to that, or whether
it too defaults to the same as leafsize.
And nowhere on the wiki do I see a sysadmin's level guide to how
leafsize, nodesize and sectorsize relate to each other, nor how they
relate to chunks or how btrfs manages chunksize.
Josef Bacik's article, "Btrfs - The Swiss Army Knife of Storage"[1],
linked below and in the wiki articles section, does mention that nodes
and leaves are b-tree terms, where nodes contain keys and links to the
next level nodes or leaves, and leaves contain actual data, which helps
somewhat. But where do sectors fit in to this?
The same article says data chunk sizes are 1GiB by default, metadata
256MiB, but when space starts getting tight (and how tight is tight, with
the last full gig be allocated to a full gig data chunk or will it go
smaller before it reserves the last fill gig? how much before, 10 gig, 2
gig?), does it shrink by orders of two or does it jump down from a gig to
say 128 meg in one jump, and do data and metadata follow the same jump
rules or not?
And hardly any of this is actually on the wiki, at least the sysadmin's
docs (the dev docs might cover it, I'm not a dev and haven't looked that
closely at them, but that still leaves sysadmins).
[1] http://static.usenix.org/publications/login/2012-02/openpdfs/Bacik.pdf
--
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
next prev parent reply other threads:[~2013-11-10 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 18:35 Btrfs might be gradually slowing the boot process yzb3
2013-11-08 19:38 ` Shridhar Daithankar
2013-11-09 10:57 ` Kai Krakow
2013-11-10 4:53 ` Chris Murphy
2013-11-10 11:14 ` Duncan [this message]
2013-11-10 12:54 ` Russell Coker
2013-11-10 16:07 ` Kai Krakow
2013-11-10 16:09 ` Hugo Mills
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$4dd5e$f5631722$5803e40a$fdc51295@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).