From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Russell Coker <russell@coker.com.au>, linux-btrfs@vger.kernel.org
Subject: Re: balance loop with raid-1 on 5.7.6-1
Date: Sun, 2 Aug 2020 09:19:21 +0800 [thread overview]
Message-ID: <927d2761-dfa8-ca50-a1b0-155d70828bdf@gmx.com> (raw)
In-Reply-To: <13086015.6n0rELWJ5N@liv>
[-- Attachment #1.1: Type: text/plain, Size: 2036 bytes --]
On 2020/8/2 上午9:07, Russell Coker wrote:
> My monthly cron job which runs a btrfs scrub followed by a btrfs balance has
> just gone into an infinite loop.
>
> root@xev:~# grep -c "found 69 extents" /var/log/kern.log
> 322889
> root@xev:~# uname -a
> Linux xev 5.7.0-1-amd64 #1 SMP Debian 5.7.6-1 (2020-06-24) x86_64 GNU/Linux
This is a known bug, and backport for 5.7.x only arrives at 5.7.11.
So please update your kernel to latest 5.7.x stable kernel, or try
v5.8-rc kernels.
Thanks,
Qu
>
> Aug 2 02:57:09 xev kernel: [894810.916299] BTRFS info (device dm-1): scrub:
> finished on devid 3 with status: 0
> Aug 2 02:57:09 xev kernel: [894810.947243] BTRFS info (device dm-1): balance:
> start -dusage=60 -musage=10 -susage=10
> Aug 2 02:57:09 xev kernel: [894810.948707] BTRFS info (device dm-1):
> relocating block group 2734629453824 flags system|raid1
> Aug 2 02:57:09 xev kernel: [894811.034399] BTRFS info (device dm-1):
> relocating block group 2659366862848 flags data|raid1
> Aug 2 02:57:15 xev kernel: [894816.467989] BTRFS info (device dm-1): found
> 12902 extents, stage: move data extents
> Aug 2 02:57:40 xev kernel: [894841.585184] BTRFS info (device dm-1): found
> 12902 extents, stage: update data pointers
> Aug 2 02:57:41 xev kernel: [894842.878672] BTRFS info (device dm-1): found 69
> extents, stage: update data pointers
> Aug 2 02:57:41 xev kernel: [894842.915311] BTRFS info (device dm-1): found 69
> extents, stage: update data pointers
> [...]
> Aug 2 11:04:01 xev kernel: [924022.697116] BTRFS info (device dm-1): found 69
> extents, stage: update data pointers
> Aug 2 11:04:01 xev kernel: [924022.754418] BTRFS info (device dm-1): found 69
> extents, stage: update data pointers
> Aug 2 11:04:01 xev kernel: [924022.805762] BTRFS info (device dm-1): found 69
> extents, stage: update data pointers
> Aug 2 11:04:01 xev kernel: [924022.870560] BTRFS info (device dm-1): found 69
> extents, stage: update data pointers
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-02 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 1:07 balance loop with raid-1 on 5.7.6-1 Russell Coker
2020-08-02 1:19 ` Qu Wenruo [this message]
2020-08-02 1:55 ` Russell Coker
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=927d2761-dfa8-ca50-a1b0-155d70828bdf@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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