Storage space management method and device, electronic equipment, storage medium and product

Abstract

The invention discloses a storage space management method and device, electronic equipment, a storage medium and a product, and the method comprises the steps that a plurality of disks of the same storage cluster are classified according to a preset strategy, a plurality of logic pools are obtained, and one logic pool comprises at least two disks; under the condition that the type of the storage volume to be created is the first type, a first storage volume of the first type is created in a target logic pool in the multiple logic pools, data contained in the first storage volume is stored in multiple disks of the target logic pool in a distributed mode, and data of the storage volumes of the first type in different logic pools are isolated from one another. And the influence range of the fault is limited in a logic pool, so that the condition of fault spreading is avoided, and the reliability and the stability of the distributed storage system are improved.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular, to a method, device, electronic device, computer-readable storage medium, and computer program product for managing storage space. Background Art

[0002] In the era of cloud computing and big data, with the continuous growth of data volume, distributed storage systems have emerged. A distributed storage system provides highly available and efficient data services by dispersing data across multiple nodes and leveraging redundant storage and parallel processing of data.

[0003] However, the reliability and stability of traditional distributed storage systems are insufficient. Summary of the Invention

[0004] The present application provides a method, device, electronic device, computer-readable storage medium, and computer program product for managing storage space, so as to at least solve the problem of insufficient reliability and stability of distributed storage systems in related technologies.

[0005] The present application provides a method for managing storage space, which is applied to a distributed storage system. The distributed storage system includes a storage cluster, and the storage cluster includes multiple disks. The method includes: classifying multiple disks of the same storage cluster according to a preset policy to obtain multiple logical pools, where at least two disks are included in one logical pool; when the type of the storage volume to be created is the first type, creating a first storage volume of the first type in a target logical pool among the multiple logical pools, where the data included in the first storage volume is distributed and stored in multiple disks of the target logical pool, and the data of the first type of storage volumes in different logical pools is isolated from each other.

[0006] The present application further provides a device for managing storage space, including:

[0007] A disk classification module, configured to classify multiple disks of the same storage cluster according to a preset policy to obtain multiple logical pools, where at least two disks are included in one logical pool;

[0008] A storage volume creation module, configured to create a first storage volume of the first type in a target logical pool among the multiple logical pools when the type of the storage volume to be created is the first type, where the data included in the first storage volume is distributed and stored in multiple disks of the target logical pool, and the data of the first type of storage volumes in different logical pools is isolated from each other.

[0009] The present application further provides an electronic device, including: a memory, configured to store a computer program; a processor, configured to implement the steps of any of the above methods for managing storage space when executing the computer program.

[0010] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above storage space management methods are implemented.

[0011] The present application also provides a computer program product, including a computer program. When the computer program is executed by a processor, the steps of any of the above storage space management methods are implemented.

[0012] Through the storage space management method of the present application, multiple disks of the same storage cluster are classified according to a preset policy, and multiple logical pools are obtained by partitioning, realizing fine-grained management of disk resources. By classifying disks to form logical pools, the distributed storage system can more effectively manage and utilize its internal resources, avoiding waste of resources and the emergence of performance bottlenecks. It can classify disks according to user needs, making the characteristics or performance of disks in one logical pool as consistent as possible, reducing performance fluctuations, and improving the stability of the storage system. This classification strategy can ensure that storage volumes with different performance requirements are created on the most suitable disk sets, thereby improving data processing efficiency and the overall performance of the storage system. By storing data distributively on multiple disks in the target logical pool, not only the storage space of the disks is fully utilized, but also through data isolation logic, it is ensured that data in different logical pools will not interfere with each other. The data isolation strategy effectively prevents data aliasing between volumes with different services or performance requirements, enhancing data security and stability. Since the data of the first storage volume is only distributively stored in the target logical pool, even if a failure occurs in the target logical pool, it will only affect the data of the first storage volume, rather than the data in other logical pools, avoiding the spread of failures. The impact range of the failure is limited to one logical pool, greatly reducing the impact of failures on the storage system and improving the reliability of the storage system. Therefore, the technical problems of insufficient reliability and stability of the distributed storage system in the related art can be solved, and the technical effect of improving the reliability and stability of the distributed storage system can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0014] Figure 1 It is a hardware structure block diagram of a server device for a storage space management method according to an embodiment of the present application;

[0015] Figure 2It is a flowchart of a method for managing storage space according to an embodiment of the present application;

[0016] Figure 3 It is a schematic structural diagram of a logical pool according to an embodiment of the present application;

[0017] Figure 4 It is a second flowchart of a method for managing storage space according to an embodiment of the present application;

[0018] Figure 5 It is a second schematic structural diagram of a logical pool according to an embodiment of the present application;

[0019] Figure 6 It is a third flowchart of a method for managing storage space according to an embodiment of the present application;

[0020] Figure 7 It is a fourth flowchart of a method for managing storage space according to an embodiment of the present application;

[0021] Figure 8 It is a fifth flowchart of a method for managing storage space according to an embodiment of the present application;

[0022] Figure 9 It is a sixth flowchart of a method for managing storage space according to an embodiment of the present application;

[0023] Figure 10 It is a seventh flowchart of a method for managing storage space according to an embodiment of the present application;

[0024] Figure 11 It is a third schematic structural diagram of a logical pool according to an embodiment of the present application;

[0025] Figure 12 It is an eighth flowchart of a method for managing storage space according to an embodiment of the present application;

[0026] Figure 13 It is a ninth flowchart of a method for managing storage space according to an embodiment of the present application;

[0027] Figure 14 It is a tenth flowchart of a method for managing storage space according to an embodiment of the present application;

[0028] Figure 15 It is an eleventh flowchart of a method for managing storage space according to an embodiment of the present application;

[0029] Figure 16 It is a twelfth flowchart of a method for managing storage space according to an embodiment of the present application;

[0030] Figure 17It is the fourth schematic diagram of the structure of a logical pool according to an embodiment of the present application;

[0031] Figure 18 It is the fifth schematic diagram of the structure of a logical pool according to an embodiment of the present application;

[0032] Figure 19 It is the thirteenth flowchart of a method for managing storage space according to an embodiment of the present application;

[0033] Figure 20 It is the fourteenth flowchart of a method for managing storage space according to an embodiment of the present application;

[0034] Figure 21 It is the sixth schematic diagram of the structure of a logical pool according to an embodiment of the present application;

[0035] Figure 22 It is the structural block diagram of a device for managing storage space according to an embodiment of the present application. Specific embodiments

[0036] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0037] It should be noted that in the description of the present application, the terms "include", "comprise" or any other variation thereof are intended to cover a non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements but also other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. The terms "first", "second", etc. in the present application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0038] In order to enable those skilled in the art of the present technology to better understand the solution of the present application, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

[0039] Combined with the specific application environment architecture or specific hardware architecture on which the execution of the method for managing storage space depends, the specific application environment architecture or specific hardware architecture is described herein.

[0040] The embodiment of the method for managing storage space provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1It is a hardware structure block diagram of a server device for a method of managing storage space according to an embodiment of the present application. As Figure 1 shown, the server device may include one or more ( Figure 1 only one is shown in the figure) processors 102 (the processors 102 may include, but are not limited to, processing devices such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. Among them, the above-mentioned server device may further include a transmission device 106 for communication functions and an input / output device 108. Those of ordinary skill in the art can understand that Figure 1 the structure shown is only schematic and does not limit the structure of the above-mentioned server device. For example, the server device may further include more or fewer components than Figure 1 shown in the figure, or have a different configuration from Figure 1 shown in the figure.

[0041] The memory 104 can be used to store computer programs. For example, software programs and modules of application software, such as the computer program corresponding to the method of managing storage space in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implements the above-mentioned method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely provided with respect to the processor 102, and these remote memories may be connected to the server device through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0042] The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the server device. In one instance, the transmission device 106 includes a network adapter (abbreviated as NIC), which can be connected to other network devices through a base station and thus can communicate with the Internet. In one instance, the transmission device 106 may be a radio frequency (abbreviated as RF) module, which is used to communicate with the Internet wirelessly.

[0043] As described in the background art, in an existing distributed storage cluster, once a node fails, not only the data access on that node will be affected, but also due to the tight coupling of data distribution, the data stored on other nodes may also need to be redistributed, which will trigger a large number of data migration and reconstruction activities, thus affecting the read and write performance of the entire cluster. In view of the above technical problems, the fault isolation ability of the storage cluster of the distributed storage system is insufficient, that is, when a node fails, it may affect the performance of the entire storage cluster, resulting in insufficient reliability of the distributed storage system. To solve the above problems, improve the reliability of the distributed storage system, and reduce the impact of a single node failure on the entire cluster, the present application proposes a method for managing storage space.

[0044] Embodiments of the present application provide a method for managing storage space, which is applied to the above-mentioned server device. The server device can be a distributed storage system, and the distributed storage system includes a storage cluster. The storage cluster includes multiple disks. In combination with the execution process of the method for managing storage space, the method will be described in detail. As Figure 2 shown, the method includes the following steps S200-210:

[0045] Step S200, classify multiple disks in the same storage cluster according to a preset policy to obtain multiple logical pools.

[0046] Among them, at least two disks are included in one logical pool.

[0047] Specifically, classify the disk resources inside the storage cluster according to a preset policy, thereby forming multiple logical pools. Each logical pool contains multiple disks, and these disks will jointly serve specific types of data storage requirements. This classification can provide a customized storage environment for different storage volumes based on factors such as disk performance, type, or geographical location.

