btrfs-qgroup - control the quota group of a btrfs filesystem
btrfs qgroup <subcommand> <args>
btrfs qgroup is used to control quota group (qgroup) of a btrfs filesystem.
To use qgroup you need to enable quota first using btrfs quota enable command.
Qgroup is not stable yet and will impact performance in current mainline kernel (v4.14).
Quota groups or qgroup in btrfs make a tree hierarchy, the leaf qgroups are attached to subvolumes. The size limits are set per qgroup and apply when any limit is reached in tree that contains a given subvolume.
The limits are separated between shared and exclusive and reflect the extent ownership. For example a fresh snapshot shares almost all the blocks with the original subvolume, new writes to either subvolume will raise towards the exclusive limit.
The qgroup identifiers conform to level/id where level 0 is reserved to the qgroups associated with subvolumes. Such qgroups are created automatically.
The qgroup hierarchy is built by commands create and assign.
If the qgroup of a subvolume is destroyed, quota about the subvolume will not be functional until qgroup 0/<subvolume id> is created again.
assign [options] <src> <dst> <path>
create <qgroupid> <path>
For the 0/<subvolume id> qgroup, a qgroup can be created even before the subvolume is created.
destroy <qgroupid> <path>
If a qgroup is not isolated, meaning it is a parent or child qgroup, then it can only be destroyed after the relationship is removed.
limit [options] <size>|none [<qgroupid>] <path>
If <qgroupid> is not given, qgroup of the subvolume identified by <path> is used if possible.
remove <src> <dst> <path>
show [options] <path>
<attr> can be one or more of qgroupid,rfer,excl,max_rfer,max_excl.
Prefix '+' means ascending order and '-' means descending order of <attr>. If no prefix is given, use ascending order by default.
If multiple <attr>s is given, use comma to separate.
The rescan reads all extent sharing metadata and updates the respective qgoups accordingly.
The information consists of bytes owned exclusively (excl) or shared/referred to (rfer). There’s no explicit information about which extents are shared or owned exclusively. This means when qgroup relationship changes, extent owners change and qgroup numbers are no longer consistent unless we do a full rescan.
However there are cases where we can avoid a full rescan, if a subvolume whose rfer number equals its excl number, which means all bytes are exclusively owned, then assigning/removing this subvolume only needs to add/subtract rfer number from its parent qgroup. This can speed up the rescan.
Example 1. Make a parent group that has two quota group children
Given the following filesystem mounted at /mnt/my-vault
Label: none uuid: 60d2ab3b-941a-4f22-8d1a-315f329797b2
Total devices 1 FS bytes used 128.00KiB
devid 1 size 5.00GiB used 536.00MiB path /dev/vdb
Enable quota and create subvolumes. Check subvolume ids.
$ cd /mnt/my-vault $ btrfs quota enable . $ btrfs subvolume create a $ btrfs subvolume create b $ btrfs subvolume list . ID 261 gen 61 top level 5 path a ID 262 gen 62 top level 5 path b
Create qgroup and set limit to 10MiB.
$ btrfs qgroup create 1/100 . $ btrfs qgroup limit 10M 1/100 . $ btrfs qgroup assign 0/261 1/100 . $ btrfs qgroup assign 0/262 1/100 .
And check qgroups.
$ btrfs qgroup show . qgroupid rfer excl -------- ---- ---- 0/5 16.00KiB 16.00KiB 0/261 16.00KiB 16.00KiB 0/262 16.00KiB 16.00KiB 1/100 32.00KiB 32.00KiB
btrfs qgroup returns a zero exit status if it succeeds. Non zero is returned in case of failure.
btrfs is part of btrfs-progs. Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for further details.