# US 2012/0259820 A1 · Method and system for restarting file lock services at an adoptive node 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/0259820 A1
- Document ID: US20120259820A1
- Status: Published application
- Kind: A1
- Application number: 13/083,465
- Filed: 2011-04-08
- Published: 2012-10-11
- Earliest claimed: 2011-04-08
- Assignees: Symantec Corporation
- Inventors: KEDAR PATWARDHAN
- Web page: https://patentgrep.com/patent/US20120259820A1

## CPC

- G06F 11/203: {using migration}
- G06F 11/2038: {with a single idle spare processing component}
- G06F 11/2043: {where the redundant components share a common memory address space}
- 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 2201/825: the problem or solution involving locking
- 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 fail over from one node of the cluster to an adoptive node of the cluster. File lock services are then stopped at the adoptive node. File lock services are subsequently restarted at the adoptive node, wherein the restart causes the adoptive node to commence a grace period for other network file system clients to connect to the adoptive node and reclaim file locks. After restarting file lock services, a cluster file system is updated on the adoptive node with process identifiers, and file lock services are resumed at the adoptive node. The cluster file system can be simultaneously exposing the file lock services to other clients as well, like CIFS, etc.

## 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 fail over from one node of the cluster to an adoptive node of the cluster;
stopping file lock services at the adoptive node;
restarting file lock services at the adoptive node, wherein the restart causes the adoptive node to commence a grace period for other network file system clients to connect to the adoptive node and reclaim file locks;
after restarting file lock services, updating a cluster file system on the adoptive node with process identifiers;
selectively resuming network file system file lock recovery requests on the adoptive node during the grace period; and
resuming normal file lock services at the adoptive node after NFS file lock recovery has completed.

### Claim 2 (depends on 1)

The method of claim 1, wherein the grace period for other network file system clients to connect to the adoptive node and reclaim file locks, and wherein the file locks were previously held by the network file system clients.

### Claim 3 (depends on 1)

The method of claim 1 wherein the file lock services are controlled by a file lock recovery agent or the NFS server itself

### 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 and the cluster file system entertain file lock requests from process identifiers of the file lock services which were previously registered with a cluster file system on the adoptive node.

### Claim 6 (depends on 3)

The method of claim 3, wherein, the file lock recovery agent and the cluster file system is configured to entertain file lock requests originating only from the process identifiers or NFS server lock reclaim requests, on the adoptive node, wherein during the grace period, no new file lock requests are processed from network file system clients or from any other source within the cluster.

### Claim 7 (depends on 6)

The method of claim 6, wherein file lock requests already held by the network file system clients are processed during the grace period, and wherein after the grace period expires and NFS file lock recovery is deemed to be complete, file lock services are fully resumed at the adoptive node.

### 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 fail over from one node of the cluster to an adoptive node of the cluster;
stopping file lock services at the adoptive node;
restarting file lock services at the adoptive node, wherein the restart causes the adoptive node to commence a grace period for other network file system clients to connect to the adoptive node and reclaim file locks;
after restarting file lock services, updating a cluster file system on the adoptive node with process identifiers;
selectively resuming network file system file lock recovery requests on the adoptive node during the grace period; and
resuming normal file lock services at the adoptive node after NFS file lock recovery has completed.

### Claim 9 (depends on 8)

The computer readable storage medium of claim 8, wherein the grace period for other network file system clients to connect to the adoptive node and reclaim file locks, and wherein the file locks were previously held by the network file system clients.

### 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 of the network file system.

### 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 and the cluster file system entertains file lock requests from process identifiers of the file lock services which were previously registered with a cluster file system on the adoptive node.

### Claim 13 (depends on 10)

The computer readable storage medium of claim 10, wherein, the file lock recovery agent and cluster file system is configured to entertain file lock requests originating only from the process identifiers or network file system server lock reclaim requests, wherein during the grace period, no new file lock requests are processed from network file system clients.

### Claim 14 (depends on 13)

The computer readable storage medium of claim 13, wherein file lock requests already held by the network file system clients are processed during the grace period, and wherein after the grace period expires and network file system file lock recovery is deemed to be complete, file lock services are resumed normally at the adoptive node.

### 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;
executing a distributed computer system having a plurality of nodes comprising a cluster;
initiating a network file system server fail over from one node of the cluster to an adoptive node of the cluster;
stopping file lock services at the adoptive node;
restarting file lock services at the adoptive node, wherein the restart causes the adoptive node to commence a grace period for other network file system clients to connect to the adoptive node and reclaim file locks;
after restarting file lock services, updating a cluster file system on the adoptive node with process identifiers;
selectively resuming network file system file lock recovery requests on the adoptive node during the grace period; and
resuming normal file lock services at the adoptive node after NFS file lock recovery has completed.

### Claim 16 (depends on 15)

The server computer system of claim 15, wherein the grace period for other network file system clients to connect to the adoptive node and reclaim file locks, and wherein the file locks were previously held by the network file system clients.

### 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 or the network file systemr itself.

### Claim 18 (depends on 15)

The server computer system of claim 15, 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 entertains file lock requests from process identifiers of the file lock services which were previously registered with a cluster file system on the adoptive node.

### Claim 19 (depends on 15)

The server computer system of claim 15, wherein, the file lock recovery agent is configured to entertain file lock requests originating only from the process identifiers or network file system server lock reclaim requests, wherein during the grace period, no new file lock requests are processed from network file system clients.

### Claim 20 (depends on 19)

The server computer system of claim 19, wherein file lock requests already held by the network file system clients are processed during the grace period, and wherein after the grace period expires and network file system file lock recovery is deemed to be complete, file lock services are resumed normally at the adoptive node.
