US 2025/0028602 A1Published application

Client data layout retention across server disruption

AssigneeDell Products L.P.

InventorsSoumyadeep Sen, JeanPierre Bono, Sitaram Pawar, Ahsan Rashid

Life of this patent

Estimating the term…

Loading patent…

Abstract

Client data layout retention across server disruption can be performed and managed. In response to a data layout request from a client device (CD), a server can communicate, to CD, metadata, comprising a mapping of a group of blocks, in a data store of the server, to which CD is able to write data to the file, a file offset associated with the file, and a filesystem block number (FSBN) associated with the file offset. CD can write data to the group of blocks. CD can communicate data layout commit request, comprising the metadata relating to data layout, including file offset and FSBN, to the server. If server disruption occurs prior to committing data layout, CD can communicate reclaim request, comprising the metadata, to server, and server can recreate the data layout and commit the data layout to the data store based on the metadata.

Claims20

Dependent claims

A method, comprising:

in response to a request to obtain a data layout associated with a file from a client device, communicating, by a system comprising a processor, extent list information to the client device, wherein the extent list information comprises a mapping of a group of blocks in a data store of a server to which the client device is able to write data associated with the file, a file offset associated with the file, and a filesystem block number associated with the file offset;
and
subsequent to the client device writing the data to the group of blocks in the data store based on the extent list information, and in response to a disruption of service of the server that occurs before committing of the data layout to the data store or before communicating, to the client device, a notification of a successful committing of the data layout to the data store, recreating, by the system, the data layout based on metadata relating to the data layout and received from the client device, wherein the metadata comprises the file offset and the filesystem block number, and wherein the metadata is received from the client device after the disruption is resolved.

A client device, comprising:

a memory that stores computer executable components;
and
a processor that executes computer executable components stored in the memory, wherein the computer executable components comprise:
a write component that writes respective items of data to respective storage locations in a data store of a server based on extent list data relating to a data layout and comprising a mapping of a group of storage locations in the data store of the server, respective file offsets associated with the file, and respective filesystem storage location numbers associated with the respective file offsets;
and
a write manager component that communicates a reclaim request, comprising metadata relating to the data layout, to the server to facilitate recreation of the data layout in response to an interruption of service by the server that potentially disrupted or prevented a commit of the data layout to the data store of the server, wherein the metadata comprises information relating to the data layout, the information comprising the respective file offsets and the respective filesystem storage location numbers.

3 more elements

A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising:

in response to a request to obtain a data layout associated with a file from a device, communicating extent list data to the device, wherein the extent list data comprises a mapping of a group of storage locations in a data store of a server to which the device is able to write data associated with the file, respective file offsets associated with the file, and respective filesystem storage location numbers associated with the respective file offsets;
and
after the device has written the data to the group of storage locations in the data store in accordance with the extent list data, and in response to a disruption of service of the server that occurs before committing of the data layout to the data store or before communicating, to the device, a notification of a successful committing of the data layout to the data store, recreating the data layout based on metadata relating to the data layout and received from the device, wherein the metadata comprises the respective file offsets and the respective filesystem storage location numbers, and wherein the metadata is received from the device after the disruption is resolved.

Dependencies are inferred from the claim text.

Facts

Application: 18/356,845Filed 21 Jul 2023
Published: 23 Jan 2025
Term ends: Not estimatedThe source records don’t support an estimate.

Classification5 codes

G06F 11/1435
At system level: using file system or storage system metadata
G06F 16/164
File or folder operations, e.g. details of user interfaces specifically adapted to file systems: file meta data generation
G06F 16/1727
Details of further file system functions: details of free space management performed by the file system
G06F 16/1734
Details of further file system functions: details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs