# US 2021/0081114 A1 · Persistent hole reservation

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

- Number: US 2021/0081114 A1
- Document ID: US20210081114A1
- Status: Published application
- Kind: A1
- Application number: 17/106,240
- Filed: 2020-11-30
- Published: 2021-03-18
- Earliest claimed: 2019-03-19
- Assignees: NetApp, Inc.
- Applicants: NetApp Inc.
- Inventors: Krishna Murthy Chandraiah setty Narasingarayanapeta; Rakesh Bhargava M.R.
- Web page: https://patentgrep.com/patent/US20210081114A1

## CPC

- G06F 3/0611: {in relation to response time}
- G06F 3/065: {Replication mechanisms}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques are provided for persistent hole reservation. For example, hole reservation flags of operations targeting a first storage object of a first node are replicated into replication operations targeting a second storage object of a second node during a transition operation to transition the first storage object and the second storage object from an asynchronous replication state to a synchronous replication state. In another example, the second storage object is grown to a size of a replication punch hole operation that failed due to targeting a file block number greater than an end of size of the second storage object.

## Claims

### Claim 1

A method comprising:
performing a transition operation to transition a first storage object and a second storage object from an asynchronous replication state to a synchronous replication state;
synchronizing the first storage object and the second storage object; and
replicating a punch hole operation targeting the first storage object as a replication punch hole operation targeting the second storage object.

### Claim 2 (depends on 1)

The method of claim 1, wherein the replication punch hole operation targets a file block number of the second storage object.

### Claim 3 (depends on 2)

The method of claim 2, comprising:
determining that the replication punch hole operation failed due to targeting the file block number of the second storage object that is greater than an end of size of the second storage object.

### Claim 4 (depends on 3)

The method of claim 3, comprising:
transmitting a write operation to the file block number for the second storage object as specified by the replication punch hole operation to increase a size of the second storage object.

### Claim 5 (depends on 4)

The method of claim 4, comprising:
re-issuing the replication punch hole operation to the second storage object based upon the write operation completing.

### Claim 6 (depends on 1)

The method of claim 1, comprising:
modifying the punch hole operation to set a hole reservation flag on an inode associated with the first storage object.

### Claim 7 (depends on 1)

The method of claim 1, comprising:
executing the punch hole operation upon a unused data block within the first storage object to free the unused data block for being available to subsequently store other data.

### Claim 8 (depends on 1)

The method of claim 1, comprising:
executing the punch hole operation upon a unused data block within the first storage object to return the unused data block to a storage array for subsequently storing other data.

### Claim 9 (depends on 1)

The method of claim 1, comprising:
executing the replicated punch hole operation upon a unused data block within the second storage object to free the unused data block for being available to subsequently store other data.

### Claim 10 (depends on 1)

The method of claim 1, comprising:
executing the replicated punch hole operation upon a unused data block within the second storage object to return the unused data block to a storage array for subsequently storing other data.

### Claim 11 (depends on 1)

The method of claim 1, comprising:
executing the replicated punch hole operation upon a unused data block within the second storage object.

### Claim 12

A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to:
perform a transition operation to transition a first storage object and a second storage object from an asynchronous replication state to a synchronous replication state;
synchronize the first storage object and the second storage object; and
replicate a punch hole operation targeting the first storage object as a replication punch hole operation targeting the second storage object.

### Claim 13 (depends on 12)

The non-transitory machine readable medium of claim 12, wherein the replication punch hole operation targets a file block number of the second storage object.

### Claim 14 (depends on 13)

The non-transitory machine readable medium of claim 13, wherein the instructions cause the machine to:
determine that the replication punch hole operation failed due to targeting the file block number of the second storage object that is greater than an end of size of the second storage object.

### Claim 15 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein the instructions cause the machine to:
transmit a write operation to the file block number for the second storage object as specified by the replication punch hole operation to increase a size of the second storage object.

### Claim 16 (depends on 15)

The non-transitory machine readable medium of claim 15, wherein the instructions cause the machine to:
re-issue the replication punch hole operation to the second storage object based upon the write operation completing.

### Claim 17

A computing device comprising:
a memory comprising machine executable code; and
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
perform a transition operation to transition a first storage object and a second storage object from an asynchronous replication state to a synchronous replication state;
synchronize the first storage object and the second storage object; and
replicate a punch hole operation targeting the first storage object as a replication punch hole operation targeting the second storage object.

### Claim 18 (depends on 17)

The computing device of claim 17, wherein the replication punch hole operation targets a file block number of the second storage object.

### Claim 19 (depends on 18)

The computing device of claim 18, wherein the machine executable code causes the machine to:
determine that the replication punch hole operation failed due to targeting the file block number of the second storage object that is greater than an end of size of the second storage object.

### Claim 20 (depends on 19)

The computing device of claim 19, wherein the machine executable code causes the machine to:
transmit a write operation to the file block number for the second storage object as specified by the replication punch hole operation to increase a size of the second storage object.
