Igneous Systems, Inc.

Emc Corporation

Rubrik, Inc.

Igeneous Systems, Inc.

Jeffrey Douglas Hughes

Triantaphyllos Byron Rakitzis

Kiran V Bhageshpur

Eric Michael Lemar

Timothy Rex Martin

Daniel Hefenbrock

Anu Engineer

Darrick Peter Lew

Justin Husted

Jonathan Mark Walton

Alain Hamel

Nathan Edward Dire

Harsha Mahuli

Sean MacQueen Smith

Steven Lockhart

Nathan Koppes

Kalen Albert Petersen

Triantaphyllos Rakitzîs

Embodiments are directed to managing file systems over a network. A hierarchical index may be provided based on a file system and a plurality of objects stored in the file system A token index may be generated based on the hierarchical index. Each token may be a portion of the path of the objects Metric indices may be generated based on the hierarchical index and a plurality of metrics associated with the objects such that the metrics indices include one or more rows that corresponds to a place position for a metric value. Employing the token index and the metric indices to generate query results based on the plurality of metrics associated with the objects.

Aggregating metrics in distributed file systems

Embodiments are directed to managing file systems. Update information associated with a change of a metric associated with a target object may be provided. A journal that includes a base bin that includes base records that associate the metric with each object in the file system. Records that include the change of the metric associated with the ancestors of target object may be generated. Another record that includes the change of the metric associated with the target object may be generated. A level bin associated with the base bin of the journal may be provided based on the update information. The records may be stored in the level bin using a sort order based on the ordering of the base bin records. In response a query, the journal may be employed to reduce latency in generating query results.

Aggregating metrics in file systems using structured journals

Embodiments are directed towards a controller that provides individual network accessibility to a storage drive. The controller may include a first connector operative to couple with a storage-drive connector, a second connector operative to couple with a backplane connector of a multi-storage-drive chassis, memory, and processor. The controller may convert communication received through the first connector into an Ethernet protocol for output through the second connector, and convert communication received through the second connector into a storage-drive protocol for output through the first connector. A physical shape of the controller may fit adjacent to the storage-drive connector and occupy less space than is bounded by peripheral edges of an end of a separate housing of a storage drive coupled to the storage-drive connector. The controller may manage power provided to the storage drive and may coordinate with other controllers to manage power-up sequences of multiple storage drives.

Network addressable storage controller with storage drive profile comparison

Embodiments are directed towards managing the distribution of tasks in a storage system. An execution path for tasks may be generated based on the type of the task and characteristics of the storage system such that the execution path includes storage computers in a storage system. The tasks may be provided to each storage computer in the execution path. A working set of intermediate results may be generated on the storage computer in the execution path. If there is more than one storage computer in the execution path, working sets may be iteratively communicated to a next storage computer in the execution path such that the next storage computer employs a previously generated working set to generate a next working set until each storage computer in the execution path has been employed to generate a working set. The results may be stored on the storage computers.

Distributed storage data repair air via partial data rebuild within an execution path

Embodiments are directed to storing data in a storage system. Data portions may be provided from blocks of write data provided by client computers. A storage location identifier may be associated with each data portion based on the content of the each data portion. Data portions may be stored in a memory buffer that may correspond to the storage location identifiers. If an amount of data stored in the memory buffer exceeds a threshold value, or if a maximum latency time expires, the data portions are stored on a storage location that corresponds to the memory buffer, such that, the maximum latency time is selected to prevent a collision caused by simultaneously storing of data portions in the same storage location. A write acknowledgement message may be provided to the client computers indicating that the blocks of write data are stored to stable storage.

Latency optimizing for scalable journaling

Various embodiments are directed to a data storage chassis for storing a plurality of non-specific storage drives, corresponding wireless controllers, and one or more radio adapters. The storage drives are operative to communicate with another network device over a network. A storage drive wirelessly communicates with other storage drives of the chassis, as well as one or more radio adapters of the chassis. The wireless controller corresponding to a storage drive is operative to wirelessly communicate with other wireless controllers corresponding to other storage drives and also with one or more radio adapters via wireless waveguides of the chassis. The one or more radio adapters are operative to communicate with other network devices external to the chassis and serve as access points to the chassis. Because the storage drives, the corresponding controllers, and the radio adapters communicate via wireless signals transmitted along waveguides, the chassis is a wireless chassis.