[0048] Exemplarily, the preset policy can be a rule formulated based on disk performance (such as Input / Output Operations Per Second (IOPS), throughput), disk type (Solid State Drive (SSD), Hard Disk Drive (HDD)), redundancy requirements, or other business requirements, and is used to guide the classification of disks. The logical pool is a storage area abstracted above the disk resources, with independent storage policies and redundancy mechanisms, and can be regarded as a logical unit for resource management.

[0049] Step S210, when the type of the storage volume to be created is the first type, create a first storage volume of the first type in the target logical pool among the multiple logical pools.

[0050] Among them, the data contained in the first storage volume is distributed and stored in multiple disks of the target logical pool, and the data of the first type of storage volume in different logical pools is isolated from each other.

[0051] Specifically, when a storage volume of a specific type (such as high performance, high redundancy, or low cost) needs to be created, the system will select a target logical pool from multiple logical pools according to the preset policy and storage volume type to create this volume. The purpose of doing this is to ensure that the data is stored in an environment that conforms to its storage characteristics, improving data access efficiency and reliability. The first storage volume of the first type is a volume designed to be distributed and stored only in one logical pool, and the data of the first type of storage volume in different logical pools is isolated from each other.

[0052] Exemplarily, as Figure 3 shown, a storage cluster may include multiple storage nodes (Node A, Node B, Node C, Node D, Node E). The storage nodes can be physical nodes or logical nodes in the storage cluster. A storage node can be an entity composed of a set of disks, a network, memory, and a central processing unit (CPU). Each storage node includes a set of disks. Classifying the multiple disks can obtain, for example Figure 3 the logical pool 10 and the logical pool 20 shown.

[0053] In this embodiment, multiple disks in the same storage cluster are classified according to a preset policy, and multiple logical pools are obtained, realizing refined management of disk resources. By classifying disks to form logical pools, the distributed storage system can more effectively manage and utilize its internal resources, avoiding waste of resources and the emergence of performance bottlenecks. It can classify disks according to user requirements, making the characteristics or performance of disks in one logical pool as consistent as possible, reducing performance fluctuations, and improving the stability of the storage system. This classification policy can ensure that storage volumes with different performance requirements are created on the most suitable set of disks, thereby improving data processing efficiency and the overall performance of the storage system. By distributing and storing data on multiple disks in the target logical pool, not only is the storage space of the disks fully utilized, but also through data isolation logic, it is ensured that data in different logical pools does not interfere with each other. The data isolation strategy effectively prevents data aliasing between volumes with different services or performance requirements, enhancing data security and stability. Since the data of the first storage volume is only distributed and stored in the target logical pool, even if a failure occurs in the target logical pool, it will only affect the data of the first storage volume, rather than the data in other logical pools, avoiding the spread of failures. The scope of influence of the failure is limited to one logical pool, greatly reducing the impact of failures on the storage system and improving the reliability of the storage system. Therefore, the technical problem of insufficient reliability and stability of the distributed storage system in the related art can be solved, and the technical effect of improving the reliability and stability of the distributed storage system can be achieved.

[0054] In one embodiment, as Figure 4 shown, step S200, classify multiple disks in the same storage cluster according to a preset policy to obtain multiple logical pools. It includes: steps S400 - S420:

[0055] Step S400, determine the disk parameters of multiple disks in the same storage cluster respectively.

[0056] Specifically, collect the basic information and performance metrics of all disks in the storage cluster as the basic data for subsequent classification. This includes disk type (SSD or HDD), read and write speed, latency, available capacity, disk array (Redundant Array of Independent Disks, RAID) level, etc.

[0057] Step S410, in response to the business requirements of the target object, match the corresponding disk classification policy for the business requirements.

[0058] Specifically, based on the business requirements of the target object (such as an application, a database, or specific user data), the system will select or automatically generate the most suitable disk classification strategy, ensuring that different business requirements can be mapped to the most suitable disk resources, and improving the pertinence and efficiency of resource allocation.

[0059] Exemplarily, a business requirement analysis engine can be built, and the inputs include the performance requirements of the business (such as Input / Output (I / O) intensive or CPU intensive), the size of the data volume, the redundancy requirements, and the cost budget, etc. Using the results output by the business requirement analysis engine, the disk classification strategy is dynamically generated or selected. For example, for an application that requires high I / O performance, the strategy will tend to select a logical pool rich in SSD resources.

[0060] Step S420, classify the multiple disks according to the disk classification strategy and the respective disk parameters of the multiple disks to obtain multiple logical pools.

[0061] Specifically, after clarifying the classification strategy that matches the disk parameters and business requirements, the system begins to allocate the disks to different logical pools according to the strategy. Each logical pool will focus on serving a certain type of business requirement, realizing the optimal configuration and management of resources.

[0062] Exemplarily, based on the disk parameters and the matched disk classification strategy, the disks can be automatically allocated to the corresponding logical pools. Create the structure of the logical pools, and add the disk Identification (ID) to the corresponding pool list. Define the storage strategy and redundancy mechanism for each logical pool, such as the number of data copies, the Erasure Code (EC) encoding parameters, etc., to ensure that the data distribution and fault tolerance mechanism within the logical pool meet the business requirements.

[0063] Exemplarily, as Figure 5 shown, the storage cluster can include multiple storage nodes (Node A, Node B, Node C), and each storage node includes a set of disks. Classifying the multiple disks can obtain logical pools such as Figure 5 shown, Logical Pool 30, Logical Pool 40, and Logical Pool 50.

[0064] In this embodiment, by accurately collecting disk parameters and intelligently matching business requirements, the system can automatically generate or dynamically adjust disk classification policies, realizing the intelligent and personalized configuration of storage resources, maximizing the satisfaction of business requirements, and improving resource utilization. The design of the classification policy takes into account the performance differences and cost factors of different disk types, enabling high-cost and high-performance disk resources to serve applications with high I / O requirements, while low-cost disk resources are used for cost-sensitive data storage, thus finding the best balance point between performance and cost. The creation of logical pools not only optimizes data distribution but also allows independent redundancy policies to be set for each pool, improving data reliability and security. In the event of a single disk or node failure, data can still be recovered from resources in other pools, reducing the risk of data loss. Through the above steps, the distributed storage system can manage storage resources more intelligently and efficiently, not only improving the performance of data storage and access but also demonstrating significant advantages in cost control, data security, and system management, providing strong support for building highly available and high-performance cloud storage solutions. By matching the corresponding disk classification policy to the business requirements, it can ensure that data is stored on the disks most suitable for its characteristics, thereby improving data processing efficiency and reducing data access latency. This method is particularly applicable to distributed storage systems that need to handle diverse business requirements and can effectively solve problems such as unreasonable resource allocation and low data processing efficiency.

[0065] In one embodiment, as Figure 6 shown, step S420, classify multiple disks according to the disk classification policy and the disk parameters of each of the multiple disks to obtain multiple logical pools. It includes: steps S600 - S630:

[0066] Step S600, determine the read / write modes of each of the multiple disks according to the disk parameters of the multiple disks.

[0067] Specifically, based on disk parameters such as read / write speed, I / O latency, disk type, etc., determine the read / write mode of each disk, that is, I / O-intensive or CPU-intensive, which helps improve the accuracy of subsequent classification.

[0068] Exemplarily, data analysis tools can be used to regularly collect and analyze the read and write operation statistics of disks, such as average I / O latency, number of I / O operations per second (IOPS), and throughput. Based on the statistical results and threshold settings, disks can be marked as I / O intensive (high-speed read / write type) or CPU intensive (low-speed read / write type), or the read / write mode of the disk can be determined by the type of disk (SSD, HDD). For example, SSD disks with faster read / write speeds are classified as the first type of disks to form a high-performance first logical pool; HDD disks with slower read / write speeds are classified as the second type of disks to form a large-capacity second logical pool. This classification method can ensure that data is stored on the disk most suitable for its access mode, thereby improving data read / write efficiency and reducing data access latency.

[0069] Step S610, determine the first type of disks and the second type of disks among the multiple disks according to the respective read / write modes of the multiple disks.

[0070] Among them, the read / write mode of the first type of disks is different from that of the second type of disks, and the read / write speed of the first type of disks is greater than that of the second type of disks.

[0071] Specifically, after clarifying the read / write mode of the disks, the system divides the disks into two major categories. Among them, the read / write speed of the first type of disks is significantly higher than that of the second type of disks. This classification lays the foundation for creating logical pools with different performance characteristics.

[0072] Step S620, select a first preset number of the first type of disks among the multiple disks as the same set to obtain at least one first logical pool. And,

[0073] Step S630, select a second preset number of the first type of disks and a third preset number of the second type of disks among the multiple disks as the same set to obtain at least one second logical pool.

[0074] Specifically, after the disk classification is completed, the system selects a certain number of disks from the first type of disks to create a first logical pool according to the preset quantity parameters, and selects some disks from the first type of disks and the second type of disks respectively to create a second logical pool. Each logical pool will have an independent data distribution and redundancy strategy to meet the needs of different types of services.

[0075] Exemplarily, the system selects a fixed number of disks (the first preset number) from the disks marked as the first type (high-speed read / write type) and forms a high-speed logical pool. This is usually applicable to application scenarios that require frequent read / write and high I / O performance. The system also selects a certain number of disks (the second preset number and the third preset number) from the first type of disks and the second type of disks to form a mixed logical pool, which combines read / write speed and cost-effectiveness. This type of logical pool is suitable for services with relatively balanced read / write operations or cost-sensitive services.

