btrfs: Mark pinned log extents as excluded
In preparation to making pinned extents per-transaction ensure that log such extents are always excluded from caching. To achieve this in addition to marking them via btrfs_pin_extent_for_log_replay they also need to be marked with btrfs_add_excluded_extent to prevent log tree extent buffer being loaded by the free space caching thread. That's required since log tree blocks are not recorded in the extent tree, hence they always look free. Reviewed-by: Josef Bacik <josef@toxicpanda.com> Signed-off-by: Nikolay Borisov <nborisov@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
parent
6b45f64172
commit
f2fb72983b
|
@ -2633,6 +2633,8 @@ int btrfs_pin_extent_for_log_replay(struct btrfs_trans_handle *trans,
|
|||
struct btrfs_block_group *cache;
|
||||
int ret;
|
||||
|
||||
btrfs_add_excluded_extent(trans->fs_info, bytenr, num_bytes);
|
||||
|
||||
cache = btrfs_lookup_block_group(trans->fs_info, bytenr);
|
||||
if (!cache)
|
||||
return -EINVAL;
|
||||
|
@ -2919,6 +2921,12 @@ int btrfs_finish_extent_commit(struct btrfs_trans_handle *trans)
|
|||
mutex_unlock(&fs_info->unused_bg_unpin_mutex);
|
||||
break;
|
||||
}
|
||||
if (test_bit(BTRFS_FS_LOG_RECOVERING, &fs_info->flags)) {
|
||||
clear_extent_bits(&fs_info->freed_extents[0], start,
|
||||
end, EXTENT_UPTODATE);
|
||||
clear_extent_bits(&fs_info->freed_extents[1], start,
|
||||
end, EXTENT_UPTODATE);
|
||||
}
|
||||
|
||||
if (btrfs_test_opt(fs_info, DISCARD_SYNC))
|
||||
ret = btrfs_discard_extent(fs_info, start,
|
||||
|
|
Loading…
Reference in New Issue