Skip to content

Commit c147aaa

Browse files
committed
btrfs-progs: clarify unlinked and deleted terminology for subvolumes
Recent patches updated stale qgroup handling, using 'unlinked' and 'dropped' where we otherwise use 'deleted' and 'cleaned'. Signed-off-by: David Sterba <dsterba@suse.com>
1 parent 7f3ab46 commit c147aaa

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

Documentation/btrfs-qgroup.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,8 @@ strings:
162162
The toplevel subvolume
163163

164164
`<under deletion>`
165-
The subvolume is unlinked, but not yet fully deleted.
165+
The subvolume has been deleted (it's directory removed), but the
166+
subvolume metadata not not yet fully cleaned.
166167

167168
`<squota space holder>`
168169
For simple quota mode only.

cmds/qgroup.c

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -83,10 +83,11 @@ struct btrfs_qgroup {
8383
u64 qgroupid;
8484

8585
/*
86-
* NULL for qgroups with level > 0 or the subvolume is unlinked.
86+
* NULL for qgroups with level > 0 or the subvolume is deleted but not
87+
* yet fully cleaned.
8788
*
88-
* An unlinked subvolume doesn't mean it has been fully dropped, so
89-
* callers should not rely on this to determine if a qgroup is stale.
89+
* A deleted subvolume means it hasn't been fully cleaned, so callers
90+
* should not rely on this to determine if a qgroup is stale.
9091
*
9192
* This member is only to help locating the path of the corresponding
9293
* subvolume.

0 commit comments

Comments
 (0)