[0076] In this embodiment, by classifying disks according to disk read and write modes and creating logical pools with different performance characteristics, this method significantly improves the resource management efficiency and data service flexibility of the distributed storage system. Specifically, the I / O-intensive first logical pool can provide excellent read and write performance to ensure the smooth operation of high-performance applications; while the hybrid second logical pool provides reasonable read and write speeds while taking into account cost control, and is suitable for processing a large amount of data with medium performance requirements. In this way, the system can not only intelligently schedule storage resources according to business needs and improve data access speed and efficiency, but also enhance data reliability and security and reduce potential data loss risks by reasonably configuring redundancy strategies for different logical pools. At the same time, this mechanism simplifies storage management and allows the system to dynamically adjust resource allocation to cope with changing business and data scales, thereby improving the stability and scalability of the storage cluster and providing efficient, flexible and secure resource management solutions for various distributed storage environments.

[0077] In one embodiment, Figure 7 As shown, step S420, classifying multiple disks according to the disk classification strategy and the disk parameters of the multiple disks, to obtain multiple logical pools. It includes: steps S700-S710:

[0078] Step S700: determining the disk models and disk capacities of the multiple disks according to the disk parameters of the multiple disks.

[0079] Specifically, the specific hardware information of all disks in the storage cluster, namely, disk model and disk capacity, is systematically identified, providing a basis for subsequent disk classification and logical pool creation.

[0080] Step S710 , according to the disk models and disk capacities of the multiple disks, the disks with the same disk model and the same disk capacity among the multiple disks are classified into the same set to obtain multiple logical pools.

[0081] Specifically, the system classifies disks with consistent hardware characteristics into the same logical pool based on the disk model and capacity information, forming a collection of storage resources with hardware homogeneity. This process helps optimize data distribution and redundancy strategies, improve storage efficiency and data access speed, and simplify storage management.

[0082] In this embodiment, through the above two steps, the distributed storage system realizes intelligent disk classification based on hardware characteristics and fine construction of logical pools. First, the accurate classification of disks enables the system to perform resource scheduling according to the actual capabilities of the disks, avoiding performance losses and uneven resource allocation caused by hardware mismatches. Second, the creation of logical pools simplifies the processes of data storage and access. The disk sets with the same hardware characteristics can provide a more consistent storage environment for data, enhancing the storage capacity and data access efficiency of the system and reducing system latency caused by disk performance fluctuations. In addition, the construction of logical pools based on hardware homogeneity also optimizes the implementation of data redundancy strategies, enabling data replication and recovery operations to be carried out under similar hardware conditions, improving the speed and reliability of data recovery, and reducing the risk of data loss. Finally, this classification and construction method greatly simplifies the management complexity of the storage system, facilitates the dynamic adjustment and expansion of the system, and ensures that the system can still operate efficiently and stably in the face of diverse storage requirements. In summary, by implementing the precise classification and logical pool construction strategy based on disk hardware parameters, the distributed storage system not only improves resource utilization efficiency and data service performance but also enhances the reliability, maintainability, and scalability of the system, providing technical support for building an efficient, stable, and flexible cloud storage environment. This fine management method enables the system to more intelligently respond to dynamically changing business needs, ensuring data security and continuous optimization of the system.

[0083] In one embodiment, as Figure 8 shown, step S210, when the type of the storage volume to be created is the first type, create a first storage volume of the first type in the target logical pool among multiple logical pools. It includes: steps S800 - S820:

[0084] Step S800, determine the type of the storage volume to be created according to the creation request of the target object.

[0085] Specifically, when receiving a request to create a storage volume, the primary task of the system is to identify the type of storage volume specified in the request to determine subsequent creation parameters and strategies.

[0086] Exemplarily, parse the creation request to extract information about the storage volume type, such as whether it is a high - performance volume, a low - cost volume, or a volume with specific redundancy requirements, or whether the storage volume is to be stored in only one logical pool or can span multiple logical pools. Based on the parsed type information, call the corresponding storage volume creation strategy to prepare for the creation process.

[0087] Step S810, when it is determined that the type of the storage volume to be created is the first type, determine the target logical pool among multiple logical pools according to the performance requirements of the storage volume carried in the creation request.

[0088] Specifically, the system further analyzes the performance requirements of the storage volume, such as I / O rate, latency level, and redundancy, so as to select the specific logical pool that best suits the storage volume type from multiple logical pools.

[0089] Exemplarily, evaluate the performance metrics in the request, such as read / write speed, data redundancy level, and storage cost budget. Search the logical pool database, compare the hardware characteristics of each logical pool (such as disk type, average I / O performance) with the storage volume performance requirements, and select the logical pool that best matches the requirements as the target logical pool. Ensure that the target logical pool has sufficient remaining capacity and the necessary hardware specifications to meet the requirements for creating a high-performance type-1 storage volume.

[0090] For example, a request is made to create a high-performance storage volume or a large-capacity storage volume. According to the performance requirements in the creation request, the system can automatically select the most suitable logical pool to create the storage volume. For example, if the creation request requires a high-performance storage volume, the system will select disks from the high-performance logical pool to create the storage volume; if the creation request requires a large-capacity storage volume, the system will select disks from the large-capacity logical pool to create the storage volume.

[0091] Step S820: Create a first storage volume of the first type in the target logical pool, and distribute and store the data in the first storage volume across multiple disks in the target logical pool according to a preset data distribution strategy.

[0092] Among them, a data isolation logic is set to isolate the data of the storage volumes of the first type in different logical pools from each other.

[0093] Specifically, after selecting the target logical pool, the next task is to create a storage volume in this logical pool, store the data on the disks in the logical pool through a preset data distribution strategy, and at the same time ensure data isolation of the first storage volumes across logical pools.

[0094] Exemplarily, execute the storage volume creation instruction to generate a new storage volume instance in the target logical pool and mark its type as the first type. Apply a preset data distribution strategy (such as an EC-coding-based redundancy strategy, RAID level, etc.) to evenly distribute the data in the storage volume across the disks in the logical pool to ensure high availability and read / write performance of the data. Implement the data isolation logic. Through the metadata management and access control mechanism, prohibit the first storage volumes in different logical pools from directly accessing each other's data to ensure data security and business independence.

[0095] In this embodiment, first, the precise determination of the storage volume type based on the performance requirements of the target object ensures the reasonable allocation of resources and avoids performance bottlenecks and resource waste caused by type errors. Second, by creating a storage volume within a logical pool that matches the hardware characteristics, the system can maximize the utilization of disk performance and provide users with the expected read / write speed and data access experience. In addition, the application of the data distribution strategy ensures data redundancy and high availability. Even if a single disk fails, data can be quickly restored from other disks within the logical pool, enhancing the fault tolerance of the system. Most importantly, the setting of the data isolation logic significantly improves data security. Data between different logical pools is completely isolated. Even for storage volumes of the same type, illegal data access and potential data leakage risks can be avoided, thus maintaining the overall data privacy and compliance of the system. In summary, this method not only optimizes resource allocation and data service performance but also strengthens data management and security, providing technical guarantees for the efficient and stable operation of the distributed storage system and the protection of user data.

[0096] In one embodiment, as Figure 9 shown, in step S820, after creating a first storage volume of the first type in the target logical pool and distributing and storing the data in the first storage volume among multiple disks in the target logical pool according to a preset data distribution strategy, the method further includes steps S900 - S910:

[0097] Step S900, create a first data copy of the first storage volume in the target logical pool.

[0098] Wherein, the first data copy is stored in at least one first backup disk in the target logical pool.

[0099] Specifically, when the system creates a storage volume, according to a preset redundancy strategy, data copies are created on multiple disks within the target logical pool. These backup disks are used to store the data copies, aiming to improve data persistence and availability.

[0100] Exemplarily, when creating the first storage volume in the target logical pool, determine the number of copies and the distribution pattern according to the strategy (such as simple copy, EC encoding, etc.). Select the backup disks in the logical pool that meet the strategy requirements and write the data copies to these disks.

[0101] Step S910, in the case where a failed disk is determined to exist in the target logical pool, use the first data copy stored in at least one first backup disk to recover the data of the failed disk.

[0102] Specifically, when a disk failure is detected in a target logical pool, the system automatically restores the data on the failed disk by using the data copies pre-stored on other backup disks, so as to maintain the integrity of the storage volume and the continuity of the service. When a failed disk appears in the target logical pool, the data can be quickly restored from the backup disks, reducing the risk of data loss and improving the availability of the system. Moreover, the failure of any disk will only affect the data storage service within the pool, and the fault domain isolation based on the logical pool is also achieved. During data recovery, the recovery can also be performed within the logical pool, improving the recovery speed.

[0103] Exemplarily, continuously monitor the running status of the disks in the logical pool. Once a disk failure is detected, immediately trigger the fault recovery process. Search for the complete data copies stored on the backup disks, and select appropriate copies for data recovery according to the data distribution and redundancy strategy. Perform the data recovery operation, migrate or copy the copy data on the backup disk to the replacement disk of the failed disk to restore the data integrity of the storage volume.

