From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Wei Tang <wei@that.world>, linux-btrfs@vger.kernel.org
Subject: Re: Balance loop converting from single to raid-1 (kernel 5.13.3)
Date: Sat, 24 Jul 2021 14:47:36 +0800 [thread overview]
Message-ID: <f7c02e15-f76e-2f34-dacb-b72976b30750@gmx.com> (raw)
In-Reply-To: <f85b8b32-0fec-056c-63ba-1ebb64f2bc09@that.world>
On 2021/7/23 下午2:39, Wei Tang wrote:
> Today I was trying to convert a btrfs disk from single to raid-1. It
> gets stuck in this seemingly infinite loop:
>
> Jul 23 08:30:48 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:48 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:48 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:48 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:48 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:49 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
> Jul 23 08:30:50 loopforward kernel: BTRFS info (device dm-5): found 1
> extents, stage: update data pointers
This looks like a runaway balance, but that should be fixed in v5.8.
Thus it's pretty weird.
>
> Canceling the conversion then restarting it, or rebooting, does not seem
> to do anything -- the same "1 extents" loop always reappears.
You can unmount, then mount with "-o skip_balance" mount option to
workaround it.
BTW, when you unmount the fs, could you also catch the kernel messages?
As since v5.8 we added an extra warning to catch such problem.
Thanks,
Qu
>
> # uname -a
> Linux loopforward 5.13.3 #1-NixOS SMP Mon Jul 19 08:04:55 UTC 2021
> x86_64 GNU/Linux
prev parent reply other threads:[~2021-07-24 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 6:39 Balance loop converting from single to raid-1 (kernel 5.13.3) Wei Tang
2021-07-24 6:47 ` Qu Wenruo [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=f7c02e15-f76e-2f34-dacb-b72976b30750@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wei@that.world \
/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).