# US 2021/0342301 A1 · Filesystem managing metadata operations corresponding to a file in another filesystem

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

- Number: US 2021/0342301 A1
- Document ID: US20210342301A1
- Status: Published application
- Kind: A1
- Application number: 17/249,907
- Filed: 2021-03-18
- Published: 2021-11-04
- Earliest claimed: 2020-04-29
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Venkataraman Kamalaksha; Suparna Bhattacharya; Ashutosh Kumar
- Web page: https://patentgrep.com/patent/US20210342301A1

## CPC

- G06F 16/148: {File search processing}
- G06F 16/164: {File meta data generation}
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 16/188: Virtual file systems
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Examples described herein relate to a computing system, a method and a non-transitory machine-readable medium for handling a request directed to a file in first filesystem having a filesystem instance being a content addressable storage objects. The computing system may also include a general-purpose second filesystem including its backing store within the filesystem instance of the first filesystem. Moreover, the computing system includes a first filesystem server to receive the request for an operation directed to the file in the first filesystem from an application. The first filesystem server may redirect the request to the second filesystem if the operation is a metadata operation; else redirect the request to the first filesystem.

## Claims

### Claim 1

A computing system comprising:
a first filesystem comprising a filesystem instance representing hierarchical arrangement of content addressable objects;
a second filesystem comprising a backing store within the filesystem instance of the first filesystem; and
a first filesystem server communicatively coupled to the first filesystem and the second filesystem, wherein the first filesystem server is to receive a request for an operation directed to a file in the first filesystem from an application, and redirect the request to the second filesystem if the operation is a metadata operation, else redirect the request to the first filesystem.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the filesystem instance comprises one or more files, wherein each of the one or more files is represented as a file object tree in the filesystem instance, and wherein the backing store comprises a file of the one or more files in the filesystem.

### Claim 3 (depends on 1)

The computing system of claim 1, wherein data information corresponding to the file is maintained in a data object arranged in a file object tree in the filesystem instance outside of the backing store, and metadata information corresponding to the file is maintained in a metadata object arranged in a file metadata object tree within the backing store.

### Claim 4 (depends on 3)

The computing system of claim 3, wherein the first filesystem server is to synchronize an identifier of the file object tree with an identifier of the file metadata object tree by generating file handles for the first filesystem and the second filesystems.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein the first filesystem server is to determine whether the operation is the metadata operation based at least on a predetermined list of metadata operations.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein the metadata operation comprises a directory create operation, a file create operation, a file lookup operation, a directory read operation, a file rename operation, or a set attribute operation.

### Claim 7 (depends on 1)

The computing system of claim 1, wherein the first filesystem server is to redirect the request to the first filesystem if the operation is a read operation or a write operation.

### Claim 8 (depends on 1)

The computing system of claim 1, further comprising a filesystem access tool accessible by the first filesystem server to aid in communication with the second filesystem, wherein the first filesystem server redirects the request to the second filesystem via the filesystem access tool.

### Claim 9 (depends on 8)

The computing system of claim 8, wherein the filesystem access tool is a Network Filesystem (NFS) server or a filesystem Application Programming Interface (API) compatible with the second filesystem.

### Claim 10

A method, comprising:
receiving, by a first filesystem server, a request for an operation directed to a file in a first filesystem from an application, wherein the first filesystem comprises a filesystem instance representing hierarchical arrangement of content addressable objects;
determining, by the first filesystem server, whether the operation is a metadata operation;
redirecting, by the first filesystem server, the request to a second filesystem in response to determining that the operation is the metadata operation, wherein the second filesystem comprises a backing store within the filesystem instance of the first filesystem; and
redirecting, by the first filesystem server, the request to the first filesystem in response to determining that the operation is not the metadata operation.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
creating, by the first filesystem server, a filesystem host file within the first filesystem, and
assigning, by the first filesystem server, the filesystem host file to the second filesystem as the backing store.

### Claim 12 (depends on 10)

The method of claim 10, wherein determining whether the operation is the metadata operation comprises comparing, by the first filesystem server, the operation against a predetermined list of metadata operations.

### Claim 13 (depends on 10)

The method of claim 10, wherein redirecting the request to the second filesystem comprises routing the request to the second filesystem via a Network Filesystem (NFS) server or a filesystem Application Programming Interface (API) compatible with the second filesystem.

### Claim 14 (depends on 10)

The method of claim 10, further comprising accessing, upon receipt of the request by the first filesystem, data information corresponding to the file from a data object organized in a file object tree within the filesystem instance outside the backing store.

### Claim 15 (depends on 14)

The method of claim 14, further comprising accessing, upon receipt of the request by the second filesystem, metadata information corresponding to the file from a metadata object organized in a file metadata object tree in the backing store, wherein an identifier of the file metadata objet tree is synchronized with an identifier of the file object tree.

### Claim 16

A non-transitory machine-readable medium storing instructions executable by a processing resource, the instructions comprising:
instructions to receive a request for an operation directed to a file in a first filesystem from an application, wherein the first filesystem comprises a filesystem instance representing hierarchical arrangement of content addressable objects;
instructions to determine whether the operation is a metadata operation;
instructions to redirect the request to a second filesystem in response to determining that the operation is the metadata operation, wherein the second filesystem comprises a backing store within the filesystem instance of the first filesystem; and
instructions to redirect the request to the first filesystem from in response to determining that the operation is not the metadata operation.

### Claim 17 (depends on 16)

The non-transitory machine-readable medium of claim 16, further comprising instructions to:
create a filesystem host file within the first filesystem; and
assign the filesystem host file to the second filesystem as the backing store.

### Claim 18 (depends on 16)

The non-transitory machine-readable medium of claim 16, further comprising instructions to maintain data information corresponding to the file in a data object arranged in a file object tree in the filesystem instance outside the backing store and metadata information corresponding to the file is maintained in a metadata object arranged in a file metadata object tree within the backing store.

### Claim 19 (depends on 18)

The non-transitory machine-readable medium of claim 18, further comprising instructions to synchronize an identifier of the file object tree with an identifier of the file metadata object tree by generating file handles for the first filesystem and the second filesystems.

### Claim 20 (depends on 18)

The non-transitory machine-readable medium of claim 18, further comprising instructions to:
access, upon receipt of the request by the first filesystem, the data information from the file object tree; or
access, upon receipt of the request by the second filesystem, the metadata information from the file metadata object tree.
