linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: devel@roosoft.ltd.uk
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Problems balancing BTRFS
Date: Sat, 23 Nov 2019 09:20:04 -0700	[thread overview]
Message-ID: <CAJCQCtTJ5PozQ=NbP4dbWuN_OPq1t1TWvfHouf6GA5h1m7_4+g@mail.gmail.com> (raw)
In-Reply-To: <e382e662-b09f-c9f3-e589-44560a7b9b97@casa-di-locascio.net>

On Fri, Nov 22, 2019 at 6:41 AM <devel@roosoft.ltd.uk> wrote:
>
> So really I am not sure what to do. It only seems to appear during a
> balance, which as far as I know is a much needed regular maintenance
> tool to keep a fs healthy, which is why it is part of the
> btrfsmaintenance tools

I wouldn't say balance is a needed regular maintenance item, let alone
much needed. The issue in your case is that the allocation is
inefficient. If I'm parsing the output correctly, it looks as if the
block groups could be, in effect, two sets of two device raid5. But
that's the worst case scenario, we'd need to see the chunk tree to
know how inefficient it is, but it's no worse than if the data were
raid1. And yes it increases the time for scrubbing as well.

-- 
Chris Murphy

      parent reply	other threads:[~2019-11-23 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22 12:37 Problems balancing BTRFS devel
2019-11-22 13:10 ` Qu Wenruo
2019-11-22 13:20   ` devel
2019-11-22 13:56     ` Qu Wenruo
2019-11-22 14:07       ` devel
2019-11-22 15:32         ` devel
2019-11-23  0:09           ` Qu Wenruo
2019-11-23 12:53             ` devel
2019-11-23 16:20     ` Chris Murphy [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='CAJCQCtTJ5PozQ=NbP4dbWuN_OPq1t1TWvfHouf6GA5h1m7_4+g@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=devel@roosoft.ltd.uk \
    --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).