Generalized verification scheme for safe metadata modification
System and method of verifying validity of a metadata modification request to prevent improper metadata operations. During initialization of a volume in a storage device and once a metadata area is reserved for a metadata structure, information characterizing the metadata structure and metadata area is stored in the storage device, which may be in the form of an area legend composed of descriptors such as a magic signature, a node size, a clump size of reservation, and extent of the metadata area. Responsive to a request for operating on metadata, relevant information provided in the request is verified against the stored characteristic information. If the verification discovers an inconsistency between the information provided in the request and the stored characteristic information, the request modification is treated as invalid and blocked from operation.
1. A machine-implemented method for a data storage system comprising a storage device and a processor, the machine-implemented method comprising:
receiving, by the processor, a request to create, in a first area of the storage device, a namespace; and
in response to the request:
adding, by the processor, an area legend of the namespace, in response to the namespace not existing in the first area; and
deleting, by the processor, one or more area legends of the namespace, in response to the namespace already existing in the first area,
wherein:
the storage device comprises the first area and a second area different from the first area;
the second area comprises metadata areas comprising a metadata area;
the metadata area is configured to store a metadata comprising information on usage of data blocks;
the first area is configured to store namespaces comprising the namespace having the area legend; and
the area legend is associated with and characterizes the metadata area.
2. The machine-implemented method of claim 1 , wherein the machine-implemented method further comprises deleting, by the processor, all of the one or more area legends of the namespace, in response to the namespace already existing in the first area and a namespace verification process being enabled.
3. The machine-implemented method of claim 1 , wherein the machine-implemented method further comprises, in response to the namespace already existing in the first area and a namespace verification process being enabled:
generating, by the processor, a set of area legends based on a file system volume of the data storage system; and
in response to the generated set of area legends being inconsistent with the one or more area legends, discarding, by the processor, an operation of deleting the one or more area legends of the namespace.
4. The machine-implemented method of claim 1 , further comprising:
deleting, by the processor, the namespace without performing a namespace verification process, in response to the namespace already existing in the first area and the namespace verification process being disabled.
5. The machine-implemented method of claim 1 , further comprising:
in response to the namespace not existing in the first area, determining, by the processor, whether a namespace verification process is to be enabled.
6. A data storage system, comprising:
a storage device comprising:
a first area; and
a second area different from the first area;
a processor; and
a memory storing instructions,
wherein the instructions are executable by the processor to perform:
receiving a request to create, in the first area of the storage device, a namespace; and
in response to the request:
adding an area legend of the namespace, in response to the namespace not existing in the first area; and
deleting one or more area legends of the namespace, in response to the namespace already existing in the first area, and
wherein:
the second area comprises metadata areas comprising a metadata area;
the metadata area is configured to store a metadata comprising information on usage of data blocks;
the first area is configured to store namespaces comprising the namespace having the area legend; and
the area legend is associated with and characterizes the metadata area.
7. The data storage system of claim 6 , wherein the instructions are further executable by the processor to perform deleting all of the one or more area legends of the namespace, in response to the namespace already existing in the first area and a namespace verification process being enabled.
8. The data storage system of claim 6 , wherein the instructions are further executable by the processor to perform, in response to the namespace already existing in the first area and a namespace verification process being enabled:
generating a set of area legends based on a file system volume of the data storage system; and
in response to the generated set of area legends being inconsistent with the one or more area legends, discarding an operation of deleting the one or more area legends of the namespace.
9. The data storage system of claim 6 , wherein in response to the one or more area legends of the namespace being inconsistent with a set of area legends prepared based on information about the second area of the storage device, the instructions are further executable by the processor to perform discarding an operation of deleting the one or more area legends of the namespace.
10. The data storage system of claim 6 , wherein the instructions are further executable by the processor to perform:
deleting the namespace without performing a namespace verification process, in response to the namespace already existing in the first area and the namespace verification process being disabled.
11. The data storage system of claim 6 , wherein the instructions are further executable by the processor to perform:
in response to the namespace not existing in the first area, determining whether a namespace verification process is to be enabled.
12. The data storage system of claim 11 , wherein in response to the namespace not existing in the first area and when the namespace verification process caused to be disabled, the instructions are further executable by the processor to perform causing the area legend of the namespace to be added without enabling the namespace verification process.
13. The data storage system of claim 11 , wherein in response to the namespace not existing in the first area and the namespace verification process caused to be enabled, the instructions are further executable by the processor to perform causing the area legend of the namespace to be added after enabling the namespace verification process.
14. The data storage system of claim 6 , wherein in response to the namespace not existing in the first area and a namespace verification process caused to be disabled, the instructions are further executable by the processor to perform causing the area legend of the namespace to be added.
15. The data storage system of claim 6 , wherein in response to the namespace not existing in the first area, the instructions are further executable by the processor to perform determining whether all of area legends of the namespace are added, regardless of whether a namespace verification process is to be enabled or to be disabled.
16. An apparatus, comprising:
a storage device comprising:
a first area; and
a second area different from the first area;
means for receiving a request to create, in the first area of the storage device, a namespace; and
in response to the request:
means for adding an area legend of the namespace, in response to the namespace not existing in the first area; and
means for deleting one or more area legends of the namespace, in response to the namespace already existing in the first area,
wherein:
the second area comprises metadata areas comprising a metadata area;
the metadata area is configured to store a metadata comprising information on usage of data blocks;
the first area is configured to store namespaces comprising the namespace having the area legend; and
the area legend is associated with and characterizes the metadata area.
17. The apparatus of claim 16 , further comprising means for deleting all of the one or more area legends of the namespace, in response to the namespace already existing in the first area and a namespace verification process being enabled.
18. The apparatus of claim 16 , wherein the apparatus further comprises:
means for generating a set of area legends based on a file system volume of the apparatus, in response to the namespace already existing in the first area and a namespace verification process being enabled; and
means for discarding an operation of deleting the one or more area legends of the namespace, in response to the namespace already existing in the first area, the namespace verification process being enabled, and the generated set of area legends being inconsistent with the one or more area legends.
19. The apparatus of claim 16 , further comprising:
means for deleting the namespace without performing a namespace verification process, in response to the namespace already existing in the first area and the namespace verification process being disabled.
20. The apparatus of claim 16 , further comprising:
means for determining whether a namespace verification process is to be enabled, in response to the namespace not existing in the first area.