A query directed to database data stored across a set of files is received. The query includes predicates applied against metadata of the set of files. One or more files are removed from the set of files whose metadata does not satisfy a predicate of the plurality of predicates. Rows of the one or more remaining files of the set of files are filtered based on the one or more predicates.

In some embodiments, a method for die-level monitoring is provided. The method includes distributing user data throughout a plurality of storage nodes through erasure coding, wherein the plurality of storage nodes are housed within a chassis that couples the storage nodes. Each of the storage nodes has a non-volatile solid-state storage with non-volatile memory and the user data is accessible via the erasure coding from a remainder of the storage nodes in event of two of the storage nodes being unreachable. The method includes producing diagnostic information that diagnoses the non-volatile memory on a basis of per package, per die, per plane, per block, or per page, the producing performed by each of the plurality of storage nodes. The method includes writing the diagnostic information to a memory in the storage cluster.

Metadata including an encrypted file name can be attached to a directory entry for a file. For example, a method may include a processing device performing operations. The operations may include receiving, from a client system, a request to generate a directory entry in a distributed file system for a file. The operations may include generating the directory entry in a storage node of the plurality of storage nodes. The directory entry may include a file name and an index number. The operations may include encrypting the file name to generate an encrypted file name. The operations may include attaching the encrypted file name to the directory entry as metadata, the metadata being distinct from the file name and the index number. The metadata may be usable by the client system for decrypting the encrypted file name.

The disclosed technology relates to a system configured to receive operations data from a content management system, wherein the operations data comprises a log of operations, execute the log of operations, and update, based on execution of the log of operations, a remote tree representing a server state for content items stored on the content management system.

Embodiments for managing metadata in a high density network attached storage system. A change file list is obtained though external or internal crawler processes. A slicer creates multiple slices of the entire fileshare to enable parallel backup of the slices. A backup engine creates a separate backup containers and separate metadata files for each slice. The individual metadata files are combined into a single consolidated metadata file, and the individual metadata files are then deleted. The consolidated metadata file contains all of the elements comprising the entire fileshare, and a corresponding container ID is also added to each entry of the file. Another table contains details of the sub-assets and their backup properties. A backup agent obtains the backup IDs for the individual sub-assets, using a job ID field for a backup query operating on the single consolidated metadata file.

A method, apparatus, and system for join operations of a plurality of relations that are distributed over a plurality of storage locations over a network of computing components.

Methods, non-transitory machine readable media, and computing devices that ensure correctness of file system analytics are disclosed. With this technology, a first generation number for a volume is incremented in response to a modification of a rule set that defines properties of objects of a file system associated with the volume. A determination is made when a second generation number in a first inode for a first one of the objects matches the first generation number. The first inode is identified based on a traversal of a directory tree associated with the file system. The modified rule set is applied to the properties for the first one of the objects to obtain values, when the second generation number fails to match the first generation number. Analytics data is output after the traversal has completed. The analytics data is generated in response to a query and is based on the values.

Provided herein are systems and methods for an efficient method of replicating share objects to remote deployments. An example method includes receiving, at a first deployment in a data exchange, a refresh message from a second deployment in the data exchange, wherein the first deployment comprises a database that stores a database object. The method also includes, in response to receiving the refresh message, retrieving, at the first deployment, a share grant from a share object of the first deployment and transmitting, by a processing device of the first deployment, a message including the share grant to the second deployment. The share grant includes a reference to the database object and allows a consumer to use the database object.

Disclosed are a storage node and method. The storage node includes a storage device, and a smart NIC, where the smart NIC is configured to receive a write request including original data to be stored in the DFS, and responsive to the receiving, generate parity data by performing erasure coding on the original data, and store the parity data and the original data directly from the smart NIC to the storage device, and receive, from a client device or another client device, a read request for data stored in the DFS, where the smart NIC is further configured to, responsive to receiving the read request, fetch a portion of the original data and the parity data directly from the storage device, and recover another portion of the original data by applying forward error correction (FEC) decoding to the fetched portion of the original data using the fetched parity data.

Systems, methods, and machine-readable media are disclosed for determining an optimal location for creating a new volume (or volumes) on a storage platform and placing the volume at the determined location. A resource tracker collects resource use and/or limits data and stores it in a database. A volume placement service receives a volume deployment specification having constraints for creating a new volume, particularly including instructions relating to relationships between volumes to be created. The volume placement service retrieves the data from the database. The volume placement service identifies an optimal location for the volume based at least in part on given constraints from the specification and the resource usage data. The system places the requested volume at the determined location.