Lines Matching +full:device +full:- +full:tree
1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
20 /* holds pointers to all of the tree roots */
27 * chunk tree stores translations from logical -> physical block numbering
28 * the super block points to the chunk tree
33 * stores information about which areas of a given device are in use.
34 * one per device. The tree of tree roots points to the device tree
41 /* directory objectid inside the root tree */
56 /* Holds the block group items for extent tree v2. */
59 /* device stats in the device tree */
62 /* for storing balance parameters in the root tree */
63 #define BTRFS_BALANCE_OBJECTID -4ULL
66 #define BTRFS_ORPHAN_OBJECTID -5ULL
69 #define BTRFS_TREE_LOG_OBJECTID -6ULL
70 #define BTRFS_TREE_LOG_FIXUP_OBJECTID -7ULL
73 #define BTRFS_TREE_RELOC_OBJECTID -8ULL
74 #define BTRFS_DATA_RELOC_TREE_OBJECTID -9ULL
78 * this allows them to share the logging tree
81 #define BTRFS_EXTENT_CSUM_OBJECTID -10ULL
84 #define BTRFS_FREE_SPACE_OBJECTID -11ULL
90 #define BTRFS_FREE_INO_OBJECTID -12ULL
93 #define BTRFS_MULTIPLE_OBJECTIDS -255ULL
99 #define BTRFS_LAST_FREE_OBJECTID -256ULL
104 * the device items go into the chunk tree. The key is in the form
136 * The merkle tree items:
139 * These also start at offset 0, and correspond to the merkle tree bytes. When
140 * fsverity asks for page 0 of the merkle tree, we pull up one page starting at
148 /* reserve 2-15 close to the inode for later flexibility */
151 * dir items are the name -> inode pointers in a directory. There is one
166 * extent csums are stored in a separate tree and hold csums for
172 * root items point to tree roots. They are typically in the root
173 * tree used by the super block to find all the other trees
191 * extent items are in the extent map tree. These record which blocks
198 * the length, so we save the level in key->offset instead of the length.
219 * Every block group is represented in the free space tree by a free space info
260 * Records the child-parent relationship of qgroups. For
273 * The key type for tree items that are stored persistently, but do not need to
274 * exist for extended period of time. The items can exist in any tree.
280 * - balance status item
291 * The key type for tree items that are stored persistently and usually exist
293 * information, stats or preference values. The item can exist in any tree.
299 * - device statistics, store IO stats in the device tree, one key for all
306 * Persistently stores the device replace state in the device tree.
313 * These items are part of the filesystem UUID tree.
364 * The key defines the order in the tree, and so it also defines (optimal)
393 /* the internal btrfs device id */
396 /* size of the device */
402 /* optimal io alignment for this device */
405 /* optimal io width for this device */
408 /* minimal io size for this device */
411 /* type and info about this device */
414 /* expected generation for this device */
418 * starting byte of this partition on the device,
426 /* seek speed 0-100 where 100 is fastest */
429 /* bandwidth 0-100 where 100 is fastest */
432 /* btrfs generated uuid for this device */
435 /* uuid of FS who owns this device */
524 /* following flags only apply to tree blocks */
557 * field points back to the chunk allocation mapping tree that allocated
558 * the extent. The chunk tree uuid field is a way to double check the owner
631 * Internal in-memory flag that a subvolume has been marked for deletion but
672 __le64 stransid; /* trans when sent. non-zero for received subvol */
673 __le64 rtransid; /* trans when received. non-zero for received subvol */
709 * BTRFS_BALANCE_ARGS_USAGE_RANGE - range syntax, min..max
741 * BTRFS_BALANCE_ARGS_LIMIT_RANGE - the extend version can use minimum
905 * fs_info->avail_*_alloc_bits (in-memory) and balance item fields
906 * (on-disk). The corresponding on-disk bit in chunk.type is reserved
963 * with a non-qgroup-aware version.
1018 * Merkle tree for encrypted verity files. These 128 bits are for the