From: Chris Murphy <lists@colorremedies.com>
To: Zirconium Hacker <jared.e.vb@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: btrfs balance hangs
Date: Thu, 4 Apr 2019 21:04:21 -0600 [thread overview]
Message-ID: <CAJCQCtSA=f+XWy8KzpzGdpjyaBsDOT5G+aC5FU9G2Fyi-sMvrQ@mail.gmail.com> (raw)
In-Reply-To: <CALsQ4_x-VViOA5Cu4vJTqmx3xSospmiEdsEcDDBcj=uvZUmrVQ@mail.gmail.com>
On Thu, Apr 4, 2019 at 12:18 PM Zirconium Hacker <jared.e.vb@gmail.com> wrote:
>
> Yes, I have qgroups enabled on that filesystem. I'll disable qgroups
> the next chance I get, they aren't worth the trouble.
>
> After rebooting, BTRFS finished the balance. I then foolishly started
> a selective metadata balance, which never got past the first block
> group; it just thrashed the disk for several hours.
> It could not be canceled, so I rebooted.
>
> Then I mounted the filesystem with skip_balance and clear_cache.
> The mount failed. The relevant part of dmesg is attached.
I can't parse that, maybe Qu has an idea. In the meantime I suggest
btrfs-progs 4.20.2 and running:
# btrfs check --readonly /dev/
Attach that output.
Balance is supposed to be COW. And skip_balance and clear_cache are
supposed to be safe. So I'd say you've found a bug but I don't know
what it is or how to work around it.
--
Chris Murphy
next prev parent reply other threads:[~2019-04-05 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 16:11 btrfs balance hangs Zirconium Hacker
2019-04-01 16:43 ` Chris Murphy
2019-04-04 18:17 ` Zirconium Hacker
2019-04-05 3:04 ` Chris Murphy [this message]
2019-04-05 5:24 ` Zirconium Hacker
2019-04-05 6:39 ` Chris Murphy
2019-04-05 7:15 ` Qu Wenruo
2019-04-09 0:12 ` Zirconium Hacker
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='CAJCQCtSA=f+XWy8KzpzGdpjyaBsDOT5G+aC5FU9G2Fyi-sMvrQ@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=jared.e.vb@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).