`btrfsck --repair`: check/qgroup-verify.c:546: account_all_refs: BUG_ON `ref->num_bytes != num_bytes` triggered, value 1

[phmarek]

I removed quite a few btrfs snapshots from a filesystem in one go, and got some kernel errors.

Upon trying to check, I get this error:

[1/7] checking root items                      (0:00:06 elapsed, 4264676 items checked)
Fixed 0 roots.
No device size related problem found           (0:05:14 elapsed, 2341723 items checked)
[2/7] checking extents                         (0:05:14 elapsed, 2341723 items checked)
cache and super generation don't match, space cache will be invalidated
[3/7] checking free space cache                (0:00:00 elapsed)
[4/7] checking fs roots                        (0:12:00 elapsed, 2149168 items checked)
[4/7] checking fs roots                        (0:13:05 elapsed, 2281151 items checked)
[5/7] checking csums (without verifying data)  (0:00:05 elapsed, 498064 items checked)
[6/7] checking root refs                       (0:00:00 elapsed, 96 items checked)
[7/7] checking quota groups                    (0:00:58 elapsed, 497482 items checked)
[7/7] checking quota groups                    (0:07:34 elapsed, 12622594 items checked)
[7/7] checking quota groups                    (0:07:35 elapsed, 12649424 items checked)
[7/7] checking quota groups                    (0:08:50 elapsed, 14609793 items checked)
check/qgroup-verify.c:546: account_all_refs: BUG_ON `ref->num_bytes != num_bytes` triggered, value 1
btrfs check(+0x18fcc)[0x5591be569fcc]
btrfs check(+0x18ffd)[0x5591be569ffd]
btrfs check(+0x191c8)[0x5591be56a1c8]
btrfs check(qgroup_verify_all+0x4a6)[0x5591be56b32f]
btrfs check(+0x3d6dc)[0x5591be58e6dc]
btrfs check(main+0x30b)[0x5591be566f8b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7f9845c0ccca]
btrfs check(_start+0x2a)[0x5591be566fca]
Abgebrochen

btrfs-progs=5.9-1+b1, using quotas.

[julian-klode]

Had the same issue today, lost my entire lxd storage pool to it. Was sad, but can't contribute much useful given that I deleted the broken volume - sorry :(

[ShrirajHegde]

Any progress on this? I have the same problem.. Is it possible to repair this error?