RepoMirrors
/
btrfs-progs
mirror of https://github.com/kdave/btrfs-progs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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>
This commit is contained in:
David Sterba 2024-05-17 18:13:18 +02:00
parent 7f3ab46400
commit c147aaa59b
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Documentation/btrfs-qgroup.rst
View File

@ -162,7 +162,8 @@ strings:
The toplevel subvolume
`<under deletion>`
The subvolume is unlinked, but not yet fully deleted.
The subvolume has been deleted (it's directory removed), but the
subvolume metadata not not yet fully cleaned.
`<squota space holder>`
For simple quota mode only.

7
cmds/qgroup.c
View File

@ -83,10 +83,11 @@ struct btrfs_qgroup {
u64 qgroupid;
/*
* NULL for qgroups with level > 0 or the subvolume is unlinked.
* NULL for qgroups with level > 0 or the subvolume is deleted but not
* yet fully cleaned.
*
* An unlinked subvolume doesn't mean it has been fully dropped, so
* callers should not rely on this to determine if a qgroup is stale.
* A deleted subvolume means it hasn't been fully cleaned, so callers
* should not rely on this to determine if a qgroup is stale.
*
* This member is only to help locating the path of the corresponding
* subvolume.