[0104] In this embodiment, by implementing the above two steps, the method of the present invention effectively improves the data persistence and service quality of the distributed storage system. First, the creation of the first data copy constructs a solid data redundancy mechanism within the target logical pool. Even in the face of a single-point failure, the data can maintain integrity, ensuring the continuous operation of the business. Second, the fault recovery strategy can be directly carried out within this logical pool, greatly shortening the data recovery time and system interruption time, reducing the risk of data service delay and business interruption caused by disk failures, and enhancing the fault tolerance and recovery efficiency of the system. Furthermore, by storing copies and performing fault recovery within the logical pool, the system can avoid cross-logical-pool data migration operations, reduce network transmission delays and processing overheads, and optimize data access performance. At the same time, this strategy also simplifies the management process of fault recovery, focuses on the internal of the logical pool, improves the accuracy and speed of the system recovery operation, and reduces the data consistency risk during the recovery process. In summary, by creating data copies in the target logical pool and implementing automatic fault recovery, the distributed storage system not only enhances the data persistence and availability, but also optimizes the fault response mechanism, significantly shortens the business interruption time, ensures the efficient and stable data service and the security of user data. This data management method provides strong technical support for building a highly available and high-performance cloud storage environment.

[0105] In one embodiment, as Figure 10 shown, after determining the type of the storage volume to be created according to the creation request of the target object in step S800, the method further includes: steps S1000 - S1020:

[0106] Step S1000, when the type of the storage volume to be created is the second type, at least two target logical pools are determined from multiple logical pools according to the performance requirements and redundancy requirements of the storage volume carried in the creation request.

[0107] Specifically, when the system receives a request to create an extended storage volume (i.e., a storage volume of the second type), it will screen out at least two suitable target logical pools from the existing multiple logical pools based on the performance metrics (such as IOPS and throughput) required by the storage volume and the redundancy strategy (such as the number of replicas and the EC encoding strategy).

[0108] Exemplarily, analyze the creation request and extract the parameters of the performance requirements and redundancy requirements. Through a preset logical pool attribute matching algorithm, screen out the logical pools that meet the requirements to ensure that they can carry the data distribution and redundancy strategy of the extended storage volume. Perform a secondary verification of the health status and resource allocation of the matching logical pools to avoid selecting logical pools with potential hazards or insufficient resources as targets.

[0109] Step S1010, create second storage volumes of the second type in at least two target logical pools respectively.

[0110] Among them, the data distributed in the second storage volume is stored in multiple disks of at least two target logical pools.

[0111] Specifically, in the selected logical pools, the system will create extended second storage volumes, and the data will be dispersed and stored on multiple disks in these logical pools according to a preset distribution strategy, such as balanced distribution or consistent hashing ring.

[0112] Exemplarily, in each selected target logical pool, execute the storage volume initialization process to generate an instance of the second type of storage volume. Apply the data distribution algorithm to evenly split and store the data in the storage volume on the disks in each logical pool to ensure that each target logical pool contains a complete data copy to meet the redundancy requirements. Update the metadata management system to record the data distribution location and redundancy information across logical pools for easy fault recovery and data access.

[0113] Step S1020, establish a first association relationship between at least two target logical pools that have stored the same second storage volume.

[0114] Specifically, the system will ensure that a tight first association relationship is established between multiple logical pools storing the data of the same extended storage volume by defining and implementing association rules to support functions such as data synchronization, redundancy management, and fault recovery.

[0115] Exemplarily, association rules are created to define the data synchronization frequency, priority, and conflict resolution mechanism between logical pools. The association rules are implemented to establish data consistency between target logical pools through data distribution and synchronization protocols. The storage volume metadata is updated to record the association status and data distribution details of the associated logical pools, facilitating subsequent management operations such as fault detection and data recovery.

[0116] Exemplarily, as Figure 11 shown, a storage cluster may include multiple storage nodes (Node A, Node B, Node C, Node D, Node E). The storage nodes can be physical nodes or logical nodes in the storage cluster. Classifying multiple disks can result in, for example, Figure 11 the logical pools 60 and 70 shown, and a first association relationship is established between the logical pools 60 and 70.

[0117] In this embodiment, first, by creating and storing extended storage volumes in multiple logical pools, the system can dynamically adjust the data distribution strategy according to actual needs and optimize the utilization efficiency of storage resources. Second, the cross-logical pool redundant storage of data ensures that even if a single logical pool or disk fails, the system can still quickly recover data through the complete data copies in other logical pools, maintaining the high availability and persistence of the data. Establishing the association relationship between logical pools not only realizes the efficient synchronization and consistent management of data but also provides the system with a higher level of disaster tolerance backup and fault recovery capabilities. This association mechanism simplifies the fault detection process of the storage system, accelerates the data recovery speed, and at the same time provides a strong guarantee for the continuity and consistency of data, ensuring the smooth operation of the business and the continuity of the user experience. In summary, by creating extended second storage volumes in at least two target logical pools and establishing the association relationship between them, the system's ability to process large datasets and complex business scenarios is effectively improved, the flexibility and reliability of data distribution are realized, and the fault recovery process is optimized, providing users with continuous, reliable, and high-performance data storage services.

[0118] In one embodiment, as Figure 12 shown, the method further includes: Steps S1200 - S1210:

[0119] Step S1200, create at least one second data copy of the second storage volume in each of at least two target logical pools that have stored the same second storage volume.

[0120] Among them, the second data copies are respectively stored in at least one second backup disk in at least two target logical pools.

[0121] Specifically, to enhance the redundancy and continuous availability of the storage volume data, the system creates and stores at least one data copy in each target logical pool storing the second storage volume data. These copies will be placed on the backup disks within each logical pool, ensuring distributed redundancy and fast access to the data.

[0122] Exemplarily, for each target logical pool, start the data copy creation process, and determine the number of copies and storage locations according to the data redundancy policy. Select a suitable location in the backup disks of each logical pool to store the second data copy, which may depend on the current utilization rate, health status of the disks, and the data distribution algorithm. Update the metadata information to record the exact location and redundancy status of each second data copy for subsequent fault detection and data recovery operations.

[0123] Step S1210, in the case where a faulty disk is detected in one of the at least two target logical pools, use the second data copies stored in at least one of the second backup disks in the at least two target logical pools to recover the data on the faulty disk.

[0124] Specifically, once a disk failure is detected in any target logical pool, the system immediately executes the fault recovery process, using the second data copies in other target logical pools to reconstruct the data on the faulty disk, thereby quickly restoring the data service and the continuity of system operation.

[0125] Exemplarily, continuously detect the status of the disks in each logical pool. Once a faulty disk is found, immediately trigger the data recovery mechanism. Locate the valid second data copies according to the metadata records, and these copies may come from the backup disks of the same or different target logical pools. Execute the data recovery algorithm to migrate the data in the second data copies to the alternative location of the faulty disk to ensure the integrity of the data and the continuous operation of the system.

[0126] In this embodiment, first, the creation of the second data copy ensures that even if a single logical pool or disk fails, the system can still quickly restore the data service by relying on the redundant data copies of other logical pools, avoiding service interruption and enhancing the fault tolerance of the system. Second, the storage of data copies across logical pools not only improves the redundancy level of the data but also optimizes the data recovery process. Even if the data within a logical pool becomes completely unavailable, the system can restore the data from other logical pools to ensure the continuity and efficiency of the data service. The above mechanism simplifies the operations of fault detection and data recovery, reduces the burden on system operation and maintenance personnel through metadata management and automated recovery processes, and improves the response speed and processing capacity of the storage system in the face of complex fault scenarios. Overall, the copy creation of the second storage volume and the cross-logical pool fault recovery mechanism significantly enhance the data security and service continuity of the distributed storage system, laying a solid foundation for building a highly reliable cloud storage environment.

[0127] In one embodiment, as Figure 13 shown, step S1210, use the second data copy stored in at least one second backup disk in at least two target logical pools to recover the data of the faulty disk. It includes steps S1300 - S1330:

[0128] Step S1300, when it is determined that there is a faulty disk in the logical pool storing the second storage volume, determine whether the data of the second storage volume stored in the faulty disk is lost.

[0129] Specifically, when the system detects that a disk in a logical pool fails, the primary task is to evaluate whether the failure has caused the loss of the second storage volume data stored on the disk, providing guidance for subsequent recovery operations.

[0130] Exemplarily, check the data status on the faulty disk, including data integrity, accessibility, and availability. If the data exists but is inaccessible, the system attempts to recover the data through underlying disk repair techniques (such as bad track repair, disk rereading, etc.); if the data is completely lost, it enters the data recovery process.

[0131] Step S1310, when it is determined that the data of the second storage volume stored in the faulty disk is lost, use the second data copy stored in the second backup disk in the logical pool to which the faulty disk belongs to recover the data of the faulty disk.

[0132] Specifically, once it is confirmed that the data is lost, the system will first use the second data copy within the same logical pool to perform the data recovery operation to restore the data service as soon as possible.

[0133] Exemplarily, according to the preset metadata and data distribution strategy, locate the second data copy on the second backup disk associated with the faulty disk. Execute a data recovery algorithm to migrate the data in the second data copy to the replacement disk of the faulty disk to ensure data integrity and service continuity.

[0134] Step S1320, in the case where the data recovery of the faulty disk using the second data copy stored in the second backup disk within the logical pool to which the faulty disk belongs fails, determine the backup logical pool associated with the logical pool to which the faulty disk belongs according to the first association relationship.

[0135] Specifically, if the recovery attempt in step S1310 fails, the system will jump to a higher-level recovery mechanism, and according to the first association relationship between logical pools, search for the data copy in the associated backup logical pool for recovery.

