Granted Patent B2

US 12,748,730 · App. 19/048,348 · Granted Sep 29, 2026

Inventors: Thomas Gregory Rothschilds (Issaquah, WA); Aaron James Passey (San Rafael, CA); Edward Carpenter (Seattle, WA)

Assignee: Qumulo, Inc.

G06F16/1774G06F16/172G06F16/182

Abstract

Claims (75)

1 . A method for managing data in a distributed file system over a network using one or more processors to execute instructions that are configured to cause performance of actions, comprising:

sharing one or more portions of a hub file system that includes one or more nodes with one or more spoke file systems that includes one or more other nodes, wherein the hub file system shares organization, access and storage of a plurality of file system items with the one or more spoke file systems; and

employing a first request from a client for access to one or more file system items of the plurality of shared file system items to perform further actions, including:

obtaining one or more log entries from a portion of the one or more spoke file systems that include cache data, wherein the one or more log entries are associated with one or more commands that were executed in the portion of the one or more spoke file systems, and wherein each log entry is associated with a sequence of execution for the one or more commands;

executing the one or more commands in the sequence again in the hub file system for each logical timestamp of the one or more log entries to update the one or more file system items in the hub file system; and

granting a lock on the one or more file system items in the hub file system that enables the client of the one or more spoke file systems to access the one or more updated file system items from the portion of one or more spoke file systems; and

employing a second request from a client for access to the one or more file system items of the plurality of shared file system items to perform further actions, including:

updating the one or more file system items based on one or more invalidation log entries generated by execution of one or more commands associated with the first request; and

communicating the one or more invalidation log entries to the portion of the one or more spoke file systems that include cached data, wherein the one or more invalidation log entries are used to invalidate the cached data.

2 . The method of claim 1 , further comprising:

concurrently storing a plurality of file system log entries into a plurality of shards that are distributed in the hub file system and the one or more spoke file systems based on one or more of a rule, a hash, or a local requirement.

3 . The method of claim 1 , further comprising:

employing initiation of a snapshot by the hub file system to flush each log entry from one or more shards distributed in one or more spoke file systems, which correspond to the snapshot, to the hub file system prior to generation of the snapshot.

4 . The method of claim 1 , further comprising:

employing a third request from the client of the hub file system to perform further actions, including:

determining another portion of the one or more spoke file systems that includes cached data associated with one or more other file system items; and

updating the one or more other file system items in the hub file system based on an execution of one or more commands associated with the third request from the client.

5 . The method of claim 1 , further comprising:

employing a fourth request from the client of the hub file system to perform further actions, including:

generating one or more invalidation log entries on the hub file system based on an execution of the one or more commands; and

communicating the one or more invalidation log entries to the one or more spoke file systems, wherein the one or more spoke file systems employ the one or more invalidation log entries to invalidate cached data associated with one or more file system items that correspond to the one or more invalidated log entries.

6 . The method of claim 1 , further comprising:

generating a lock for a local cache of a spoke file system to obtain subsequent access to a fresh copy of stored data that corresponds to one or more invalidation log entries from the hub file system.

7 . The method of claim 1 , further comprising:

employing updates to meta-data associated with the one or more file system items to generate updated meta-data associated with each corresponding log entry.

8 . A network computer for managing data in a distributed file system, comprising:

a memory that stores at least instructions; and

one or more processors that execute instructions that are configured to cause performance of actions, including:

sharing one or more portions of a hub file system that includes one or more nodes with one or more spoke file systems that includes one or more other nodes, wherein the hub file system shares organization, access and storage of a plurality of file system items with the one or more spoke file systems; and

employing a first request from a client for access to one or more file system items of the plurality of shared file system items to perform further actions, including:

obtaining one or more log entries from a portion of the one or more spoke file systems that include cache data, wherein the one or more log entries are associated with one or more commands that were executed in the portion of the one or more spoke file systems, and wherein each log entry is associated with a sequence of execution for the one or more commands;

executing the one or more commands in the sequence again in the hub file system for each logical timestamp of the one or more log entries to update the one or more file system items in the hub file system; and

granting a lock on the one or more file system items in the hub file system that enables the client of the one or more spoke file systems to access the one or more updated file system items from the portion of one or more spoke file systems; and

employing a second request from a client for access to the one or more file system items of the plurality of shared file system items to perform further actions, including:

updating the one or more file system items based on one or more invalidation log entries generated by execution of one or more commands associated with the first request; and

communicating the one or more invalidation log entries to the portion of the one or more spoke file systems that include cached data, wherein the one or more invalidation log entries are used to invalidate the cached data.

