From: Ian Kelling <iank@fsf.org>
To: linux-btrfs@vger.kernel.org
Subject: balance stuck in loop on linux 6.1.7
Date: Tue, 24 Jan 2023 19:43:24 -0500 [thread overview]
Message-ID: <87a6271kbg.fsf@fsf.org> (raw)
Jan 19 11:48:50 frodo kernel: BTRFS info (device dm-13): balance: start -dconvert=raid1c3 -mconvert=raid1c3 -sconvert=raid1c3
...
Jan 22 05:03:23 frodo kernel: BTRFS info (device dm-13): relocating block group 80026774405120 flags data|raid1c3
Jan 22 05:03:48 frodo kernel: BTRFS info (device dm-13): found 41 extents, stage: move data extents
Jan 22 05:03:57 frodo kernel: BTRFS info (device dm-13): found 41 extents, stage: update data pointers
Jan 22 05:04:06 frodo kernel: BTRFS info (device dm-13): relocating block group 80025700663296 flags data|raid1c3
Jan 22 05:04:29 frodo kernel: BTRFS info (device dm-13): found 71 extents, stage: move data extents
Jan 22 05:04:48 frodo kernel: BTRFS info (device dm-13): found 71 extents, stage: update data pointers
Jan 22 05:05:10 frodo kernel: BTRFS info (device dm-13): relocating block group 42827839111168 flags data|raid10
Jan 22 05:05:24 frodo kernel: BTRFS info (device dm-13): found 1 extents, stage: move data extents
Jan 22 05:05:42 frodo kernel: BTRFS info (device dm-13): found 1 extents, stage: update data pointers
Jan 22 05:05:55 frodo kernel: BTRFS info (device dm-13): found 1 extents, stage: update data pointers
Jan 22 05:06:08 frodo kernel: BTRFS info (device dm-13): found 1 extents, stage: update data pointers
Jan 22 05:06:21 frodo kernel: BTRFS info (device dm-13): found 1 extents, stage: update data pointers
Jan 22 05:06:29 frodo kernel: BTRFS info (device dm-13): found 1 extents, stage: update data pointers
...
Jan 24 19:48:19 frodo kernel: BTRFS info (device dm-13): found 1 extents, stage: update data pointers
Jan 24 19:48:35 frodo kernel: BTRFS info (device dm-13): found 1 extents, stage: update data pointers
Since the ..., all the lines have been repeats.
# btrfs balance status /mnt/i
Balance on '/mnt/i' is running
6650 out of about 7480 chunks balanced (6651 considered), 11% left
It has been stuck at 11% for the last 2 days and I assume since the loop
started.
I first experienced this on an earlier kernel so I canceled it and
upgraded to the latest but it is still getting stuck.
# cat /proc/version
Linux version 6.1.7-gnu (rms@mit-oz) (x86_64-linux-gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.40) #1.0 SMP PREEMPT_DYNAMIC Tue Sep 27 12:35:59 EST 1983
# btrfs --version
btrfs-progs v6.1.2
If this is a bug, I would like to help the btrfs developers solve it. I
can run whatever commands needed to get more information and try out
patches. But I cannot provide a copy of the filesystem because it has
personal data.
If I restart the balance, it will take about 2.8 days to get back to the
stuck 11% point. The balance is still running, but I'm going to cancel
it morning unless I hear from the list that there is some use to letting
it run since it is wearing out the mechanical drives.
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
next reply other threads:[~2023-01-25 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 0:43 Ian Kelling [this message]
2023-01-25 10:44 ` balance stuck in loop on linux 6.1.7 Patrik Lundquist
2023-01-25 19:48 ` Ian Kelling
2023-01-25 20:25 ` Patrik Lundquist
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=87a6271kbg.fsf@fsf.org \
--to=iank@fsf.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.