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 /* device stats in the device tree */
59 /* for storing balance parameters in the root tree */
60 #define BTRFS_BALANCE_OBJECTID -4ULL
63 #define BTRFS_ORPHAN_OBJECTID -5ULL
66 #define BTRFS_TREE_LOG_OBJECTID -6ULL
67 #define BTRFS_TREE_LOG_FIXUP_OBJECTID -7ULL
70 #define BTRFS_TREE_RELOC_OBJECTID -8ULL
71 #define BTRFS_DATA_RELOC_TREE_OBJECTID -9ULL
75 * this allows them to share the logging tree
78 #define BTRFS_EXTENT_CSUM_OBJECTID -10ULL
81 #define BTRFS_FREE_SPACE_OBJECTID -11ULL
87 #define BTRFS_FREE_INO_OBJECTID -12ULL
90 #define BTRFS_MULTIPLE_OBJECTIDS -255ULL
96 #define BTRFS_LAST_FREE_OBJECTID -256ULL
101 * the device items go into the chunk tree. The key is in the form
133 * The merkle tree items:
136 * These also start at offset 0, and correspond to the merkle tree bytes. When
137 * fsverity asks for page 0 of the merkle tree, we pull up one page starting at
145 /* reserve 2-15 close to the inode for later flexibility */
148 * dir items are the name -> inode pointers in a directory. There is one
161 * extent csums are stored in a separate tree and hold csums for
167 * root items point to tree roots. They are typically in the root
168 * tree used by the super block to find all the other trees
186 * extent items are in the extent map tree. These record which blocks
193 * the length, so we save the level in key->offset instead of the length.
214 * Every block group is represented in the free space tree by a free space info
255 * Records the child-parent relationship of qgroups. For
268 * The key type for tree items that are stored persistently, but do not need to
269 * exist for extended period of time. The items can exist in any tree.
275 * - balance status item
286 * The key type for tree items that are stored persistently and usually exist
288 * information, stats or preference values. The item can exist in any tree.
294 * - device statistics, store IO stats in the device tree, one key for all
301 * Persistently stores the device replace state in the device tree.
308 * These items are part of the filesystem UUID tree.
359 * The key defines the order in the tree, and so it also defines (optimal)
388 /* the internal btrfs device id */
391 /* size of the device */
397 /* optimal io alignment for this device */
400 /* optimal io width for this device */
403 /* minimal io size for this device */
406 /* type and info about this device */
409 /* expected generation for this device */
413 * starting byte of this partition on the device,
421 /* seek speed 0-100 where 100 is fastest */
424 /* bandwidth 0-100 where 100 is fastest */
427 /* btrfs generated uuid for this device */
430 /* uuid of FS who owns this device */
519 /* following flags only apply to tree blocks */
552 * field points back to the chunk allocation mapping tree that allocated
553 * the extent. The chunk tree uuid field is a way to double check the owner
626 * Internal in-memory flag that a subvolume has been marked for deletion but
667 __le64 stransid; /* trans when sent. non-zero for received subvol */
668 __le64 rtransid; /* trans when received. non-zero for received subvol */
704 * BTRFS_BALANCE_ARGS_USAGE_RANGE - range syntax, min..max
736 * BTRFS_BALANCE_ARGS_LIMIT_RANGE - the extend version can use minimum
913 * fs_info->avail_*_alloc_bits (in-memory) and balance item fields
914 * (on-disk). The corresponding on-disk bit in chunk.type is reserved
971 * with a non-qgroup-aware version.
1022 * Merkle tree for encrypted verity files. These 128 bits are for the