Christopher M Corey

20210334160, Oct 28, 2021

Apr 24, 2020

16/858376

- Sunnyvale CA, US
Daniel David McCarthy - Erie CO, US
Christopher Clark Corey - Boulder CO, US
Austino Nicholas Longo - Lafayette CO, US
Christopher Cason - Boulder CO, US

G06F 11/10
H03M 13/15

A technique provides efficient data protection, such as erasure coding, for data blocks of volumes served by storage nodes of a cluster. Data blocks associated with write requests of unpredictable client workload patterns may be compressed. A set of the compressed data blocks may be selected to form a write group and an erasure code may be applied to the group to algorithmically generate one or more encoded blocks in addition to the data blocks. Due to the unpredictability of the data workload patterns, the compressed data blocks may have varying sizes. A pool of the various-sized compressed data blocks may be established and maintained from which the data blocks of the write group are selected. Establishment and maintenance of the pool enables selection of compressed data blocks that are substantially close to the same size and, thus, that require minimal padding.

20210334241, Oct 28, 2021

Apr 24, 2020

16/858294

- Sunnyvale CA, US
Austino Nicholas Longo - Lafayette CO, US
Christopher Clark Corey - Boulder CO, US
Sneheet Kumar Mishra - Lafayette CO, US

G06F 16/182
G06F 16/16
G06F 12/02

A technique transitions data blocks of volumes served by storage nodes of a storage cluster from an old data protection scheme (DPS) to a new DPS in a non-disruptive manner. Slice services of the storage nodes forward the data blocks associated with write requests to the block services for storage on storage devices of the nodes. Mapping of volume logical block addresses to block identifiers are contained in slice files, wherein there is a single slice file for each volume. To transition a volume between the old and new DPSs, the slice service tags the data blocks with the new DPS when forwarding new write requests to the block services. In accordance with a background transitioning process, the slice service also retrieves every data block referenced by the to slice file and then resends the data to the block service with the new DPS.

20210248254, Aug 12, 2021

Feb 12, 2020

16/788979

- Sunnyvale CA, US
Daniel David McCarthy - Erie CO, US
Christopher Clark Corey - Boulder CO, US
Sneheet Kumar Mishra - Lafayette CO, US

G06F 21/62
G06F 16/27
H04L 9/32

A bin syncing technique ensures continuous data protection, such as replication and erasure coding, for content driven distribution of data served by storage nodes of a cluster in the event of failure to one or more block services configured to process the data. The cluster maintains information about the block services assigned to host a bin with a copy of the data in a bin assignment table associated with a state. The copies of the data are named, e.g., replica 0 (R0), replica 1 (R1) or replica 2 (R2). In response to failure of one or more block services assigned to host a bin with a replica of the data, an alternate or replacement block service may access the assignments maintained in the bin assignment table, which specify names of the replicas associated with the state.