btrfs: move existing remaps before relocating block group

Browse source

If when relocating a block group we find that `remap_bytes` > 0 in its
block group item, that means that it has been the destination block
group for another that has been remapped.

We need to search the remap tree for any remap backrefs within this
range, and move the data to a third block group. This is because
otherwise btrfs_translate_remap() could end up following an unbounded
chain of remaps, which would only get worse over time.

We only relocate one block group at a time, so `remap_bytes` will only
ever go down while we are doing this. Once we're finished we set the
REMAPPED flag on the block group, which will permanently prevent any
other data from being moved to within it.

Reviewed-by: Boris Burkov <boris@bur.io>
Signed-off-by: Mark Harmstone <mark@harmstone.com>
Signed-off-by: David Sterba <dsterba@suse.com>

...

This commit is contained in:

Mark Harmstone 2026-01-07 14:09:12 +00:00 • committed by David Sterba

parent b56f35560b

commit bbea42dfb9

4 changed files with 467 additions and 5 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

fs/btrfs/bio.c

View file

3

fs/btrfs/bio.h

View file

6

fs/btrfs/extent-tree.c

View file

461

fs/btrfs/relocation.c

View file