From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Brad Templeton <4brad@templetons.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-transacti hangs system for several seconds every few minutes
Date: Tue, 31 Mar 2020 00:04:40 -0400 [thread overview]
Message-ID: <20200331040440.GH2693@hungrycats.org> (raw)
In-Reply-To: <CAJCQCtQjjHWunKi7T2GC4MN708sF5RPJmx+w1o8Y_LDzdK3RXQ@mail.gmail.com>
On Mon, Mar 30, 2020 at 04:14:46PM -0600, Chris Murphy wrote:
> On Sun, Mar 29, 2020 at 12:42 AM Zygo Blaxell
> <ce3g8jdj@umail.furryterror.org> wrote:
> >
> > 90 seconds sounds about right for the block group scan when mounting on
> > a 10TB filesystem. There's a feature called block group tree in kernel
> > 5.5 that helps with that: it lays out block group items on disk closer
> > together so they can be read in milliseconds. This is an on-disk format
> > change, so once you enable that feature, you wouldn't be able to mount
> > the filesystem on an older kernel. This can be a problem if your
> > sound drivers have regressions. You might want to wait a few kernel
> > releases to be sure you don't need to downgrade.
>
> I'm not seeing anything about block group tree in btrfs/super.c.
>
> There is block_group_cache_tree but I'm not seeing anything about it
> in 'man 5 btrfs' using btrfs-progs 5.4, or in the devel branch.
>
> So I'm not sure what mount option or btrfstune option this would be,
> seems to be automatic?
> https://github.com/kdave/btrfs-progs/commit/2eaf862f46b3ccb6b7248a0417ebf7096bc93b80
Sorry, my mistake...it was in one of the misc-next branches, but seems to
have been dropped. Maybe not finished yet?
>
> --
> Chris Murphy
>
next prev parent reply other threads:[~2020-03-31 4:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 18:26 btrfs-transacti hangs system for several seconds every few minutes Brad Templeton
2020-03-28 21:20 ` Zygo Blaxell
[not found] ` <7778ece0-67d4-8d1c-b773-35f07d81dcbe@templetons.com>
2020-03-29 6:42 ` Zygo Blaxell
2020-03-30 22:14 ` Chris Murphy
2020-03-31 4:04 ` Zygo Blaxell [this message]
2020-03-29 0:58 ` Qu Wenruo
2020-03-29 4:03 Brad Templeton
2020-03-29 13:14 ` Qu Wenruo
2020-03-29 17:58 ` Brad Templeton
2020-03-29 18:09 ` Zygo Blaxell
2020-03-30 2:29 Tomasz Chmielewski
2020-03-30 5:56 ` Andrei Borzenkov
2020-03-30 8:11 ` Brad Templeton
2020-03-30 8:35 ` Tomasz Chmielewski
2020-03-31 4:20 ` Zygo Blaxell
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=20200331040440.GH2693@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=4brad@templetons.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).