# US 2020/0004723 A1 · Data migration in a distributive file system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0004723 A1
- Document ID: US20200004723A1
- Status: Published application
- Kind: A1
- Application number: 16/273,762
- Filed: 2019-02-12
- Published: 2020-01-02
- Earliest claimed: 2018-06-29
- Assignees: Weka.IO Ltd.
- Applicants: Weka.IO Ltd
- Inventors: Maor Ben Dayan; Omri Palmon; Liran Zvibel; Kanael Arditti
- Web page: https://patentgrep.com/patent/US20200004723A1

## CPC

- G06F 16/119: {Details of migration of file systems (migration mechanisms in storage systems G06F3/0647)}
- G06F 11/1076: {Parity data used in redundant arrays of independent storages, e.g. in RAID systems}
- G06F 16/13: File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06)
- G06F 16/182: Distributed file systems
- G06F 2211/1028: Distributed, i.e. distributed RAID systems with parity
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A plurality of computing devices are communicatively coupled to each other via a network, and each of the plurality of computing devices is operably coupled to one or more of a plurality of storage devices. A plurality of failure resilient address spaces are distributed across the plurality of storage devices such that each of the plurality of failure resilient address spaces spans a plurality of the storage devices. The plurality of computing devices maintains metadata that maps each failure resilient address space to one of the plurality of computing devices. The metadata is grouped into buckets. Each bucket is stored in the backend of a computing device. Data may be migrated from an external file system to the plurality of storage devices using inode stubs to represent directories and files of the external file system. As the contents of the external file system are copied, the inode stubs are replaced with real inodes.

## Claims

### Claim 1

A system comprising:
a plurality of storage devices; and
a computing device comprising a backend, wherein:
the backend comprises a bucket that is operable to generate a first data structure of a first data structure type and a second data structure of a second data structure type,
the first data structure is operable to direct a data access to an external storage that is outside of the plurality of storage devices, and
the second data structure is operable to direct a data access to a failure-protected stripe comprising a plurality of storage blocks in the plurality of storage devices.

### Claim 2 (depends on 1)

The system of claim 1, wherein the storage blocks of the failure-protected stripe are distributed across at least two storage devices of the plurality of storage devices.

### Claim 3 (depends on 1)

The system of claim 1, wherein at least one storage block of the plurality of storage blocks of the failure-protected stripe is reserved for error correction data that is associated with the other storage blocks of the plurality of storage blocks of the failure-protected stripe.

### Claim 4 (depends on 1)

The system of claim 1, wherein the second data structure comprises an inode and one or more extents that point to the plurality of storage blocks of the failure-protected stripe.

### Claim 5 (depends on 1)

The system of claim 1, wherein the first data structure type is used when data is copied from the external storage to the plurality of storage devices.

### Claim 6 (depends on 5)

The system of claim 5, wherein the second data structure is used after data has been copied from the external storage to the plurality of storage devices.

### Claim 7 (depends on 5)

The system of claim 5, wherein the plurality of storage blocks in the plurality of storage devices are determined before data is migrated from the external storage to the plurality of storage devices, and wherein a storage block of the plurality of storage blocks is designated as a sparse file is it is not used for migrated data or associated error correction data.

### Claim 8 (depends on 1)

The system of claim 1, wherein the first data structure comprises a stub inode.

### Claim 9 (depends on 8)

The system of claim 8, wherein the stub inode corresponds to a file in the external storage.

### Claim 10 (depends on 8)

The system of claim 8, wherein the stub inode corresponds to a directory in the external storage.

### Claim 11

A method comprising:
generating, by a bucket in a computing device backend, a first data structure comprises a stub inode;
designating, by the bucket in the computing device backend, a stripe comprising a plurality of storage blocks in a plurality of storage devices;
migrating data from an external storage to one or more storage blocks in the plurality of storage devices, wherein data migration comprises generating and storing error correction data associated with the data from the external storage;
accessing data from the external storage during data migration, via the stub inode in the first data structure; and
accessing data from the stripe after data migration, via a second data structure.

### Claim 12 (depends on 11)

The method of claim 11, wherein the stripe is a failure-protected stripe.

### Claim 13 (depends on 11)

The method of claim 11, wherein the plurality of storage blocks of the stripe are distributed across at least two storage devices of the plurality of storage devices.

### Claim 14 (depends on 11)

The method of claim 11, wherein at least one storage block of the plurality of storage blocks of the stripe is reserved for a block of error correction data that is generated according to the other storage blocks of the plurality of storage blocks of the stripe.

### Claim 15 (depends on 11)

The method of claim 11, wherein the second data structure comprises an inode and one or more extents that point to the plurality of storage blocks of the stripe.

### Claim 16 (depends on 11)

The method of claim 11, wherein a storage block of the plurality of storage blocks is designated as a sparse file is it is not used for migrated data or associated error correction data.

### Claim 17 (depends on 11)

The method of claim 11, wherein the stub inode corresponds to a file in the external storage.

### Claim 18 (depends on 11)

The method of claim 11, wherein the stub inode corresponds to a directory in the external storage.

### Claim 19 (depends on 11)

The method of claim 11, wherein the computing device backend is on a network interface card (NIC).

### Claim 20 (depends on 1)

The system of claim 1, wherein the system comprises a network interface card (NIC).
