Storage management method, device and computer-readable medium

1. A method of storage management, comprising:

receiving a request for creating a storage space, the request at least including a storage capacity and a RAID configuration of the storage space, the RAID configuration at least indicating a RAID type;

allocating an extent based on the storage capacity;

creating a RAID group for the extent based on the RAID type; and

storing metadata of the RAID group into the extent, the metadata indicating a configuration of the RAID group and a configuration of a user data region in the extent;

wherein the metadata includes:

first metadata for recording configuration information of a RAID unit in the RAID group, the RAID group including a plurality of RAID units, and

second metadata for recording an extent to be rebuilt amongst extents mapped by the RAID unit; and

wherein storing metadata of the RAID group into the extent comprises:

storing the first metadata in a mirror stripe created for the extent, the mirror stripe being stored at a start of the extent, and

storing the second metadata at an end of the extent, a region between the start and the end of the extent being the user data region.

2. The method of claim 1 , wherein the received request for creating a storage space is a request for expanding an existed storage space.

3. The method of claim 1 , further comprising:

maintaining a dynamic mapping, the dynamic mapping including at least one of the following:

a first multi-tuple including identification information of the storage space, a storage capacity of the storage space, and a RAID configuration and reference information of the storage space, the reference information indicating a logic block address (LBA) corresponding to the storage space,

a second multi-tuple including a mapping relationship between a logic unit number (LUN) of the storage space and an address of the RAID group, the second multi-tuple including at least one sub-multi-tuple of a same size, and

a third multi-tuple including a mapping relationship between the RAID group of the storage space and the extent.

4. The method of claim 1 , wherein at least a portion of the RAID group is formed of magnetic disk drive storage.

5. A method of storage management, comprising:

receiving a request for creating a storage space, the request at least including a storage capacity and a RAID configuration of the storage space, the RAID configuration at least indicating a RAID type;

allocating an extent based on the storage capacity;

creating a RAID group for the extent based on the RAID type;

storing metadata of the RAID group into the extent, the metadata indicating a configuration of the RAID group and a configuration of a user data region in the extent; and

maintaining a dynamic mapping, the dynamic mapping including at least one of the following:

a first multi-tuple including identification information of the storage space, a storage capacity of the storage space, and a RAID configuration and reference information of the storage space, the reference information indicating a logic block address (LBA) corresponding to the storage space,

a second multi-tuple including a mapping relationship between a logic unit number (LUN) of the storage space and an address of the RAID group, the second multi-tuple including at least one sub-multi-tuple of a same size, and

a third multi-tuple including a mapping relationship between the RAID group of the storage space and the extent.

6. The method of claim 5 , further comprising:

detecting whether an idle storage unit is present in the second multi-tuple for storing the address of the RAID group;

in response to absence of the idle storage unit in the second multi-tuple, allocating a sub-multi-tuple including a plurality of idle storage units; and

arranging the sub-multi-tuple at an end of the second multi-tuple.

7. The method of claim 5 , further comprising:

receiving a reducing request for a storage space to be reduced, the reducing request including indication information for indicating a predetermined RAID group to be reduced;

erasing metadata on an extent corresponding to the predetermined RAID group according to the indication information; and

distributing to an extent pool the extent having the metadata erased, the extent pool including a plurality of extents.

8. The method of claim 7 , further comprising:

marking the third multi-tuple corresponding to the predetermined RAID group in the dynamic mapping as invalid so as to invalid the predetermined RAID group.

9. The method of claim 7 , further comprising:

marking a predetermined storage unit that was used to store the address of the predetermined RAID group in the second multi-tuple of the dynamic mapping, as idle.

10. The method of claim 9 , further comprising:

in response to all storage units in a predetermined sub-multi-tuple where the predetermined storage unit locates are all marked as idle, releasing a corresponding relationship of the predetermined sub-multi-tuple and the second multi-tuple so that a storage space in a memory occupied by the predetermined sub-multi-tuple can be used to store other data.

11. A device, comprising:

at least one processing unit; and

at least one memory coupled to the at least one processing unit and storing instructions executable by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the device to perform acts including:

