btrfs: free space tree mounting fixes
v4 cover btrfs: free space tree mounting fixes
This patch set cleans up issues surrounding enabling and disabling various free space cache features and their reporting in /proc/mounts. Because the improvements became somewhat complex, the series starts by lifting rw mount logic into a single place.
The first patch is a setup patch that unifies very similar logic between a normal rw mount and a ro->rw remount. This is a useful setup step for adding more functionality to ro->rw remounts.
The second patch fixes the omission of orphan inode cleanup on a few trees during ro->rw remount.
The third patch adds enabling the free space tree to ro->rw remount.
The fourth patch sets up for more accurate /proc/mounts by ensuring that cache_generation > 0 iff space_cache is enabled.
The fifth patch is the more accurate /proc/mounts logic.
The sixth patch is a convenience kernel message that complains when we skip enabling the free space tree on remount.
The seventh patch removes the space cache v1 free space item and free space inodes when space cache v1 is disabled (nospace_cache or space_cache=v2).
The eighth patch stops re-creating the free space objects when we are not using space_cache=v1
changes for v4:
Patch 1/8: New
Patch 2/8: New
Patch 3/8: (was Patch 1) Made much simpler by lifting of Patch 1. Simply add
free space tree creation to lifted rw mount logic.
Patch 4/8: Split out from old Patch 2. Add an fs_info flag to avoid surprises
when a different transaction updates the cache_generation.
Patch 5/8: Split out from old Patch 2, but no change logically. Patch 6/8: Split out from old Patch 1. Formatting fixes.
Patch 7/8: (was Patch 3) Rely on delayed_iput running after orphan cleanup
(setup in patch 2) to pull iputs out of mount path, per review.
Patch 8/8: No change.
changes for v3:
Patch 1/4: Change failure to warning logging.
Patch 2/4: New; fixes mount option printing.
Patch 3/4: Fix orphan inode vs. delayed iput bug, change remove function
to take inode as a sink.
Patch 4/4: No changes.
changes for v2:
Patch 1/3: made remount _only_ work in ro->rw case, added comment. Patch 2/3: added btrfs_ prefix to non-static function, removed bad
whitespace.
Boris Burkov (8):
btrfs: lift rw mount setup from mount and remount
btrfs: cleanup all orphan inodes on ro->rw remount
btrfs: create free space tree on ro->rw remount
btrfs: keep sb cache_generation consistent with space_cache
btrfs: use sb state to print space_cache mount option
btrfs: warn when remount will not create the free space tree
btrfs: remove free space items when disabling space cache v1
btrfs: skip space_cache v1 setup when not using it
fs/btrfs/block-group.c | 42 ++--------- fs/btrfs/ctree.h | 3 + fs/btrfs/disk-io.c | 141 ++++++++++++++++++++---------------- fs/btrfs/disk-io.h | 1 + fs/btrfs/free-space-cache.c | 121 +++++++++++++++++++++++++++++++ fs/btrfs/free-space-cache.h | 6 ++ fs/btrfs/super.c | 59 ++++++--------- fs/btrfs/transaction.c | 2 + 8 files changed, 241 insertions(+), 134 deletions(-)
Signature · 1 line
2.24.1
PATCH v4 1/8 btrfs: lift rw mount setup from mount and remount
Mounting rw and remounting from ro to rw naturally share invariants and functionality which result in a correctly setup rw filesystem. Luckily, there is even a strong unity in the code which implements them. In mount's open_ctree, these operations mostly happen after an early return for ro file systems, and in remount, they happen in a section devoted to remounting ro->rw, after some remount specific validation passes.
However, there are unfortunately a few differences. There are small deviations in the order of some of the operations, remount does not cleanup orphan inodes in root_tree or fs_tree, remount does not create the free space tree, and remount does not handle "one-shot" mount options like clear_cache and uuid tree rescan.
Since we want to add building the free space tree to remount, and since it is possible to leak orphans on a filesystem mounted as ro then remounted rw (common for the root filesystem when booting), we would benefit from unifying the logic between the two codepaths.
This patch only lifts the existing common functionality, and leaves a natural path for fixing the discrepancies.
--- fs/btrfs/disk-io.c | 93 ++++++++++++++++++++++++++-------------------- fs/btrfs/disk-io.h | 1 + fs/btrfs/super.c | 37 +++--------------- 3 files changed, 60 insertions(+), 71 deletions(-)
fs/btrfs/disk-io.c +53 -40
@@ -2814,6 +2814,53 @@ static int btrfs_check_uuid_tree(struct btrfs_fs_info *fs_info)return 0 ; } +/* +* Mounting logic specific to read-write file systems. Shared by open_ctree +* and btrfs_remount when remounting from read-only to read-write. +*/ +int btrfs_mount_rw (struct btrfs_fs_info *fs_info) +{ +int ret; + + ret =btrfs_cleanup_fs_roots (fs_info); +if (ret) + goto out; + +mutex_lock (&fs_info->cleaner_mutex); + ret =btrfs_recover_relocation (fs_info->tree_root); +mutex_unlock (&fs_info->cleaner_mutex); +if (ret <0 ) { +btrfs_warn (fs_info,"failed to recover relocation: %d" , ret); + goto out; + } + + ret =btrfs_resume_balance_async (fs_info); +if (ret) + goto out; + + ret =btrfs_resume_dev_replace_async (fs_info); +if (ret) { +btrfs_warn (fs_info,"failed to resume dev_replace" ); + goto out; + } + +btrfs_qgroup_rescan_resume (fs_info); + +if (!fs_info->uuid_root) { +btrfs_info (fs_info,"creating UUID tree" ); + ret =btrfs_create_uuid_tree (fs_info); +if (ret) { +btrfs_warn (fs_info, +"failed to create the UUID tree %d" , + ret); + goto out; + } + } + +out: +return ret; +} +int __cold open_ctree (struct super_block *sb,struct btrfs_fs_devices *fs_devices,char *options) {
@@ -3218,22 +3265,6 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_deviceif (ret) goto fail_qgroup; -if (!sb_rdonly (sb)) { - ret =btrfs_cleanup_fs_roots (fs_info); -if (ret) - goto fail_qgroup; - -mutex_lock (&fs_info->cleaner_mutex); - ret =btrfs_recover_relocation (tree_root); -mutex_unlock (&fs_info->cleaner_mutex); -if (ret <0 ) { -btrfs_warn (fs_info,"failed to recover relocation: %d" , - ret); - err = -EINVAL ; - goto fail_qgroup; - } - } - fs_info->fs_root =btrfs_get_fs_root (fs_info,BTRFS_FS_TREE_OBJECTID , true);if (IS_ERR (fs_info->fs_root)) { err =PTR_ERR (fs_info->fs_root);
@@ -3286,35 +3317,17 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device }up_read (&fs_info->cleanup_work_sem); - ret =btrfs_resume_balance_async (fs_info); -if (ret) { -btrfs_warn (fs_info,"failed to resume balance: %d" , ret); -close_ctree (fs_info); -return ret; - } - - ret =btrfs_resume_dev_replace_async (fs_info); +btrfs_discard_resume (fs_info); + ret =btrfs_mount_rw (fs_info);if (ret) { -btrfs_warn (fs_info,"failed to resume device replace: %d" , ret);close_ctree (fs_info);return ret; } -btrfs_qgroup_rescan_resume (fs_info); -btrfs_discard_resume (fs_info); - -if (!fs_info->uuid_root) { -btrfs_info (fs_info,"creating UUID tree" ); - ret =btrfs_create_uuid_tree (fs_info); -if (ret) { -btrfs_warn (fs_info, -"failed to create the UUID tree: %d" , ret); -close_ctree (fs_info); -return ret; - } - }else if (btrfs_test_opt (fs_info,RESCAN_UUID_TREE ) || - fs_info->generation != -btrfs_super_uuid_tree_generation (disk_super)) { +if (fs_info->uuid_root && + (btrfs_test_opt (fs_info,RESCAN_UUID_TREE ) || + fs_info->generation != +btrfs_super_uuid_tree_generation (disk_super))) {btrfs_info (fs_info,"checking UUID tree" ); ret =btrfs_check_uuid_tree (fs_info);if (ret) {
fs/btrfs/disk-io.h +1 -0
@@ -50,6 +50,7 @@ struct extent_buffer *btrfs_find_create_tree_block(struct btrfs_fs_info *fs_info, u64 bytenr);void btrfs_clean_tree_block (struct extent_buffer *buf); +int btrfs_mount_rw (struct btrfs_fs_info *fs_info);int __cold open_ctree (struct super_block *sb,struct btrfs_fs_devices *fs_devices,char *options);
fs/btrfs/super.c +6 -31
@@ -1831,7 +1831,6 @@ static inline void btrfs_remount_cleanup(struct btrfs_fs_info *fs_info,static int btrfs_remount (struct super_block *sb,int *flags,char *data) {struct btrfs_fs_info *fs_info =btrfs_sb (sb); -struct btrfs_root *root = fs_info->tree_root;unsigned old_flags = sb->s_flags;unsigned long old_opts = fs_info->mount_opt;unsigned long old_compress_type = fs_info->compress_type;
@@ -1924,39 +1923,15 @@ static int btrfs_remount(struct super_block *sb, int *flags, char *data) goto restore; } - ret =btrfs_cleanup_fs_roots (fs_info); -if (ret) - goto restore; - -/* recover relocation */ -mutex_lock (&fs_info->cleaner_mutex); - ret =btrfs_recover_relocation (root); -mutex_unlock (&fs_info->cleaner_mutex); -if (ret) - goto restore; - - ret =btrfs_resume_balance_async (fs_info); +/* +* NOTE: when remounting with a change that does writes, don't +* put it anywhere above this point, as we are not sure to be +* safe to write until we pass the above checks. +*/ + ret =btrfs_mount_rw (fs_info);if (ret) goto restore; - ret =btrfs_resume_dev_replace_async (fs_info); -if (ret) { -btrfs_warn (fs_info,"failed to resume dev_replace" ); - goto restore; - } - -btrfs_qgroup_rescan_resume (fs_info); - -if (!fs_info->uuid_root) { -btrfs_info (fs_info,"creating UUID tree" ); - ret =btrfs_create_uuid_tree (fs_info); -if (ret) { -btrfs_warn (fs_info, -"failed to create the UUID tree %d" , - ret); - goto restore; - } - } sb->s_flags &= ~SB_RDONLY ;set_bit (BTRFS_FS_OPEN , &fs_info->flags);
Signature · 1 line
2.24.1
PATCH v4 2/8 btrfs: cleanup all orphan inodes on ro->rw remount
In reply to Boris BurkovWhen we mount a rw file system, we clean the orphan inodes in the filesystem trees, and also on the tree_root and fs_root. However, when we remount a ro file system rw, we only clean the former. Move the calls to btrfs_orphan_cleanup() on tree_root and fs_root to the shared rw mount routine to effectively add them on ro->rw remount.
--- fs/btrfs/disk-io.c | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-)
fs/btrfs/disk-io.c +8 -9
@@ -2826,6 +2826,14 @@ int btrfs_mount_rw(struct btrfs_fs_info *fs_info)if (ret) goto out; +down_read (&fs_info->cleanup_work_sem); +if ((ret =btrfs_orphan_cleanup (fs_info->fs_root)) || + (ret =btrfs_orphan_cleanup (fs_info->tree_root))) { +up_read (&fs_info->cleanup_work_sem); + goto out; + } +up_read (&fs_info->cleanup_work_sem); +mutex_lock (&fs_info->cleaner_mutex); ret =btrfs_recover_relocation (fs_info->tree_root);mutex_unlock (&fs_info->cleaner_mutex);
@@ -3308,15 +3316,6 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device } } -down_read (&fs_info->cleanup_work_sem); -if ((ret =btrfs_orphan_cleanup (fs_info->fs_root)) || - (ret =btrfs_orphan_cleanup (fs_info->tree_root))) { -up_read (&fs_info->cleanup_work_sem); -close_ctree (fs_info); -return ret; - } -up_read (&fs_info->cleanup_work_sem); -btrfs_discard_resume (fs_info); ret =btrfs_mount_rw (fs_info);if (ret) {
Signature · 1 line
2.24.1
PATCH v4 3/8 btrfs: create free space tree on ro->rw remount
In reply to Boris BurkovWhen a user attempts to remount a btrfs filesystem with 'mount -o remount,space_cache=v2', that operation silently succeeds. Unfortunately, this is misleading, because the remount does not create the free space tree. /proc/mounts will incorrectly show space_cache=v2, but on the next mount, the file system will revert to the old space_cache.
For now, we handle only the easier case, where the existing mount is read-only and the new mount is read-write. In that case, we can create the free space tree without contending with the block groups changing as we go.
--- fs/btrfs/disk-io.c | 23 +++++++++++------------ 1 file changed, 11 insertions(+), 12 deletions(-)
fs/btrfs/disk-io.c +11 -12
@@ -2842,6 +2842,17 @@ int btrfs_mount_rw(struct btrfs_fs_info *fs_info) goto out; } +if (btrfs_test_opt (fs_info,FREE_SPACE_TREE ) && + !btrfs_fs_compat_ro (fs_info,FREE_SPACE_TREE )) { +btrfs_info (fs_info,"creating free space tree" ); + ret =btrfs_create_free_space_tree (fs_info); +if (ret) { +btrfs_warn (fs_info, +"failed to create free space tree: %d" , ret); + goto out; + } + } + ret =btrfs_resume_balance_async (fs_info);if (ret) goto out;
@@ -3304,18 +3315,6 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device } } -if (btrfs_test_opt (fs_info,FREE_SPACE_TREE ) && - !btrfs_fs_compat_ro (fs_info,FREE_SPACE_TREE )) { -btrfs_info (fs_info,"creating free space tree" ); - ret =btrfs_create_free_space_tree (fs_info); -if (ret) { -btrfs_warn (fs_info, -"failed to create free space tree: %d" , ret); -close_ctree (fs_info); -return ret; - } - } -btrfs_discard_resume (fs_info); ret =btrfs_mount_rw (fs_info);if (ret) {
Signature · 1 line
2.24.1
PATCH v4 4/8 btrfs: keep sb cache_generation consistent with space_cache
In reply to Boris BurkovWhen mounting, btrfs uses the cache_generation in the super block to determine if space cache v1 is in use. However, by mounting with nospace_cache or space_cache=v2, it is possible to disable space cache v1, which does not result in un-setting cache_generation back to 0.
In order to base some logic, like mount option printing in /proc/mounts, on the current state of the space cache rather than just the values of the mount option, keep the value of cache_generation consistent with the status of space cache v1.
We ensure that cache_generation > 0 iff the file system is using space_cache v1. This requires committing a transaction on any mount which changes whether we are using v1. (v1->nospace_cache, v1->v2, nospace_cache->v1, v2->v1).
Since the mechanism for writing out the cache generation is transaction commit, but we want some finer grained control over when we un-set it, we can't just rely on the SPACE_CACHE mount option, and introduce an fs_info flag that mount can use when it wants to unset the generation.
--- fs/btrfs/ctree.h | 3 +++ fs/btrfs/disk-io.c | 8 ++++++++ fs/btrfs/free-space-cache.c | 28 ++++++++++++++++++++++++++++ fs/btrfs/free-space-cache.h | 3 +++ fs/btrfs/super.c | 4 +--- fs/btrfs/transaction.c | 2 ++ 6 files changed, 45 insertions(+), 3 deletions(-)
fs/btrfs/ctree.h +3 -0
@@ -559,6 +559,9 @@ enum {/* Indicate that the discard workqueue can service discards. */ BTRFS_FS_DISCARD_RUNNING , + +/* Indicate that we need to cleanup space cache v1 */ + BTRFS_FS_CLEANUP_SPACE_CACHE_V1, };/*
fs/btrfs/disk-io.c +8 -0
@@ -2821,6 +2821,7 @@ static int btrfs_check_uuid_tree(struct btrfs_fs_info *fs_info)int btrfs_mount_rw (struct btrfs_fs_info *fs_info) {int ret; +bool cache_opt =btrfs_test_opt (fs_info,SPACE_CACHE ); ret =btrfs_cleanup_fs_roots (fs_info);if (ret)
@@ -2853,6 +2854,12 @@ int btrfs_mount_rw(struct btrfs_fs_info *fs_info) } } +if (cache_opt !=btrfs_free_space_cache_v1_active (fs_info)) { + ret =btrfs_set_free_space_cache_v1_active (fs_info, cache_opt); +if (ret) + goto out; + } + ret =btrfs_resume_balance_async (fs_info);if (ret) goto out;
@@ -3335,6 +3342,7 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_devicereturn ret; } } +set_bit (BTRFS_FS_OPEN , &fs_info->flags);/*
fs/btrfs/free-space-cache.c +28 -0
@@ -3992,6 +3992,34 @@ int btrfs_write_out_ino_cache(struct btrfs_root *root,return ret; } +bool btrfs_free_space_cache_v1_active (struct btrfs_fs_info *fs_info) +{ +return btrfs_super_cache_generation (fs_info->super_copy); +} + +int btrfs_set_free_space_cache_v1_active (struct btrfs_fs_info *fs_info, +bool active) +{ +struct btrfs_trans_handle *trans; +int ret; + +/* +* update_super_roots will appropriately set +* fs_info->super_copy->cache_generation based on the SPACE_CACHE +* option, so all we have to do is trigger a transaction commit. +*/ + trans =btrfs_start_transaction (fs_info->tree_root,0 ); +if (IS_ERR (trans)) +return PTR_ERR (trans); + +if (!active) +set_bit (BTRFS_FS_CLEANUP_SPACE_CACHE_V1 , &fs_info->flags); + + ret =btrfs_commit_transaction (trans); +clear_bit (BTRFS_FS_CLEANUP_SPACE_CACHE_V1 , &fs_info->flags); +return ret; +} +#ifdef CONFIG_BTRFS_FS_RUN_SANITY_TESTS /* * Use this if you need to make a bitmap or extent entry specifically, it
fs/btrfs/free-space-cache.h +3 -0
@@ -148,6 +148,9 @@ int btrfs_trim_block_group_bitmaps(struct btrfs_block_group *block_group, u64 *trimmed, u64 start, u64 end, u64 minlen, u64 maxlen, bool async); +bool btrfs_free_space_cache_v1_active (struct btrfs_fs_info *fs_info); +int btrfs_set_free_space_cache_v1_active (struct btrfs_fs_info *fs_info, +bool active);/* Support functions for running our sanity tests */ #ifdef CONFIG_BTRFS_FS_RUN_SANITY_TESTS int test_add_free_space_entry(struct btrfs_block_group *cache,
fs/btrfs/super.c +1 -3
@@ -511,7 +511,6 @@ int btrfs_parse_options(struct btrfs_fs_info *info, char *options, {substring_t args[MAX_OPT_ARGS ];char *p, *num; -u64 cache_gen;int intarg;int ret =0 ;char *compress_type;
@@ -521,10 +520,9 @@ int btrfs_parse_options(struct btrfs_fs_info *info, char *options,bool saved_compress_force;int no_compress =0 ; - cache_gen =btrfs_super_cache_generation (info->super_copy);if (btrfs_fs_compat_ro (info,FREE_SPACE_TREE ))btrfs_set_opt (info->mount_opt,FREE_SPACE_TREE ); -else if (cache_gen) +else if (btrfs_free_space_cache_v1_active (info))btrfs_set_opt (info->mount_opt,SPACE_CACHE );/*
fs/btrfs/transaction.c +2 -0
@@ -1761,6 +1761,8 @@ static void update_super_roots(struct btrfs_fs_info *fs_info) super->root_level = root_item->level;if (btrfs_test_opt (fs_info,SPACE_CACHE )) super->cache_generation = root_item->generation; +else if (test_bit (BTRFS_FS_CLEANUP_SPACE_CACHE_V1 , &fs_info->flags)) + super->cache_generation =0 ;if (test_bit (BTRFS_FS_UPDATE_UUID_TREE_GEN , &fs_info->flags)) super->uuid_tree_generation = root_item->generation; }
Signature · 1 line
2.24.1
PATCH v4 5/8 btrfs: use sb state to print space_cache mount option
In reply to Boris BurkovTo make the contents of /proc/mounts better match the actual state of the file system, base the display of the space cache mount options off the contents of the super block rather than the last mount options passed in. Since there are many scenarios where the mount will ignore a space cache option, simply showing the passed in option is misleading.
For example, if we mount with -o remount,space_cache=v2 on a read-write file system without an existing free space tree, we won't build a free space tree, but /proc/mounts will read space_cache=v2 (until we mount again and it goes away)
cache_generation is set iff space_cache=v1, FREE_SPACE_TREE is set iff space_cache=v2, and if neither is the case, we print nospace_cache.
--- fs/btrfs/super.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/btrfs/super.c +2 -2
@@ -1427,9 +1427,9 @@ static int btrfs_show_options(struct seq_file *seq, struct dentry *dentry)seq_puts (seq,",discard=async" );if (!(info->sb->s_flags &SB_POSIXACL ))seq_puts (seq,",noacl" ); -if (btrfs_test_opt (info,SPACE_CACHE )) +if (btrfs_free_space_cache_v1_active (info))seq_puts (seq,",space_cache" ); -else if (btrfs_test_opt (info,FREE_SPACE_TREE )) +else if (btrfs_fs_compat_ro (info,FREE_SPACE_TREE ))seq_puts (seq,",space_cache=v2" );else seq_puts (seq,",nospace_cache" );
Signature · 1 line
2.24.1
PATCH v4 6/8 btrfs: warn when remount will not create the free space tree
In reply to Boris BurkovIf the remount is ro->ro, rw->ro, or rw->rw, we will not create the free space tree. This can be surprising, so print a warning to dmesg to make the failure more visible.
--- fs/btrfs/super.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
fs/btrfs/super.c +14 -0
@@ -1859,6 +1859,20 @@ static int btrfs_remount(struct super_block *sb, int *flags, char *data)btrfs_resize_thread_pool (fs_info, fs_info->thread_pool_size, old_thread_pool_size); +if (btrfs_test_opt (fs_info,FREE_SPACE_TREE ) && + !btrfs_fs_compat_ro (fs_info,FREE_SPACE_TREE ) && + ((!sb_rdonly (sb) || *flags &SB_RDONLY ))) { +btrfs_warn (fs_info, +"remount supports enabling free space tree only from ro to rw" ); +/* +* if we aren't building the free space tree, reset +* the space cache options to what they were before +*/ +btrfs_clear_opt (fs_info->mount_opt,FREE_SPACE_TREE ); +if (btrfs_free_space_cache_v1_active (fs_info)) +btrfs_set_opt (fs_info->mount_opt,SPACE_CACHE ); + } +if ((bool )(*flags &SB_RDONLY ) ==sb_rdonly (sb)) goto out;
Signature · 1 line
2.24.1
PATCH v4 7/8 btrfs: remove free space items when disabling space cache v1
In reply to Boris BurkovWhen the file system transitions from space cache v1 to v2 or to nospace_cache, it removes the old cached data, but does not remove the FREE_SPACE items nor the free space inodes they point to. This doesn't cause any issues besides being a bit inefficient, since these items no longer do anything useful.
To fix it, when we are mounting, and plan to disable the space cache, destroy each block group's free space item and free space inode. The code to remove the items is lifted from the existing use case of removing the block group, with a light adaptation to handle whether or not we have already looked up the free space inode.
References: https://github.com/btrfs/btrfs-todo/issues/5
--- fs/btrfs/block-group.c | 39 +------------- fs/btrfs/free-space-cache.c | 101 ++++++++++++++++++++++++++++++++++-- fs/btrfs/free-space-cache.h | 3 ++ 3 files changed, 102 insertions(+), 41 deletions(-)
fs/btrfs/block-group.c +2 -37
@@ -892,8 +892,6 @@ int btrfs_remove_block_group(struct btrfs_trans_handle *trans,struct btrfs_path *path;struct btrfs_block_group *block_group;struct btrfs_free_cluster *cluster; -struct btrfs_root *tree_root = fs_info->tree_root; -struct btrfs_key key;struct inode *inode;struct kobject *kobj =NULL ;int ret;
@@ -971,42 +969,9 @@ int btrfs_remove_block_group(struct btrfs_trans_handle *trans,spin_unlock (&trans->transaction->dirty_bgs_lock);mutex_unlock (&trans->transaction->cache_write_mutex); -if (!IS_ERR (inode)) { - ret =btrfs_orphan_add (trans,BTRFS_I (inode)); -if (ret) { -btrfs_add_delayed_iput (inode); - goto out; - } -clear_nlink (inode); -/* One for the block groups ref */ -spin_lock (&block_group->lock); -if (block_group->iref) { - block_group->iref =0 ; - block_group->inode =NULL ; -spin_unlock (&block_group->lock); -iput (inode); - }else { -spin_unlock (&block_group->lock); - } -/* One for our lookup ref */ -btrfs_add_delayed_iput (inode); - } - - key.objectid =BTRFS_FREE_SPACE_OBJECTID ; - key.type =0 ; - key.offset = block_group->start; - - ret =btrfs_search_slot (trans, tree_root, &key, path,-1 ,1 ); -if (ret <0 ) + ret =btrfs_remove_free_space_inode (trans, inode, block_group); +if (ret) goto out; -if (ret >0 ) -btrfs_release_path (path); -if (ret ==0 ) { - ret =btrfs_del_item (trans, tree_root, path); -if (ret) - goto out; -btrfs_release_path (path); - }spin_lock (&fs_info->block_group_cache_lock); rb_erase(&block_group->cache_node,
fs/btrfs/free-space-cache.c +97 -4
127 lines not on this page · raw message
fs/btrfs/free-space-cache.h +3 -0
@@ -84,6 +84,9 @@ struct inode *lookup_free_space_inode(struct btrfs_block_group *block_group,int create_free_space_inode (struct btrfs_trans_handle *trans,struct btrfs_block_group *block_group,struct btrfs_path *path); +int btrfs_remove_free_space_inode (struct btrfs_trans_handle *trans, +struct inode *inode, +struct btrfs_block_group *block_group);int btrfs_check_trunc_cache_free_space (struct btrfs_fs_info *fs_info,struct btrfs_block_rsv *rsv);
Signature · 1 line
2.24.1
PATCH v4 8/8 btrfs: skip space_cache v1 setup when not using it
In reply to Boris BurkovIf we are not using space cache v1, we should not create the free space object or free space inodes. This comes up when we delete the existing free space objects/inodes when migrating to v2, only to see them get recreated for every dirtied block group.
--- fs/btrfs/block-group.c | 3 +++ 1 file changed, 3 insertions(+)
fs/btrfs/block-group.c +3 -0
@@ -2325,6 +2325,9 @@ static int cache_save_setup(struct btrfs_block_group *block_group,int retries =0 ;int ret =0 ; +if (!btrfs_test_opt (fs_info,SPACE_CACHE )) +return 0 ; +/* * If this block group is smaller than 100 megs don't bother caching the * block group.
Signature · 1 line
2.24.1