From: Nikolay Borisov <nborisov@suse.com>
To: mailing@dmilz.net, Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Filesystem Read Only due to errno=-28 during metadata allocation
Date: Mon, 25 Oct 2021 13:32:27 +0300 [thread overview]
Message-ID: <a875f5f2-5d58-39bd-87be-74f5322ce035@suse.com> (raw)
In-Reply-To: <537ba7e11aae3e2c2cf28f546268c356@dmilz.net>
On 25.10.21 г. 12:53, mailing@dmilz.net wrote:
<snip>
> Thanks for all information!
>
> If the chunk size (128MB, 256MB... 1GB) is in relation to the FS size,
> is there a command to determine the chunk size for data and metadata?
You can determine it by dumping the on-disk data structure via btrfs
inspect-internal dump-tree -t2 /dev/foo this will contain the currently
allocated blockgroups and their respective size.
> Should I expect BTRFS to start allocating bigger chunk at some point
> after filesystem extension?
Yes, this is mandated by the code in init_alloc_chunk_ctl_policy_regular
function.
Basically data chunks are at most 1G in size, metadat chunks are either
1G or 256m depending on whether the fs is larger than 50gb. But a chunk
can never be more than 10% of the writable space on disk.
>
prev parent reply other threads:[~2021-10-25 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 12:35 Filesystem Read Only due to errno=-28 during metadata allocation mailing
2021-10-18 11:13 ` mailing
2021-10-18 14:09 ` Zygo Blaxell
2021-10-19 10:57 ` mailing
2021-10-19 13:26 ` Zygo Blaxell
2021-10-25 9:53 ` mailing
2021-10-25 10:32 ` Nikolay Borisov [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=a875f5f2-5d58-39bd-87be-74f5322ce035@suse.com \
--to=nborisov@suse.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=mailing@dmilz.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).