Wireless data storage chassis

Embodiments are directed towards managing designations of a plurality of files across multiple clusters. Files may be designated as primary files or secondary files. Primary files at one cluster may be asynchronously replicated at another cluster as secondary files. Secondary files may be synchronously validated with remote primary files based on local file access requests. If a write request for a local secondary file is provided, then the local file may be designated as the primary file and the remote file may be designated as the secondary file. Local access may then be provided to the local primary file. If a read request for a local secondary file is provide, then local access may be provided to the local secondary file without changing file designations. In some embodiments, file designations may be preemptively changed based on a file change designation schedule for clusters at different geographic locations.

Geographic distribution of files

The various embodiments are directed towards enabling access to snapshotted versions of files in a distributed file system. The distributed file system may receive a file system operation request that includes at least an entry-ID and a snapshot-ID. File system operation requests may include operations such as reads, writes, moves, or the like. Directory entries that match the entry-ID and the snapshot-ID may be looked up and retrieved from the distributed file system. The retrieved directory entries may also be arranged to include a generation-ID. In the directory entry matching the snapshot-ID, if the generation-ID and the snapshot-ID are different, another directory entry may be looked up from the distributed file system using the entry-ID and the generation-ID. Then the initially requested file system operation may be performed on the retrieved directory entry.

Dynamic network access of snapshotted versions of a clustered file system

Embodiments are directed towards managing data storage that may experience a data failure. If a repair event is associated with a data storage failure, a new repair task may be generated and added to a task list. A priority value for each repair task in the task list may be determined based in part on the mean-time-to-data-loss (MTTDL) value associated with each repair task in the task list such that a lower MTTDL may indicate a higher priority value over a lower MTTDL. One or more repair tasks may be promoted to become active repair tasks based on the priority value the repair tasks such that the promoted repair tasks have a higher priority that than other repair tasks in the task list, if any. Each active repair task may be executed to repair one or more associated the storage failures.

Prioritized repair of data storage failures

Embodiments are directed towards replication and restoration of file system objects stored on file system clusters. Modified file system objects may be tracked using a snapshot tracking file corresponding to a snapshot. The snapshot tracking file may be employed to generate a snapshot change set. The snapshot change set may be used to restore a file system cluster to a version corresponding to a snapshot by reversing the changes in the snapshot change set. Also, a snapshot change set may be used to replicate file system objects by committing the included changes on another file system cluster. If a primary file system cluster becomes unavailable the file system may failover to the secondary file system cluster. If the primary file system cluster later becomes available it may be restored by using snapshot change sets generated on the secondary file system cluster.

Replication and restoration

Embodiments are directed towards efficient erasure coding for storage systems. A smallest integer in a set may be determined based on a number of storage devices in the storage system such that the determined integer is greater or equal to the number of storage devices. The smallest integer in the set may be determined from the set {2&#x2212;1} where N is an integer based on the number of storage devices. A matrix may be generated based on a number of columns equal to the determined integer and a number of rows equal to the number of columns plus a number of global repair symbol devices and plus a number of virtual repair symbol devices. Each virtual repair symbol device enables an additional of level of protection against failures in the storage system.

Efficiency for erasure encoding

Embodiments are directed towards writing data to a shingle of storage devices enabling storage devices not in the shingle to be turned off. A shingle may be a sub-group of more than one storage devices selected from a larger group of storage devices. A plurality of data repair sets may be written to various subsets of the storage devices in the shingle. Each data repair set may include data block(s) and repair block(s)&#x2014;with each block being stored on a different storage device in the shingle. When a condition is satisfied, the shingle may be modified to either remove at least one storage device from the shingle, add at least one other storage device to the shingle, or both. In various embodiments, the at least one other storage device may be a storage device in the group of storage devices that is not currently included in the shingle.

Growing community of inventors

Seattle, WA, United States of America

Jeffrey Douglas Hughes