Abstract: Embodiments of the present disclosure relate to creating and maintaining a separate compliance store within a domain. Files that are committed within the domain are linked to the compliance store using canonical links. Canonical links are guaranteed to be non-erasable and non-rewritable for the duration of their retention period. When using a source cluster of nodes as a primary production cluster and a target cluster of nodes as a backup cluster, file data and canonical links can be synced from the source cluster to the target cluster to maintain compliance with data retention rules. Non-canonical links can be modified as necessary to ensure snapshot consistency when failover or failback occurs between a source cluster of nodes and a target cluster of nodes.

Abstract: Techniques are provided for inlining data in inodes of a file system. In an example, data (e.g., a file) is to be written to storage. Where the data is small enough to fit in an inode, it can be written to a dynamic area of the inode. Where dynamic attributes of the inode conflict with storing the data, the dynamic attributes can be spilled to a metadata block. Where the inlined data becomes too large to be stored in the inode, it can be spilled to a data block, and a metadata tree can be written to the inode. Where data that was previously too large to inline is truncated so that now it can be written to the inode, the data is inlined in the inode from a data block.

Abstract: Techniques are provided for inlining data in inodes of a file system. In an example, data (e.g., a file) is to be written to storage. Where the data is small enough to fit in an inode, it can be written to a dynamic area of the inode. Where dynamic attributes of the inode conflict with storing the data, the dynamic attributes can be spilled to a metadata block. Where the inlined data becomes too large to be stored in the inode, it can be spilled to a data block, and a metadata tree can be written to the inode. Where data that was previously too large to inline is truncated so that now it can be written to the inode, the data is inlined in the inode from a data block.

Abstract: Implementations are provided herein for sending event notifications based on modifications to files and/or directories. When a file is read, modified or changed under the conditions for a registered event notification, a consistency point can be established. An impact list can then be determined based on the target. It can then be determined whether the version of event caches associated with the files and folders identified in the impact list match a global event cache version determined at the time of the consistency point. If the event caches are an old version, the system call can be restarted, and the event caches can be rebuilt to the current version. If the event caches of the impact list are current, the file system operation can be performed, and notifications can be sent based on the set of listeners identified within the current set of event caches.