[0136] Exemplarily, evaluate the reason for the recovery failure in step S1310. If it is due to the failure of the second backup disk itself or the corruption of the data copy, the system will automatically switch to the backup logical pool according to the association rule. Search for the metadata record to locate the valid second data copy in the backup logical pool and prepare for secondary data recovery.

[0137] Step S1330, recover the data of the faulty disk using the second data copy stored in the second backup disk within the backup logical pool.

[0138] Specifically, use the data copy of the backup logical pool to perform a data recovery operation to ensure that even in the case where the recovery in step S1310 fails, the data can be recovered in a timely and effective manner.

[0139] In this embodiment, by constructing a multi-level fault detection and data recovery process, the persistence and availability of the second storage volume data are significantly enhanced. First, the primary data recovery mechanism can quickly respond to disk failures by rapidly utilizing the data copies within the same logical pool, avoiding the situation where the data is unavailable for a long time and reducing the service interruption time. Second, the secondary data recovery process provides a higher level of disaster tolerance through the utilization of data copies across logical pools. Even in the case where a single logical pool is completely unavailable, it can rely on the associated backup logical pool to quickly recover the data, ensuring the continuity of the data service. Through the automated fault detection and recovery process, the complexity and response time of system operation and maintenance are significantly reduced, enhancing the self-repair ability of the system and the efficiency of data recovery. The multi-level data recovery strategy greatly improves the data security and business continuity of the distributed storage system, provides users with a more reliable and efficient data storage and access service, and at the same time reduces the business risks and economic losses caused by data loss.

[0140] In one embodiment, as Figure 14 shown, in step S200, multiple disks in the same storage cluster are classified according to a preset policy to obtain multiple logical pools. It includes steps S1400 - S1420:

[0141] Step S1400, obtain the physical parameters and disk resource information of multiple storage nodes.

[0142] Among them, the storage cluster includes multiple storage nodes, and each storage node includes multiple disks.

[0143] Specifically, one of the cores of distributed storage cluster management is to effectively classify storage nodes to optimize resource allocation and data distribution strategies. It involves collecting comprehensive information of storage nodes, including physical parameters such as hardware configuration (CPU, memory), disk types (SSD, HDD), disk capacity, network bandwidth, etc., and resource information such as the current usage and health status of disks.

[0144] Step S1410, classify multiple storage nodes according to the physical parameters and disk resource information of multiple storage nodes to obtain multiple storage node sets.

[0145] Specifically, based on the collected physical parameters and disk resource information, the system executes a storage node classification algorithm to classify storage nodes with similar physical characteristics, similar resource utilization, or in the same geographical location into the same set, providing a classification basis for subsequent construction of logical pools.

[0146] Step S1420, classify the multiple disks included in multiple storage nodes belonging to the same storage node set into the same logical pool.

[0147] Specifically, after completing the classification of storage nodes, the system regards the disk resources of storage nodes in the same set as storage units with the same or similar characteristics, and then merges them into one logical pool to achieve refined storage management based on hardware characteristics and resource status.

[0148] Exemplarily, all disks under the same storage node set are regarded as candidate members of the same logical pool. Execute the logical pool construction process, select disks according to a preset policy (such as performance optimization, redundancy policy, cost control), and divide the disks belonging to the same storage node into the same logical pool.

[0149] In this embodiment, first, based on the classification of storage nodes according to physical parameters and disk resource information, the construction of the logical pool ensures that hardware compatibility, resource status, and geographical location factors are taken into account, optimizing the data distribution logic and improving data read / write speed and storage efficiency. Then, according to the classified storage nodes, the disks are classified, and the disks of the storage nodes belonging to the same class after classification are divided into the same logical pool, which not only facilitates the implementation of unified data redundancy and recovery strategies, but also simplifies the management and maintenance of the storage system and enhances the disaster tolerance of the system.

[0150] In one embodiment, as Figure 15 shown, the method further includes: steps S1500 - S1520:

[0151] Step S1500, when the type of the storage volume to be created is the second type, determine at least two target logical pools among multiple logical pools.

[0152] Among them, the storage nodes included in at least two target logical pools are different.

[0153] Specifically, for the second - type storage volume with specific performance and redundancy requirements, the system intelligently selects a combination of logical pools containing different storage nodes as the target in a multi - logical - pool environment to disperse storage risks and improve data redundancy.

[0154] Exemplarily, analyze the special requirements of the second - type storage volume, such as high performance, high availability, or geographically dispersed storage. Screen and select at least two logical pools covering different storage nodes from multiple logical pools to ensure the diversity of data distribution and wide - area redundancy.

[0155] Step S1510, create a second storage volume of the second type in each of the at least two target logical pools.

[0156] Among them, the data included in the second storage volume is distributed and stored in multiple disks of at least two target logical pools.

[0157] Specifically, within the selected target logical pools, the system will create a second - type storage volume and follow the pre - set data distribution strategy to evenly distribute the storage volume data on the disks of different logical pools to achieve optimal storage efficiency and data protection.

[0158] Step S1520, establish a first association relationship between at least two target logical pools that have stored the same second storage volume.

[0159] Specifically, in order to achieve cross - logical - pool data synchronization and redundancy management, the system will establish a clear association relationship between the logical pools storing the same second - type storage volume to support efficient data synchronization and consistent management.

[0160] In this embodiment, the target selection across logical pools and the creation of storage volumes ensure that data is dispersed among different nodes, effectively preventing single-point failures and enhancing the overall robustness of the storage system and its ability to handle disasters. Secondly, the wide-area distribution of data is stored on multiple disks. Combining the requirements of high performance and high redundancy, it not only ensures fast response to data access but also enhances data persistence and security, significantly improving the user experience and service quality. The established first association relationship between logical pools not only simplifies data synchronization and consistency management but also provides a clear path for fault recovery and data migration, greatly reducing the complexity of data management and enhancing the maintainability and scalability of the system. In summary, this method of creating and associating the second type of storage volumes across logical pools provides a high level of data distribution and redundancy management capabilities for distributed storage systems, ensuring the efficiency, reliability, and security of data storage.

[0161] In one embodiment, the method further includes: establishing a first data synchronization mechanism between at least two logical pools where the first association relationship has been established.

[0162] Specifically, the system builds a data synchronization framework between associated logical pools to ensure that any data changes in the second storage volume within any one logical pool can be promptly detected and responded to by other relevant logical pools, achieving data consistency or quasi-consistency.

[0163] Among them, the first data synchronization mechanism includes:

[0164] In the case where the data in the second storage volume of any one of at least two logical pools where the first association relationship has been established is updated, the data in the second storage volumes of the other logical pools among the at least two logical pools where the first association relationship has been established is updated simultaneously.

[0165] Specifically, when data updates occur in the second storage volume of any one logical pool, through the real-time data synchronization mechanism, it is ensured that the data in the corresponding storage volumes of other logical pools can be immediately updated to maintain data consistency.

[0166] Or, in the case where the data in the second storage volume of any one of at least two logical pools where the first association relationship has been established is updated, the data in the second storage volumes of the other logical pools among the at least two logical pools where the first association relationship has been established is updated after a preset duration.

[0167] Specifically, to address the network pressure and resource consumption issues that may be caused by real-time synchronization, the system also supports synchronizing the changes to other relevant logical pools after a preset duration after data updates to achieve a quasi-consistent state. A data synchronization delay time window can be defined to allow data to be briefly cached locally before synchronization.

[0168] In this embodiment, through a real-time or delayed data synchronization mechanism, the distributed storage system not only improves data consistency and stability, but also optimizes resource utilization efficiency and enhances the overall performance of the system. The real-time data synchronization strategy ensures that the data of the second storage volume between associated logical pools always remains consistent, which is crucial for application scenarios that require high data consistency. Secondly, the delayed data synchronization strategy introduced by the system balances the relationship between data consistency and network resource consumption, avoiding network bottlenecks and increased latency caused by high-frequency data synchronization, and is particularly suitable for scenarios where data is updated frequently but the consistency requirement is slightly lower, such as logging or big data analysis. By establishing the first association relationship and data synchronization mechanism between logical pools, the flexibility and reliability of the storage system are enhanced.

[0169] In one embodiment, as Figure 16 shown, the method further includes: steps S1600 - S1620:

[0170] Step S1600, in response to a dual-active storage request of a target object, when the type of the storage volume to be created is the first type, determine at least one target logical pool in at least two storage clusters respectively.

[0171] Among them, the distributed storage system includes at least two storage clusters.

[0172] Specifically, when the system receives a dual-active storage request initiated by a target object, it means that the requester hopes that the data can be redundantly stored in an Active-Active manner in two or more storage clusters. For this purpose, first, according to the specific conditions of the request, at least one target logical pool is selected from at least two storage clusters respectively to undertake the creation and data storage responsibilities of the first-type storage volume.

[0173] Step S1610, create a first storage volume of the first type in at least one target logical pool determined in at least two storage clusters respectively.

[0174] Step S1620, establish a second association relationship between the target logical pools in at least two storage clusters that have stored the same first storage volume.

[0175] Specifically, to achieve the goal of dual-active storage, that is, real-time or near-real-time synchronization of data across all selected storage clusters, the system needs to establish a second association relationship between the target logical pools. This relationship defines the rules and processes for data synchronization, including the triggering conditions for data synchronization, synchronization directions, synchronization protocols, and conflict resolution mechanisms, etc., to ensure data consistency and high availability. By implementing these association rules between the target logical pools, a data synchronization network is established to ensure that any data update on one side can be quickly perceived and synchronized by other sides, maintaining data consistency.

