Btrfs: improve the logic in btrfs_can_relocate() (4a5e98f5) · Commits · 戴 / test

fs/btrfs/extent-tree.c

+18 −6

Original line number	Diff line number	Diff line
		@@ -7136,6 +7136,7 @@ int btrfs_can_relocate(struct btrfs_root *root, u64 bytenr)
		u64 min_free;
		u64 dev_min = 1;
		u64 dev_nr = 0;
		u64 target;
		int index;
		int full = 0;
		int ret = 0;
		@@ -7176,13 +7177,11 @@ int btrfs_can_relocate(struct btrfs_root *root, u64 bytenr)
		/*
		* ok we don't have enough space, but maybe we have free space on our
		* devices to allocate new chunks for relocation, so loop through our
		* alloc devices and guess if we have enough space. However, if we
		* were marked as full, then we know there aren't enough chunks, and we
		* can just return.
		* alloc devices and guess if we have enough space. if this block
		* group is going to be restriped, run checks against the target
		* profile instead of the current one.
		*/
		ret = -1;
		if (full)
		goto out;

		/*
		* index:
		@@ -7192,7 +7191,20 @@ int btrfs_can_relocate(struct btrfs_root *root, u64 bytenr)
		* 3: raid0
		* 4: single
		*/
		target = get_restripe_target(root->fs_info, block_group->flags);
		if (target) {
		index = __get_block_group_index(extended_to_chunk(target));
		} else {
		/*
		* this is just a balance, so if we were marked as full
		* we know there is no space for a new chunk
		*/
		if (full)
		goto out;

		index = get_block_group_index(block_group);
		}

		if (index == 0) {
		dev_min = 4;
		/* Divide by 2 */