Granted Patent B2

US 12,461,832 · App. 18/393,187 · Granted Nov 4, 2025

Inventors: Ashok Tellakula (Bangalore, IN); Atul Kumar (Noida, IN); Hemanth Kumar Thummala (San Jose, CA); Manoj Premanand Naik (San Jose, CA); Saji Kumar Vijaya Kumari Rajendran Nair (Cupertino, CA)

Assignee: Nutanix, Inc.

G06F11/2053G06F16/1774G06F2201/85

Abstract

Claims (46)

1 . A system comprising:

a first computing node configured to host:

a first server message block (SMB) process configured to provide access to a file share, the file share configured to receive asynchronous writes;

a failover process;

a persistent volume group coupled to the first computing node, the persistent volume group configured to store durable handle state for the file share; and

a second computing node configured to host a second SMB process;

wherein the failover process is configured to move the persistent volume group to the second computing node in advance of an outage of the first SMB process, and the failover process is further configured to flush the asynchronous writes to disk in advance of the outage; and

wherein the second SMB process is configured to read a durable handle for the file share from the persistent volume group and respond to reconnect requests for the file share.

2 . The system of claim 1 , wherein the file share comprises a non-continuous availability (CA) file share.

3 . The system of claim 1 , wherein the failover process is configured to cause the second SMB process to service access requests for the file share responsive to the outage of the first SMB process.

4 . The system of claim 1 , wherein the second computing node is configured to prioritize reconnect requests for the file share over other requests for the file share.

5 . The system of claim 1 , wherein the persistent volume group is further configured to store lock information for the file share.

6 . The system of claim 5 , wherein the second computing node is further configured to access the lock information from the persistent volume group and provide lock states indicated by the lock information.

7 . The system of claim 6 , wherein the second computing node is configured to provide the lock states prior to responding to requests for the file share.

8 . The system of claim 1 , wherein the second computing node is configured to receive the asynchronous writes flushed to disk, and wherein the second computing node is configured to process the asynchronous writes for the file share prior to responding to requests for access to the file share.

9 . At least one non-transitory computer readable medium encoded with instructions which, when executed, cause a system to perform operations responsive to an indication of a failover event, the operations comprising:

flush asynchronous write operations for a file share to disk at a first computing node;

move a persistent volume group to a second computing node, the persistent volume group storing durable handles for the file share; and

failover an SMB process from the first computing node to the second computing node, wherein the SMB process is configured to provide access to the file share.

10 . The non-transitory computer readable medium of claim 9 , wherein the operations further comprise:

store the durable handles for the file share to the persistent volume group.

11 . The non-transitory computer readable medium of claim 9 , wherein the operations further comprise:

move the persistent volume group to the second computing node, the persistent volume group storing lock state for the file share.

12 . The non-transitory computer readable medium of claim 11 , wherein the operations further comprise:

read and implement the lock state.

13 . The non-transitory computer readable medium of claim 9 , the operations further comprising:

receive the indication of the failover event.

14 . The non-transitory computer readable medium of claim 9 , wherein the operations further comprise:

provide the asynchronous write operations to the second computing node.

15 . The non-transitory computer readable medium of claim 9 , wherein the failover event comprises an upgrade.

16 . At least one non-transitory computer readable medium encoded with instructions which, when executed, cause a system to perform operations responsive to an indication of a failover event, the operations comprising:

receive, at a second computing node, from a first computing node, a persistent volume group, the persistent volume group storing durable handles for a file share;

receive, from the first computing node, asynchronous write operations for the file share;

process the asynchronous write operations for the file share utilizing an SMB process at the second computing node; and

respond to a reconnect request for the file share at the second computing node, including accessing the durable handles for the file share.

17 . The non-transitory computer readable medium of claim 16 , wherein the operations further comprise:

prioritize the reconnect request for the file share over another request for the file share.

18 . The non-transitory computer readable medium of claim 16 , wherein the persistent volume group further is configured to store lock state for the file share.

19 . The non-transitory computer readable medium of claim 18 , wherein the operations further comprise:

restore the lock state from the persistent volume group.

20 . The non-transitory computer readable medium of claim 18 , wherein the operations further comprise:

delete the durable handles after a threshold time.

21 . The non-transitory computer readable medium of claim 18 , wherein the operations further comprise:

receive an indication of a failover event;

wherein the asynchronous write operations and the persistent volume group are responsive to the indication of the failover event.

22 . The non-transitory computer readable medium of claim 21 , wherein the failover event comprises an upgrade of the first computing node.

Assignments (2)

Priority Claims (1)

Continuity (1)

References Cited (400)