[0176] Exemplarily, as Figure 17 shown, the distributed storage system includes two storage clusters. The first storage cluster includes multiple storage nodes (Node A, Node B, Node C), and the second storage cluster includes multiple storage nodes (Node D, Node E). The storage nodes can be physical nodes or logical nodes in the storage cluster. Classifying multiple disks can obtain, for example Figure 17 the logical pools 80 and 90 shown, and a second association relationship is established between the logical pools 80 and 90.

[0177] Exemplarily, as Figure 18 shown, the distributed storage system includes three storage clusters. The first storage cluster includes multiple storage nodes (Node A, Node B, Node C), the second storage cluster includes multiple storage nodes (Node D, Node E), and the third storage cluster includes multiple storage nodes (Node F, Node G). The storage nodes can be physical nodes or logical nodes in the storage cluster. Classifying multiple disks can obtain, for example Figure 18 the logical pools 100, 110, and 120 shown, and second association relationships are established between the logical pools 100, 110, and 120 with each other.

[0178] In this embodiment, by constructing a redundant storage architecture based on dual-active storage requests, the reliability, access speed, and disaster recovery capabilities of data storage are significantly improved. The system establishes a second association relationship between the target logical pools of two storage clusters to ensure data synchronization between the two clusters. Even if one of the clusters fails, the other cluster can immediately take over the service, ensuring business continuity and data reliability.

[0179] In one embodiment, as Figure 19 shown, the method further includes steps S1900 - S1930:

[0180] Step S1900, designating one of the at least two storage clusters with the second association relationship established as the primary storage site, and designating the other storage clusters with the second association relationship established as the standby storage sites.

[0181] Specifically, one cluster is established as the primary storage site, and the remaining clusters are used as backup storage sites to form a dual-active or multi-active storage environment. The primary storage site bears the daily data reading, writing, and access requests, while the backup storage site takes over the service when the primary storage site fails and also undertakes the function of data recovery.

[0182] Step S1910, when the primary storage site is normal, use the primary storage site to provide storage services for the target object.

[0183] Specifically, when the primary storage site is running normally, all storage service requests from the target object are processed by the primary storage site to achieve efficient data reading and writing.

[0184] Step S1920, when the primary storage site fails, use the backup storage site to provide storage services for the target object, and

[0185] Step S1930, use the data of the first storage volume stored in the backup storage site to recover the data of the primary storage site.

[0186] Specifically, when the primary storage site fails, the system automatically redirects the service requests to the backup storage site to seamlessly continue providing storage services. At the same time, the backup storage site uses the data copy of the primary site stored in it for data recovery to ensure that the primary site can roll back to the state before the failure after the failure is repaired. When the primary storage site cannot provide services normally, it automatically switches to the backup storage site to ensure the continuity of the business.

[0187] In this embodiment, by distinguishing between the primary storage site and the backup storage site, a dynamic dual-active storage environment is established, enabling the system to quickly continue providing storage services through the backup storage site when the primary storage site fails, avoiding service interruption, and ensuring the continuity of data services. Through the data synchronization mechanism and the efficient utilization of the backup storage site, not only the redundancy and durability of data are improved, but also the response speed of storage services is optimized, the data access latency is reduced, and the user experience is enhanced. The failover and primary site data recovery mechanisms ensure the integrity of data. Even if the primary storage site suffers a serious failure, it can be quickly recovered through the data copy of the backup storage site, effectively preventing data loss and improving the overall reliability and stability of the system.

[0188] In one embodiment, as Figure 20 shown, the method further includes: Steps S2000 - S2030:

[0189] Step S2000, when the type of the storage volume to be created is the second type, determine at least two target logical pools in multiple logical pools of the first storage cluster.

[0190] Specifically, the second type of storage volume is the storage volume that needs to be stored across logical pools. At least two target logical pools are used in the first cluster to create the second type of storage volume.

[0191] Step S2010: Create second storage volumes of the second type in at least two target logical pools of the first storage cluster.

[0192] Among them, the data contained in the second storage volume is distributed and stored in multiple disks of at least two target logical pools.

[0193] Specifically, in the selected at least two target logical pools, create a second type of storage volume to ensure that the data is distributed and stored across multiple disks, improving data persistence and access efficiency.

[0194] Step S2020: Establish a first association relationship between at least two target logical pools that have stored the same second storage volume.

[0195] Specifically, construct the relationship between the target logical pools that have stored the same second type of storage volume to provide a framework for data synchronization and fault isolation. The first association relationship is the relationship between at least two target logical pools in the same storage cluster that store the same second storage volume.

[0196] Step S2030: Establish a third association relationship between the second storage volume in the first storage cluster and the first storage volume in the second storage cluster.

[0197] Specifically, between the first storage cluster and the second storage cluster, establish a connection between the second type of storage volume and the first storage volume of the standby storage cluster to form a cross-cluster data redundancy and synchronization mechanism, enhancing the system's disaster recovery and business continuity capabilities. The third association relationship is the relationship between the second storage volume of the second type in the first storage cluster and the first storage volume of the first type in the second storage cluster, realizing cross-cluster synchronization and redundancy of data.

[0198] Exemplarily, through the metadata management system, track the mapping relationship and data status between the second type of storage volume and the first storage volume of the standby cluster, providing a basis for data synchronization and fault recovery.

[0199] Exemplarily, as Figure 21 shown, the distributed storage system includes two storage clusters. The first storage cluster includes multiple storage nodes (Node A, Node B, Node C, Node D, Node E), and the second storage cluster includes multiple storage nodes (Node F, Node G). The storage nodes can be physical nodes or logical nodes in the storage cluster. Classifying multiple disks can obtain, for example Figure 21The logical pools 130, 140, and 150 shown. A first association relationship is established between the logical pool 130 and the logical pool 140. A third association relationship is established between the second storage volume (logical pools 130 and 140) in the first storage cluster and the first storage volume (logical pool 150) in the second storage cluster.

[0200] In this embodiment, the selection of the target logical pool and the creation of the storage volume ensure the balance and persistence of data distribution within the first storage cluster, enhancing the resistance to single-point failures. Secondly, the establishment of the first association relationship between logical pools and the third association relationship between clusters forms a multi-level data redundancy and synchronization network. Even if a certain logical pool or cluster encounters a failure, the system can quickly recover data through replicas in other logical pools or clusters, maintaining business continuity. A first association relationship is established between two logical pools in the same cluster to achieve cross-logical pool redundant backup of data. A third association relationship is established between the second storage volume in the first storage cluster and the first storage volume in the second storage cluster to ensure data synchronization between clusters, improving data reliability and system stability.

[0201] In one embodiment, the method further includes: establishing a first data synchronization mechanism between at least two logical pools with the first association relationship established, where the first data synchronization mechanism includes:

[0202] When the data in the second storage volume of any one of the at least two logical pools with the first association relationship established is updated, the data in the second storage volumes of the other logical pools among the at least two logical pools with the first association relationship established is updated simultaneously.

[0203] Specifically, between at least two logical pools with the first association relationship established, a data synchronization mechanism is established to ensure that when the data in the second storage volume of any logical pool is updated, the data in the second storage volumes of other associated logical pools can be instantaneously synchronized and updated to maintain data consistency and availability.

[0204] Establish a second data synchronization mechanism between the second storage volume of the first storage cluster and the first storage volume of the second storage cluster with the third association relationship established, where the second data synchronization mechanism includes:

[0205] When the data in any one of the second storage volume and the first storage volume with the third association relationship established is updated, the data in the other storage volume is updated after a preset time period.

[0206] Specifically, between the first storage cluster and the second storage cluster, based on the established third association relationship, a second data synchronization mechanism is implemented, such that after the data in any one storage volume is updated, the data in the other storage volume can be updated after a preset time duration, ensuring cross-cluster data consistency and high availability, while also considering the reasonable utilization of network resources and latency management.

[0207] Exemplarily, the method in this embodiment can be applicable to the scenario of two locations and three centers (that is, two geographical regions, but three data storage centers). A first association relationship is established between two data storage centers in the same region, and the first data synchronization mechanism is used. A third association relationship is established between data storage centers in different regions, and the second data synchronization mechanism is used. That is, the data security policy based on the extended cluster is adopted in the same city, and the data security policy of dual-active asynchronous data synchronization is adopted between different locations; it can achieve real-time synchronization of data in the same city and asynchronous disaster recovery of data between two locations.

[0208] In this embodiment, the instant data synchronization update mechanism (the first data synchronization mechanism) ensures the instant consistency of data within multiple logical pools, reduces potential problems caused by data inconsistency, such as read-write conflicts or service interruptions, and enhances the overall stability and data security of the system. Secondly, the cross-cluster data synchronization mechanism (the second data synchronization mechanism) balances the consumption of network resources by introducing a latency mechanism while ensuring data consistency, avoiding network congestion and high latency that may be brought about by real-time synchronization, and is particularly applicable to clusters with a wide geographical distribution, improving the performance and efficiency of the system in a large-scale deployment environment.

[0209] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware, but in many cases, the former is a better implementation manner.

[0210] An embodiment of the present application also provides a management device for storage space. Figure 22 It is a structural block diagram of a management device for storage space according to an embodiment of the present application. The device includes:

[0211] A disk classification module 2201, configured to classify multiple disks in the same storage cluster according to a preset policy to obtain multiple logical pools, where at least two disks are included in one logical pool.