receiving a request for creating a storage space, the request at least including a storage capacity and a RAID configuration of the storage space, the RAID configuration at least indicating a RAID type,

allocating an extent based on the storage capacity,

creating a RAID group for the extent based on the RAID type, and

storing metadata of the RAID group into the extent, the metadata indicating a configuration of the RAID group and a configuration of a user data region in the extent;

wherein the metadata includes:

first metadata for recording configuration information of a RAID unit in the RAID group, the RAID group including a plurality of RAID units, and

second metadata for recording an extent to be rebuilt amongst extents mapped by the RAID unit; and

wherein storing metadata of the RAID group in the extent comprises:

storing the first metadata in a mirror stripe created for the extent, the mirror stripe being stored at a start of the extent, and

storing the second metadata at an end of the extent, a region between the start and the end of the extent being the user data region.

12. The device of claim 11 , wherein the received request for creating a storage space is a request for expanding an existed storage space.

13. The device of claim 11 , wherein the acts further include:

maintaining a dynamic mapping, the dynamic mapping including at least one of the following:

a first multi-tuple including identification information of the storage space, a storage capacity of the storage space, and a RAID configuration and reference information of the storage space, the reference information indicating a logic block address (LBA) corresponding to the storage space,

a second multi-tuple including a mapping relationship between a logic unit number (LUN) of the storage space and an address of the RAID group, the second multi-tuple including at least one sub-multi-tuple of a same size, and

a third multi-tuple including a mapping relationship between the RAID group of the storage space and the extent.

14. The device of claim 11 , wherein at least a portion of the RAID group is formed of magnetic disk drive storage.

15. A device, comprising:

at least one processing unit; and

at least one memory coupled to the at least one processing unit and storing instructions executable by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the device to perform acts including:

receiving a request for creating a storage space, the request at least including a storage capacity and a RAID configuration of the storage space, the RAID configuration at least indicating a RAID type,

allocating an extent based on the storage capacity,

creating a RAID group for the extent based on the RAID type,

storing metadata of the RAID group into the extent, the metadata indicating a configuration of the RAID group and a configuration of a user data region in the extent, and

maintaining a dynamic mapping, the dynamic mapping including at least one of the following:

a first multi-tuple including identification information of the storage space, a storage capacity of the storage space, and a RAID configuration and reference information of the storage space, the reference information indicating a logic block address (LBA) corresponding to the storage space,

a second multi-tuple including a mapping relationship between a logic unit number (LUN) of the storage space and an address of the RAID group, the second multi-tuple including at least one sub-multi-tuple of a same size, and

a third multi-tuple including a mapping relationship between the RAID group of the storage space and the extent.

16. The device of claim 15 , wherein the acts further include:

detecting whether an idle storage unit is present in the second multi-tuple for storing the address of the RAID group;

in response to absence of the idle storage unit in the second multi-tuple, allocating a sub-multi-tuple including a plurality of idle storage units; and

arranging the sub-multi-tuple at an end of the second multi-tuple.

17. The device of claim 15 , wherein the actions further comprise:

receiving a reducing request for a storage space to be reduced, the reducing request including indication information for indicating a predetermined RAID group to be reduced;

erasing metadata on an extent corresponding to the predetermined RAID group according to the indication information; and

distributing to an extent pool the extent having the metadata erased, the extent pool including a plurality of extent.

18. The device of claim 17 , wherein the acts further include:

marking the third multi-tuple corresponding to the predetermined RAID group in the dynamic mapping as invalid so as to invalid the predetermined RAID group.

19. The device of claim 17 , wherein the acts further include:

marking a predetermined storage unit that was used to store the address of the predetermined RAID group in the second multi-tuple of the dynamic mapping, as idle.

20. The device of claim 19 , wherein the acts further include:

in response to all storage units for a predetermined sub-multi-tuple where the predetermined storage unit locates are all marked as idle, releasing a corresponding relationship of the predetermined sub-multi-tuple and the second multi-tuple so that the storage space in a memory occupied by the predetermined sub-multi-tuple can be used to store other data.