Generalized write operations verification method

• US 10,380,069 B2
• Filed: 05/04/2016
• Issued: 08/13/2019
• Est. Priority Date: 05/04/2016
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: Western Digital Technologies Incorporated (Western Digital Corporation)
• Inventors: Dubeyko, Viacheslav, Manzanares, Adam
• Primary Examiner(s): Le, Thu Nguyet T
• Application Number:
  US15/146,685
• Publication Number:
  US 20170322927A1
• Time in Patent Office: 1,196 Days
• Field of Search: 707822
• CPC Class Codes: G06F 11/006 Identification G06F11/2289 takes precedence
• CPC Class Codes: G06F 11/1435 using file system or storage system metadata
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 16/164 File meta data generation
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity

Abstract

A verification architecture described according to embodiments of the present invention validates changes made to metadata and may comprise one or more subsystems and phases. According to some embodiments, the “mkfs” volume creation utility works in cooperation with the device driver to create a file system volume by means of reservation and initialization space for metadata structures inside the device'"'"'s partition that is reserved for the specific file system volume. The storage device uses a verified area legend when checking write requests after the file system volume has been created. The verified area legends may be stored in a dedicated partition or inside the master boot record (MBR) or Globally Unique Identifier (GUID) partition table (GPT) or special memory chip (NAND flash, for example). Write requests that overlap with any extent of reserved metadata area must be verified to prevent metadata corruption.

Claims

1. A method of validating a write request to a storage device to prevent corruption of metadata, wherein the write request comprises a logical block address, a magic signature, and a data type flag, the method comprising:

determining if the logical block address of the write request overlaps an existing extent of a verified area of the storage device;

responsive to determining that the logical block address overlaps an existing extent of a verified area, determining if the write request comprises metadata based on the data type flag indicating metadata;

responsive to determining that the write request comprises metadata, determining if the magic signature matches an expected magic signature of a legend of the verified area;

responsive to determining that the magic signature matches an expected magic signature of a legend of the verified area,

determining if a number of blocks of the write request is valid;

responsive to determining that the number of blocks of the write request is valid, determining if a size of the blocks of the write request is equal to a multiple of a node size of the legend of the verified area; and

responsive to determining that the size of the blocks of the write request is equal to a multiple of a node size of the legend of the verified area, writing the metadata of the write request to the storage device.

2. The method of claim 1, further comprising responsive to one or more of:

determining that the write request does not comprise metadata based on the data type flag, determining that the magic signature does not match the expected magic signature of the legend, determining that the number of blocks of the write request is not valid, or determining that the size of the blocks of the write request is not equal to a multiple of a node size of the legend of the verified area, presenting a notification indicating that the write request is not valid.

3. The method of claim 1, wherein the write request was generated by file system activity and comprises user data, and further comprising:

responsive to determining the logical block address of the write request does not overlap an existing extent of a verified area of the storage device, determining that the write request comprises the user data and not metadata based on the data type flag; and

responsive to determining that the write request comprises the user data, writing the user data to the storage device.

4. The method of claim 1, wherein the magic signature comprises a value that identifies a concrete metadata structure.

5. The method of claim 4, wherein the value of the magic signature is a pre-defined binary value.

6. The method of claim 1, wherein the write request comprises a byte stream.

7. The method of claim 1, wherein the legend is stored in a namespace associated with a file system volume of the storage device.

8. An apparatus for validating a write request to prevent corruption of metadata, comprising:

a storage device; and

a processor communicatively coupled to the storage device that is configured to;

analyze the write request, wherein the write request comprises a logical block address, a magic signature, and a data type flag;

determine if the logical block address of the write request overlaps an existing extent of a verified area of the storage device;

responsive to determining that the logical block address overlaps an existing extent of a verified area, determine if the write request comprises metadata based on the data type flag indicating metadata;

responsive to determining that the write request comprises metadata, determine if the magic signature matches an expected magic signature of a legend of the verified area;

responsive to determining that the magic signature matches an expected magic signature of a legend of the verified area,

determine if a number of blocks of the write request is valid;

responsive to determining that the number of blocks of the write request is valid, determining if a size of the blocks of the write request is equal to a multiple of a node size of the legend of the verified area; and

responsive to determining that the size of the blocks of the write request is equal to a multiple of a node size of the legend of the verified area, write the metadata of the write request to the storage device.

9. The apparatus of claim 8, wherein the processor is further configured to responsive to one or more of:

determining that the write request does not comprise metadata based on the data type flag, determining that the magic signature does not match the expected magic signature of the legend, determining that the number of blocks of the write request is not valid, or determining that the size of the blocks of the write request is not equal to a multiple of a node size of the legend of the verified area, present a notification indicating that the write request is not valid.

10. The apparatus of claim 8, wherein the write request was generated by file system activity and comprises user data, and wherein the processor is further configured to:

responsive to determining the logical block address of the write request does not overlap an existing extent of a verified area of the storage device, determine that the write request comprises the user data and not metadata based on the data type flag; and

responsive to determining that the write request comprises user data, writing the user data to the storage device.

11. The apparatus of claim 8, wherein the magic signature comprises a value that identifies a concrete metadata structure.

12. The apparatus of claim 11, wherein the value of the magic signature is a pre-defined binary value.

13. The apparatus of claim 8, wherein the write request comprises a byte stream.

14. The apparatus of claim 8, wherein the legend is stored in a namespace associated with a file system volume of the storage device.

15. A computer program product tangibly embodied in a computer-readable storage medium and comprising instructions that, when executed by a processor, perform a method for validating a write request to a storage device to prevent corruption of metadata, wherein the write request comprises a logical block address, a magic signature, and a data type flag, and wherein the method comprises:

determining if the logical block address of the write request overlaps an existing extent of a verified area of the storage device;

responsive to determining that the logical block address overlaps an existing extent of a verified area, determining if the write request comprises metadata based on the data type flag indicating metadata;

responsive to determining that the write request comprises metadata, determining if the magic signature matches an expected magic signature of a legend of the verified area;

responsive to determining that the magic signature matches an expected magic signature of a legend of the verified area,

determining if a number of blocks of the write request is valid;

responsive to determining that the number of blocks of the write request is valid, determining if a size of the blocks of the write request is equal to a multiple of a node size of the legend of the verified area; and

responsive to determining that the size of the blocks of the write request is equal to a multiple of a node size of the legend of the verified area, writing the metadata of the write request to the storage device.

16. The computer program product of claim 15, the method further comprising responsive to one or more of:

determining that the write request does not comprise metadata based on the data type flag, determining that the magic signature does not match the expected magic signature of the legend, determining that the number of blocks of the write request is not valid, or determining that the size of the blocks of the write request is not equal to a multiple of a node size of the legend of the verified area, presenting a notification indicating that the write request is not valid.

17. The computer program product of claim 15, wherein the write request was generated by file system activity and comprises user data, and wherein the method further comprises:

responsive to determining the logical block address of the write request does not overlap an existing extent of a verified area of the storage device, determining that the write request comprises the user data and not metadata based on the data type flag; and

responsive to determining that the write request comprises the user data, writing the user data from being written to the storage device, writing the user data to the storage device.

18. The computer program product of claim 15, wherein the magic signature comprises a value that identifies a concrete metadata structure.

19. The computer program product of claim 18, wherein the value is a pre-defined binary value, the write request comprises a byte stream, and the legend is stored in a namespace associated with a file system volume of the storage device.