Lines Matching defs:blockref
461 * case which means no data associated with the blockref, and
553 * HAMMER2 directory entry header (embedded in blockref) exactly 16 bytes
571 * A blockref references a single media item, which typically can be a
574 * The primary feature a blockref represents is the ability to validate
576 * anything propagates up the blockref tree all the way to the root, replacing
581 * blockref but later expanded it to 128 bytes to be able to support the
602 * NOTE: The range of keys represented by the blockref is (key) to
618 * A number of blockref fields are reserved and should generally be set to
621 * FUTURE BLOCKREF EXPANSION
631 uint8_t flags; /* blockref flags */
707 #define HAMMER2_BLOCKREF_BYTES 128 /* blockref struct in bytes */
713 * On-media and off-media blockref types.
797 hammer2_blockref_t blockref[HAMMER2_SET_COUNT];
846 * Typically integrated with the blockref type in the upper 8 bits
861 * blockref[0] : 4EB
862 * blockref[1] : 4EB
863 * blockref[2] : 4EB
864 * blockref[3] : 4EB
869 * blockref[0] : 1GB,256GB,64TB,16PB
870 * blockref[1] : 1GB,256GB,64TB,16PB
872 * blockref[255] : 1GB,256GB,64TB,16PB
915 * Directories represent one inode per blockref. Inodes are not laid out
927 * recorded on a blockref-by-blockref basis.
1132 * However, there may be shortcutted blockref updates present from deep in
1249 * blockref is used.
Indexes created Wed Oct 01 15:09:59 GMT 2025