[0212] A storage volume creation module 2202, configured to create a first storage volume of a first type in a target logical pool among multiple logical pools when the type of the storage volume to be created is the first type, where the data included in the first storage volume is distributed and stored in multiple disks of the target logical pool, and the data of the first-type storage volumes in different logical pools is isolated from each other.

[0213] In an exemplary embodiment, the disk classification module 2201 is further configured to determine the disk parameters of multiple disks in the same storage cluster respectively. In response to the service requirements of the target object, match a corresponding disk classification policy. Classify the multiple disks according to the disk classification policy and the disk parameters of the multiple disks respectively to obtain multiple logical pools.

[0214] In an exemplary embodiment, the disk classification module 2201 is further configured to determine the read / write modes of the multiple disks respectively according to the disk parameters of the multiple disks. Determine a first type of disk and a second type of disk among the multiple disks according to the read / write modes of the multiple disks respectively, where the read / write mode of the first type of disk is different from that of the second type of disk and the read / write speed of the first type of disk is greater than that of the second type of disk. Select a first preset number of the first type of disks in the multiple disks as the same set to obtain at least one first logical pool. And select a second preset number of the first type of disks and a third preset number of the second type of disks in the multiple disks as the same set to obtain at least one second logical pool.

[0215] In an exemplary embodiment, the disk classification module 2201 is further configured to determine the disk models and disk capacities of the multiple disks respectively according to the disk parameters of the multiple disks. Classify the disks with the same disk model and the same disk capacity among the multiple disks into the same set to obtain multiple logical pools.

[0216] In an exemplary embodiment, the storage volume creation module 2202 is further configured to determine the type of the storage volume to be created according to the creation request of the target object. When it is determined that the type of the storage volume to be created is the first type, determine the target logical pool among the multiple logical pools according to the performance requirements of the storage volume carried in the creation request. Create a first storage volume of the first type in the target logical pool, and distribute and store the data in the first storage volume in multiple disks of the target logical pool according to a preset data distribution policy, where a data isolation logic is set to isolate the data of the first-type storage volumes in different logical pools from each other.

[0217] In an exemplary embodiment, the apparatus further includes:

[0218] A first creation module, configured to create a first data copy of a first storage volume within a target logical pool, where the first data copy is stored in at least one first backup disk in the target logical pool.

[0219] A first backup module, configured to, when it is determined that there is a faulty disk in the target logical pool, recover the data of the faulty disk by using the first data copy stored in at least one first backup disk.

[0220] In an exemplary embodiment, the apparatus further includes:

[0221] A first logical pool determination module, configured to, when the type of the storage volume to be created is a second type, determine at least two target logical pools from multiple logical pools according to the performance requirements and redundancy requirements of the storage volume carried in the creation request.

[0222] A second creation module, configured to create second storage volumes of the second type in at least two target logical pools respectively, where the data included in the second storage volumes is distributed and stored in multiple disks of at least two target logical pools.

[0223] A first relationship establishment module, configured to establish a first association relationship between at least two target logical pools that have stored the same second storage volume.

[0224] In an exemplary embodiment, the apparatus further includes:

[0225] A third creation module, configured to create at least one second data copy of the second storage volume in at least two target logical pools that have stored the same second storage volume respectively, where the second data copies are stored in at least one second backup disk in at least two target logical pools respectively.

[0226] A second backup module, configured to, when it is determined that there is a faulty disk in one of the at least two target logical pools, recover the data of the faulty disk by using the second data copy stored in at least one second backup disk in the at least two target logical pools.

[0227] In an exemplary embodiment, the second backup module is further configured to determine whether the data of the second storage volume stored in the faulty disk is lost when it is determined that there is a faulty disk in the logical pool storing the second storage volume. When it is determined that the data of the second storage volume stored in the faulty disk is lost, the data of the faulty disk is restored using the second data copy stored in the second backup disk in the logical pool to which the faulty disk belongs. When the restoration of the data of the faulty disk using the second data copy stored in the second backup disk in the logical pool to which the faulty disk belongs fails, a backup logical pool associated with the logical pool to which the faulty disk belongs is determined according to the first association relationship. The data of the faulty disk is restored using the second data copy stored in the second backup disk in the backup logical pool.

[0228] In an exemplary embodiment, the disk classification module 2201 is further configured to obtain the physical parameters and disk resource information of multiple storage nodes. Classify the multiple storage nodes according to the physical parameters and disk resource information of the multiple storage nodes to obtain multiple storage node sets. Classify the multiple disks included in the multiple storage nodes belonging to the same storage node set into the same logical pool.

[0229] In an exemplary embodiment, the apparatus further includes:

[0230] A second logical pool determination module, configured to determine at least two target logical pools from multiple logical pools when the type of the storage volume to be created is the second type, where the storage nodes included in the at least two target logical pools are different.

[0231] A fourth creation module, configured to create second storage volumes of the second type in the at least two target logical pools respectively, where the data included in the second storage volume is distributed and stored in multiple disks of the at least two target logical pools.

[0232] A second relationship establishment module, configured to establish a first association relationship between at least two target logical pools that have stored the same second storage volume.

[0233] In an exemplary embodiment, the apparatus further includes:

[0234] The first data synchronization module is used to establish a first data synchronization mechanism between at least two logical pools with a first association relationship established. Among them, the first data synchronization mechanism includes: when the data in the second storage volume of any one of the at least two logical pools with the first association relationship is updated, the data in the second storage volumes of the other logical pools among the at least two logical pools with the first association relationship is updated simultaneously. Or, when the data in the second storage volume of any one of the at least two logical pools with the first association relationship is updated, the data in the second storage volumes of the other logical pools among the at least two logical pools with the first association relationship is updated after a preset duration.

[0235] In an exemplary embodiment, the apparatus further includes:

[0236] The third logical pool determination module is used to, in response to the dual-active storage request of the target object, determine at least one target logical pool in each of at least two storage clusters when the type of the storage volume to be created is the first type.

[0237] The fifth creation module is used to create a first storage volume of the first type in at least one target logical pool determined in each of at least two storage clusters.

[0238] The third relationship establishment module is used to establish a second association relationship between the target logical pools in at least two storage clusters that have stored the same first storage volume.

[0239] In an exemplary embodiment, the apparatus further includes:

[0240] The site determination module is used to use one of the at least two storage clusters with the second association relationship established as the primary storage site, and use the other storage clusters among the at least two storage clusters with the second association relationship established as the standby storage sites.

[0241] The service module is used to provide storage services for the target object using the primary storage site when the primary storage site is normal.

[0242] The standby module is used to provide storage services for the target object using the standby storage site when the primary storage site fails, and to recover the data of the primary storage site using the data of the first storage volume stored in the standby storage site.

[0243] In an exemplary embodiment, the apparatus further includes:

[0244] The fourth logical pool determination module is used to determine at least two target logical pools in multiple logical pools of the first storage cluster when the type of the storage volume to be created is the second type.

[0245] A sixth creation module, configured to respectively create second - type second storage volumes in at least two target logical pools of the first storage cluster, where the data included in the second storage volumes is distributed and stored in multiple disks of at least two target logical pools.

[0246] A fourth relationship - establishing module, configured to establish a first association relationship between at least two target logical pools that have stored the same second storage volume.

[0247] A fifth relationship - establishing module, configured to establish a third association relationship between the second storage volumes in the first storage cluster and the first storage volumes in the second storage cluster.

[0248] In an exemplary embodiment, the apparatus further includes:

[0249] A second data synchronization module, configured to establish a first data synchronization mechanism between at least two logical pools where the first association relationship has been established, where the first data synchronization mechanism includes: when the data in the second storage volume of any one of at least two logical pools where the first association relationship has been established is updated, the data in the second storage volumes of the other logical pools where the first association relationship has been established is updated simultaneously.

[0250] A third data synchronization module, configured to establish a second data synchronization mechanism between the second storage volume of the first storage cluster and the first storage volume of the second storage cluster where the third association relationship has been established, where the second data synchronization mechanism includes: when the data in any one of the second storage volume and the first storage volume where the third association relationship has been established is updated, the data in the other storage volume is updated after a preset time period.

[0251] For the description of the features in the corresponding embodiments of the storage - space management apparatus, reference can be made to the relevant descriptions in the corresponding embodiments of the storage - space management method, which will not be elaborated here one by one.

[0252] An embodiment of the present application further provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above - mentioned embodiments of the storage - space management method.

[0253] An embodiment of the present application further provides a computer - readable storage medium, in which a computer program is stored, where the computer program is configured to execute the steps in any one of the above - mentioned embodiments of the storage - space management method when running.

[0254] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: various media that can store computer programs, such as USB flash drives, read-only memory (ROM for short), random access memory (RAM for short), external hard drives, magnetic disks, or optical discs.

[0255] The embodiments of the present application also provide a computer program product. The above computer program product includes a computer program, and when the computer program is executed by a processor, it implements the steps in any of the above embodiments of the storage space management method.

[0256] The embodiments of the present application also provide another computer program product, including a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the steps in any of the above embodiments of the storage space management method.

[0257] Those skilled in the art can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Skilled professionals can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0258] The above has introduced in detail a storage space management method, device, electronic device, computer-readable storage medium, and computer program product provided by the present application. Specific examples are used in this article to elaborate on the principles and implementation manners of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application. It should be noted that for those of ordinary skill in the art in the technical field, without departing from the principle of the present application, several improvements and modifications can still be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

Claims

