# US 2012/0259819 A1 · Method and system for performing a clean file lock recovery during a network filesystem server migration or failover

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

- Number: US 2012/0259819 A1
- Document ID: US20120259819A1
- Status: Published application
- Kind: A1
- Application number: 13/083,013
- Filed: 2011-04-08
- Published: 2012-10-11
- Earliest claimed: 2011-04-08
- Assignees: Symantec Corporation
- Inventors: Kedar Patwardhan; Rachit Chadha; Sushil Patil
- Web page: https://patentgrep.com/patent/US20120259819A1

## CPC

- G06F 16/119: {Details of migration of file systems (migration mechanisms in storage systems G06F3/0647)}
- G06F 16/1774: {Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files}
- G06F 16/183: {Provision of network file services by network file servers, e.g. by using NFS, CIFS (network file access protocols H04L67/1097)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for file lock recovery in a distributed computer system. The method includes executing a distributed computer system having a plurality of nodes comprising a cluster, and initiating a network file system server migration from one node of the cluster to a different node of the cluster. A migration count is incremented, wherein the migration count is stored at each of the nodes comprising the cluster. File lock services are paused at each of the nodes comprising the cluster. The network file system server migration is completed at the different node of the cluster. The migration count is then decremented in response to the completion. File lock services are then resumed at each of the nodes comprising cluster.

## Claims

### Claim 1

A method for file lock recovery in a distributed computer system, comprising:
executing a distributed computer system having a plurality of nodes comprising a cluster;
initiating a network file system server migration from one node of the cluster to a different node of the cluster;
incrementing a migration count, wherein the migration count is stored at each of the nodes comprising the cluster;
pausing file lock services at each of the nodes comprising the cluster;
completing the network file system server migration at the different node of the cluster;
decrementing the migration count in response to the completion; and
resuming file lock services at each of the nodes comprising cluster.

### Claim 2 (depends on 1)

The method of claim 1, wherein a cluster node status is posted to each of the nodes comprising the cluster upon the resumption of file lock services.

### Claim 3 (depends on 1)

The method of claim 1 wherein the file lock services are controlled by a file lock recovery agent.

### Claim 4 (depends on 3)

The method of claim 3, wherein the file lock recovery agent is instantiated on each of the plurality of nodes comprising the cluster.

### Claim 5 (depends on 3)

The method of claim 3, wherein the file lock recovery agent includes the migration count for tracking the number of migrations that occur within the cluster.

### Claim 6 (depends on 1)

The method of claim 1, wherein the migration count is stored within a cluster file system at each of the plurality of nodes comprising the cluster.

### Claim 7 (depends on 1)

The method of claim 1, wherein a generation count is maintained at each of the plurality nodes comprising cluster, and wherein the generation count is incremented in response to a reconfiguration of the cluster in order to ensure each node of the cluster is updated to the current generation configuration.

### Claim 8

A computer readable storage medium having stored thereon, computer executable instructions that, if executed by a computer system cause the computer system to perform a method comprising:
executing a distributed computer system having a plurality of nodes comprising a cluster;
initiating a network file system server migration from one node of the cluster to a different node of the cluster;
incrementing a migration count, wherein the migration count is stored at each of the nodes comprising the cluster;
pausing file lock services at each of the nodes comprising the cluster;
completing the network file system server migration at the different node of the cluster;
decrementing the migration count in response to the completion; and
resuming file lock services at each of the nodes comprising cluster.

### Claim 9 (depends on 8)

The computer readable storage medium of claim 8, wherein a cluster node status is posted to each of the nodes comprising the cluster upon the resumption of file lock services.

### Claim 10 (depends on 8)

The computer readable storage medium of claim 8 wherein the file lock services are controlled by a file lock recovery agent.

### Claim 11 (depends on 10)

The computer readable storage medium of claim 10, wherein the file lock recovery agent is instantiated on each of the plurality of nodes comprising the cluster.

### Claim 12 (depends on 10)

The computer readable storage medium of claim 10, wherein the file lock recovery agent includes the migration count for tracking the number of migrations that occur within the cluster.

### Claim 13 (depends on 8)

The computer readable storage medium of claim 8, wherein the migration count is stored within a cluster file system at each of the plurality of nodes comprising the cluster.

### Claim 14 (depends on 8)

The computer readable storage medium of claim 8, wherein a generation count is maintained at each of the plurality nodes comprising cluster, and wherein the generation count is incremented in response to a reconfiguration of the cluster in order to ensure each node of the cluster is updated to the current generation configuration.

### Claim 15

A server computer system, comprising:
a computer system having a processor coupled to a computer readable storage media and executing computer readable code which causes the computer system to implement a file lock recovery agent that functions by:
incrementing a migration count, wherein the migration count is stored at each of the nodes comprising the cluster, wherein the incrementing is in response to a network file system server migration from one node of a cluster to a different node of the cluster, wherein the cluster comprises a plurality of nodes;
pausing file lock services at each of the nodes comprising the cluster;
completing the network file system server migration at the different node of the cluster;
decrementing the migration count in response to the completion; and
resuming file lock services at each of the nodes comprising cluster.

### Claim 16 (depends on 15)

The server computer system of claim 15, wherein a cluster node status is posted to each of the nodes comprising the cluster upon the resumption of file lock services.

### Claim 17 (depends on 15)

The server computer system of claim 15, wherein the file lock services are controlled by a file lock recovery agent, and wherein the file lock recovery agent is instantiated on each of the plurality of nodes comprising the cluster, and wherein the file lock recovery agent includes the migration count for tracking the number of migrations that occur within the cluster.

### Claim 18 (depends on 15)

The server computing system of claim 15, wherein file lock processing is resumed when migrations pending for a particular CFS file system are over.

### Claim 19 (depends on 15)

The server computing system of claim 15, wherein file lock processing is resumed after file lock recovery is complete for a latest known generation count maintained on an adoptive node.

### Claim 20 (depends on 15)

The server computing system of claim 15, wherein a plurality of service migrations and a plurality of service reconfigurations occur at an arbitrary order, and wherein file lock processing is resumed after the service migrations are indicated to be complete and a file lock recovery agent has finished a recovery for a latest known generation count maintained on an adoptive node.