9 . The network computer of claim 8 , further comprising:

concurrently storing a plurality of file system log entries into a plurality of shards that are distributed in the hub file system and the one or more spoke file systems based on one or more of a rule, a hash, or a local requirement.

10 . The network computer of claim 8 , further comprising:

employing initiation of a snapshot by the hub file system to flush each log entry from one or more shards distributed in one or more spoke file systems, which correspond to the snapshot, to the hub file system prior to generation of the snapshot.

11 . The network computer of claim 8 , further comprising:

employing a third request from the client of the hub file system to perform further actions, including:

determining another portion of the one or more spoke file systems that includes cached data associated with one or more other file system items; and

updating the one or more other file system items in the hub file system based on an execution of one or more commands associated with the third request from the client.

12 . The network computer of claim 8 , further comprising:

employing a fourth request from the client of the hub file system to perform further actions, including:

generating one or more invalidation log entries on the hub file system based on an execution of the one or more commands; and

communicating the one or more invalidation log entries to the one or more spoke file systems, wherein the one or more spoke file systems employ the one or more invalidation log entries to invalidate cached data associated with one or more file system items that correspond to the one or more invalidated log entries.

13 . The network computer of claim 8 , further comprising:

generating a lock for a local cache of a spoke file system to obtain subsequent access to a fresh copy of stored data that corresponds to one or more invalidation log entries from the hub file system.

14 . The network computer of claim 8 , further comprising:

employing updates to meta-data associated with the one or more file system items to generate updated meta-data associated with each corresponding log entry.

15 . A processor readable non-transitory storage media that includes instructions for managing data in a distributed file system over a network, wherein execution of the instructions by one or more processors on one or more network computers performs actions, comprising:

sharing one or more portions of a hub file system that includes one or more nodes with one or more spoke file systems that includes one or more other nodes, wherein the hub file system shares organization, access and storage of a plurality of file system items with the one or more spoke file systems; and

employing a first request from a client for access to one or more file system items of the plurality of shared file system items to perform further actions, including:

obtaining one or more log entries from a portion of the one or more spoke file systems that include cache data, wherein the one or more log entries are associated with one or more commands that were executed in the portion of the one or more spoke file systems, and wherein each log entry is associated with a sequence of execution for the one or more commands;

executing the one or more commands in the sequence again in the hub file system for each logical timestamp of the one or more log entries to update the one or more file system items in the hub file system; and

granting a lock on the one or more file system items in the hub file system that enables the client of the one or more spoke file systems to access the one or more updated file system items from the portion of one or more spoke file systems; and

employing a second request from a client for access to the one or more file system items of the plurality of shared file system items to perform further actions, including:

updating the one or more file system items based on one or more invalidation log entries generated by execution of one or more commands associated with the first request; and

communicating the one or more invalidation log entries to the portion of the one or more spoke file systems that include cached data, wherein the one or more invalidation log entries are used to invalidate the cached data.

16 . The processor readable non-transitory storage media of claim 15 , further comprising:

concurrently storing a plurality of file system log entries into a plurality of shards that are distributed in the hub file system and the one or more spoke file systems based on one or more of a rule, a hash, or a local requirement.

17 . The processor readable non-transitory storage media of claim 15 , further comprising:

employing initiation of a snapshot by the hub file system to flush each log entry from one or more shards distributed in one or more spoke file systems, which correspond to the snapshot, to the hub file system prior to generation of the snapshot.

18 . The processor readable non-transitory storage media of claim 15 , further comprising:

employing a third request from the client of the hub file system to perform further actions, including:

determining another portion of the one or more spoke file systems that includes cached data associated with one or more other file system items; and

updating the one or more other file system items in the hub file system based on an execution of one or more commands associated with the third request from the client.

19 . The processor readable non-transitory storage media of claim 15 , further comprising:

employing a fourth request from the client of the hub file system to perform further actions, including:

generating one or more invalidation log entries on the hub file system based on an execution of the one or more commands; and

communicating the one or more invalidation log entries to the one or more spoke file systems, wherein the one or more spoke file systems employ the one or more invalidation log entries to invalidate cached data associated with one or more file system items that correspond to the one or more invalidated log entries.

20 . The processor readable non-transitory storage media of claim 15 , further comprising:

generating a lock for a local cache of a spoke file system to obtain subsequent access to a fresh copy of stored data that corresponds to one or more invalidation log entries from the hub file system.

Assignments (1)

Continuity (2)

References Cited (400)