1. A method for managing storage space, characterized in that, Applied to a distributed storage system, the distributed storage system includes a storage cluster, and the storage cluster includes multiple disks. The method includes: Classifying the multiple disks of the same storage cluster according to a preset policy to obtain multiple logical pools, where at least two of the disks are included in one logical pool; When the type of the storage volume to be created is the first type, creating the first storage volume of the first type in a target logical pool among the multiple logical pools, where the data included in the first storage volume is distributed and stored in multiple disks of the target logical pool, and the data of the first type of storage volumes in different logical pools is isolated from each other.

2. The storage space management method according to claim 1, wherein The classifying the multiple disks of the same storage cluster according to a preset policy to obtain multiple logical pools includes: Determining the disk parameters of the multiple disks in the same storage cluster respectively; Matching a corresponding disk classification policy for the service requirement in response to the service requirement of the target object; Classifying the multiple disks according to the disk classification policy and the disk parameters of the multiple disks respectively to obtain multiple logical pools.

3. The method for managing a storage space according to claim 2, wherein The classifying the multiple disks according to the disk classification policy and the disk parameters of the multiple disks respectively to obtain multiple logical pools includes: Determining the read / write modes of the multiple disks respectively according to the disk parameters of the multiple disks; Determining a first type of disks and a second type of disks among the multiple disks according to the read / write modes of the multiple disks respectively, where the read / write mode of the first type of disks is different from that of the second type of disks and the read / write speed of the first type of disks is greater than that of the second type of disks; Selecting a first preset number of the first type of disks as the same set among the multiple disks to obtain at least one first logical pool; and Selecting a second preset number of the first type of disks and a third preset number of the second type of disks as the same set among the multiple disks to obtain at least one second logical pool.

4. The method for managing a storage space according to claim 2, wherein, The classifying the multiple disks according to the disk classification policy and the disk parameters of the multiple disks respectively to obtain multiple logical pools includes: Determining the disk models and disk capacities of the multiple disks respectively according to the disk parameters of the multiple disks; Classifying the disks with the same disk model and the same disk capacity among the multiple disks into the same set according to the disk models and disk capacities of the multiple disks respectively to obtain multiple logical pools.

5. The method for managing a storage space according to any one of claims 1-4, characterized in that, The creating the first storage volume of the first type in a target logical pool among the multiple logical pools when the type of the storage volume to be created is the first type includes: Determining the type of the storage volume to be created according to the creation request of the target object; When it is determined that the type of the storage volume to be created is the first type, determining the target logical pool among the multiple logical pools according to the performance requirement of the storage volume carried in the creation request. Create a first storage volume of the first type within the target logical pool, and distribute and store the data in the first storage volume among multiple disks in the target logical pool according to a preset data distribution strategy. Among them, set up a data isolation logic to isolate the data of the first-type storage volumes in different logical pools from each other.

6. The method for managing a storage space according to claim 5, wherein After creating the first storage volume of the first type within the target logical pool and distributing and storing the data in the first storage volume among multiple disks in the target logical pool according to a preset data distribution strategy, the method further includes: Create a first data copy of the first storage volume within the target logical pool, where the first data copy is stored in at least one first backup disk in the target logical pool; When it is determined that there is a faulty disk in the target logical pool, use the first data copy stored in at least one first backup disk to recover the data of the faulty disk.

7. The method for managing a storage space according to claim 5, wherein After determining the type of the storage volume to be created according to the creation request of the target object, the method further includes: When the type of the storage volume to be created is the second type, determine at least two target logical pools among the multiple logical pools according to the performance requirements and redundancy requirements of the storage volume carried in the creation request; Create second storage volumes of the second type in the at least two target logical pools respectively, where the data included in the second storage volumes is distributed and stored among multiple disks in the at least two target logical pools; Establish a first association relationship between the at least two target logical pools that have stored the same second storage volume.

8. The method for managing a storage space according to claim 7, wherein The method further includes: Create at least one second data copy of the second storage volume in the at least two target logical pools that have stored the same second storage volume respectively, where the second data copies are stored in at least one second backup disk in the at least two target logical pools respectively; When it is determined that there is a faulty disk in one of the at least two target logical pools, use the second data copy stored in at least one second backup disk in the at least two target logical pools to recover the data of the faulty disk.

9. The method for managing a storage space according to claim 8, wherein The using the second data copy stored in at least one second backup disk in the at least two target logical pools to recover the data of the faulty disk includes: When it is determined that there is a faulty disk in the logical pool storing the second storage volume, determine whether the data of the second storage volume stored in the faulty disk is lost; When it is determined that the data of the second storage volume stored in the faulty disk is lost, use the second data copy stored in the second backup disk in the logical pool where the faulty disk belongs to recover the data of the faulty disk; When the recovery of the data of the faulty disk using the second data copy stored in the second backup disk in the logical pool where the faulty disk belongs fails, determine the backup logical pool associated with the logical pool where the faulty disk belongs according to the first association relationship; Recover the data of the faulty disk using the second data copy stored in the second backup disk within the backup logical pool.

10. The method for managing a storage space according to any one of claims 1-4, characterized in that, The storage cluster includes multiple storage nodes, and each storage node includes multiple disks. Classifying the multiple disks of the same storage cluster according to a preset policy to obtain multiple logical pools further includes: Obtain the physical parameters and disk resource information of the multiple storage nodes; Classify the multiple storage nodes according to the physical parameters and disk resource information of the multiple storage nodes to obtain multiple storage node sets; Classify the multiple disks included in the multiple storage nodes belonging to the same storage node set into the same logical pool.

11. The method for managing a storage space according to claim 10, wherein, The method further includes: When the type of the storage volume to be created is the second type, determine at least two target logical pools among the multiple logical pools, where the storage nodes included in the at least two target logical pools are different; Create the second storage volume of the second type in the at least two target logical pools respectively, where the data included in the second storage volume is distributed and stored in the multiple disks of the at least two target logical pools; Establish a first association relationship between the at least two target logical pools that have stored the same second storage volume.

12. The method for managing a storage space according to claim 11, wherein The method further includes: Establish a first data synchronization mechanism between at least two logical pools where the first association relationship has been established, where the first data synchronization mechanism includes: When the data in the second storage volume of any one of the at least two logical pools where the first association relationship has been established is updated, the data in the second storage volumes of the other logical pools among the at least two logical pools where the first association relationship has been established is updated simultaneously; Or, when the data in the second storage volume of any one of the at least two logical pools where the first association relationship has been established is updated, the data in the second storage volumes of the other logical pools among the at least two logical pools where the first association relationship has been established is updated after a preset duration.

13. The method for managing a storage space according to any one of claims 1-4, characterized in that, The distributed storage system includes at least two storage clusters, and the method further includes: In response to the dual-active storage request of the target object, when the type of the storage volume to be created is the first type, determine at least one target logical pool in each of the at least two storage clusters; Create the first storage volume of the first type in the at least one target logical pool determined in each of the at least two storage clusters; Establish a second association relationship between the target logical pools that have stored the same first storage volume in the at least two storage clusters.

14. The method for managing a storage space according to claim 13, wherein The method further includes: Regard one of the at least two storage clusters where the second association relationship has been established as the primary storage site, and regard the other storage clusters among the at least two storage clusters where the second association relationship has been established as the standby storage sites; When the primary storage site is normal, use the primary storage site to provide storage services for the target object; In the event of a failure of the primary storage site, the secondary storage site is used to provide storage services for the target object, and the data of the primary storage site is restored using the data of the first storage volume stored in the secondary storage site.

15. The method for managing a storage space according to claim 13, wherein The method further includes: When the type of the storage volume to be created is the second type, at least two target logical pools are determined from multiple logical pools of the first storage cluster; Second storage volumes of the second type are respectively created in the at least two target logical pools of the first storage cluster, wherein the data included in the second storage volumes is distributed and stored in multiple disks of the at least two target logical pools; A first association relationship is established between the at least two target logical pools that have stored the same second storage volume; A third association relationship is established between the second storage volume in the first storage cluster and the first storage volume in the second storage cluster.

16. The management method of the storage space according to claim 15, characterized in that, The method further includes: A first data synchronization mechanism is established between at least two logical pools for which the first association relationship has been established, wherein the first data synchronization mechanism includes: When the data in the second storage volume in any one of the at least two logical pools for which the first association relationship has been established is updated, the data in the second storage volumes in the other logical pools for which the first association relationship has been established is updated simultaneously; A second data synchronization mechanism is established between the second storage volume in the first storage cluster and the first storage volume in the second storage cluster for which the third association relationship has been established, wherein the second data synchronization mechanism includes: When the data in any one of the second storage volume and the first storage volume for which the third association relationship has been established is updated, the data in the other storage volume is updated after a preset time period.

17. A storage space management device, characterized in that, Includes: A disk classification module, configured to classify multiple disks of the same storage cluster according to a preset policy to obtain multiple logical pools, wherein at least two of the disks are included in one logical pool; A storage volume creation module, configured to create a first storage volume of the first type in a target logical pool among the multiple logical pools when the type of the storage volume to be created is the first type, wherein the data included in the first storage volume is distributed and stored in multiple disks of the target logical pool, and the data of the first type of storage volumes in different logical pools is isolated from each other.

18. An electronic device, characterized in that, Includes: A memory, configured to store a computer program; A processor, configured to implement the steps of the method according to any one of claims 1 to 16 when executing the computer program.

19. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein the computer program implements the steps of the method according to any one of claims 1 to 16 when executed by a processor.

20. A computer program product, comprising a computer program, characterized in that, The computer program implements the steps of the method according to any one of claims 1 to 16 when executed by a processor.

Images