btrfs: qgroup: Try our best to delete qgroup relations
PATCH 1/1 btrfs: qgroup: Try our best to delete qgroup relations
When we try to delete qgroups, we're pretty cautious, we make sure both qgroups exist and there is a relationship between them, then try to delete the relation.
This behavior is OK, but the problem is we need to two relation items, and if we failed the first item deletion, we error out, leaving the other relation item in qgroup tree.
Sometimes the error from del_qgroup_relation_item() could just be -ENOENT, thus we can ignore that error and continue without any problem.
Further more, such cautious behavior makes qgroup relation deletion impossible for orphan relation items.
This patch will enhance __del_qgroup_relation():
- If both qgroups and their relation items exist
Go the regular deletion routine and update their accounting if needed.
- If any qgroup or relation item doesn't exist
Then we still try to delete the orphan items anyway, but don't trigger the accounting update.
By this, we try our best to remove relation items, and can handle orphan relation items properly, while still keep the existing behavior for good qgroup tree.
--- fs/btrfs/qgroup.c | 46 +++++++++++++++++++++++++++++----------------- 1 file changed, 29 insertions(+), 17 deletions(-)
fs/btrfs/qgroup.c +29 -17
@@ -1312,8 +1312,9 @@ static int __del_qgroup_relation(struct btrfs_trans_handle *trans, u64 src,struct btrfs_qgroup *member;struct btrfs_qgroup_list *list;struct ulist *tmp; +bool found = false;int ret =0 ; -int err; +int ret2; tmp =ulist_alloc (GFP_KERNEL );if (!tmp)
@@ -1327,28 +1328,39 @@ static int __del_qgroup_relation(struct btrfs_trans_handle *trans, u64 src, member =find_qgroup_rb (fs_info, src); parent =find_qgroup_rb (fs_info, dst); -if (!member || !parent) { - ret = -EINVAL ; - goto out; - } +/* +* The parent/member pair doesn't exist, then try to delete the dead +* relation items only. +*/ +if (!member && !parent) + goto delete_item;/* check if such qgroup relation exist firstly */ list_for_each_entry (list, &member->groups, next_group) { -if (list->group == parent) - goto exist; +if (list->group == parent) { + found = true; +break ; + } } - ret = -ENOENT ; - goto out; -exist: + +delete_item: ret =del_qgroup_relation_item (trans, src, dst); - err =del_qgroup_relation_item (trans, dst, src); -if (err && !ret) - ret = err; +if (ret <0 && ret != -ENOENT ) + goto out; + ret2 =del_qgroup_relation_item (trans, dst, src); +if (ret2 <0 && ret2 != -ENOENT ) + goto out; -spin_lock (&fs_info->qgroup_lock); -del_relation_rb (fs_info, src, dst); - ret =quick_update_accounting (fs_info, tmp, src, dst,-1 ); -spin_unlock (&fs_info->qgroup_lock); +/* At least one deletion succeeded, return 0 */ +if (!ret || !ret2) + ret =0 ; + +if (found) { +spin_lock (&fs_info->qgroup_lock); +del_relation_rb (fs_info, src, dst); + ret =quick_update_accounting (fs_info, tmp, src, dst,-1 ); +spin_unlock (&fs_info->qgroup_lock); + } out:ulist_free (tmp);return ret;
Signature · 1 line
2.22.0
Quoted 22 lines · Qu Wenruo
When we try to delete qgroups, we're pretty cautious, we make sure both qgroups exist and there is a relationship between them, then try to delete the relation.
This behavior is OK, but the problem is we need to two relation items, and if we failed the first item deletion, we error out, leaving the other relation item in qgroup tree.
Sometimes the error from
del_qgroup_relation_item()could just be-ENOENT, thus we can ignore that error and continue without any problem.Further more, such cautious behavior makes qgroup relation deletion impossible for orphan relation items.
This patch will enhance
__del_qgroup_relation():
- If both qgroups and their relation items exist
Go the regular deletion routine and update their accounting if needed.- If any qgroup or relation item doesn't exist
Then we still try to delete the orphan items anyway, but don't trigger the accounting update.
Quoted 6 lines
By this, we try our best to remove relation items, and can handle orphan relation items properly, while still keep the existing behavior for good qgroup tree.
Reported-by Andrei Borzenkov <[email protected]>Signed-off-by Qu Wenruo <[email protected]>
Adding this to misc-next, please send a fstests testcase, thanks.
Quoted 23 lines · David Sterba
Quoted 22 lines · Qu Wenruo
When we try to delete qgroups, we're pretty cautious, we make sure both qgroups exist and there is a relationship between them, then try to delete the relation.
This behavior is OK, but the problem is we need to two relation items, and if we failed the first item deletion, we error out, leaving the other relation item in qgroup tree.
Sometimes the error from
del_qgroup_relation_item()could just be-ENOENT, thus we can ignore that error and continue without any problem.Further more, such cautious behavior makes qgroup relation deletion impossible for orphan relation items.
This patch will enhance
__del_qgroup_relation():
- If both qgroups and their relation items exist
Go the regular deletion routine and update their accounting if needed.- If any qgroup or relation item doesn't exist
Then we still try to delete the orphan items anyway, but don't trigger the accounting update.
Quoted 9 lines
Quoted 6 lines
By this, we try our best to remove relation items, and can handle orphan relation items properly, while still keep the existing behavior for good qgroup tree.
Reported-by Andrei Borzenkov <[email protected]>Signed-off-by Qu Wenruo <[email protected]>Adding this to misc-next, please send a fstests testcase, thanks.
That's the problem, I haven't found how the orphan relationship item is left over.
Latest kernel will already delete both of them if nothing wrong happened.
So no idea how to write one test case.
Thanks,
Qu