Implementing a redundant array of independent disks (RAID) in which compressed data is stored
By predicting and updating the virtual storage capacity of the RAID array and combining over-configuration technology, the problem that RAID array cannot support compressed data is solved, achieving efficient data storage and performance improvements.
Patent Information
- Application Number
- CN202010164288.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-03-28
- Filing Date
- 2020-03-11
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-03-11
AI Technical Summary
Existing RAID arrays cannot effectively support compressed data, resulting in storage capacity issues and performance delays, especially when data compressibility changes, and conventional methods have difficulty adjusting storage capacity to cope with changes in compressed data.
By predicting the compression ratio of the data and the physical storage capacity of the RAID array, the maximum virtual storage capacity is calculated, and the virtual storage capacity is periodically updated based on the current compression ratio and physical storage capacity, over-configuration is achieved for improved performance and durability.
It effectively supports data compression, avoids performance delays and data loss caused by storage capacity problems, improves the overall capacity and performance of RAID arrays, and ensures stable data storage.
Smart Images

Figure CN111752478B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to data storage systems, and more particularly, to implementing a RAID array that supports data compression. Background Art
[0002] RAID refers to a data storage virtualization technology that combines multiple physical data storage device (e.g., memory) components into one or more logical units. Storing data in these logical units actually involves distributing or "striping" data across different physical data storage components. In doing so, one or more logical units can improve data redundancy and / or overall performance compared to traditional data storage solutions.
[0003] Data is distributed across different physical data storage components in a RAID array using one of several schemes, also referred to as "RAID levels." Each RAID level is typically represented by the word "RAID" followed by a number, such as RAID 0 or RAID 1. Each scheme or RAID level provides a different data distribution layout that balances reliability, availability, performance, and capacity in different ways. For example, RAID levels greater than RAID 0 provide protection against unrecoverable sector read errors as well as entire physical drive failures.
[0004] While RAID arrays have provided many improvements to data storage, they have not previously been able to effectively support compressed data. The compressibility of data varies greatly depending on a variety of factors, including the type of data itself. Each storage drive included in a RAID array, and even the different storage components included therein (e.g., different disks in a hard drive), can also have a significant impact on the compressibility of the data stored thereon. Therefore, the actual amount of compressed data that can be stored in storage will vary significantly.
[0005] These differences in achievable data compression also directly impact the overall capacity of the RAID array, subjecting the RAID array to data overflow situations. While these changes are relatively simple to address in standard data storage schemes by simply adding additional storage components to accommodate any excess data, doing so is more difficult in the context of a RAID array. As a result, conventional RAID arrays are unable to support compressed data. Summary of the invention
[0006] According to one approach, a computer-implemented method for implementing a RAID array includes predicting a compression ratio of data to be stored in the RAID array and calculating a maximum virtual storage capacity of the RAID array using the predicted compression ratio and the physical storage capacity of the RAID array. The maximum virtual storage capacity is used to establish an effective storage capacity of the RAID array. One or more instructions to store compressed data in the RAID array are also sent. In response to the occurrence of a predetermined event, a current compression ratio of the compressed data stored in the RAID array and the physical storage capacity of the RAID array are used to calculate a current virtual storage capacity of the RAID array. In addition, the effective storage capacity of the RAID array is scaled based on the current virtual storage capacity.
[0007] Therefore, this approach can actively monitor the data compression ratio of each storage device level and adjust the virtual capacity of the overall RAID array based on the compression performance of the device level. Desirably, this allows the various approaches included herein to effectively and efficiently implement a RAID array that supports data compression.
[0008] In some practices, in response to detecting a predetermined change in a current compression ratio of compressed data stored in the RAID array, a current virtual storage capacity of the RAID array is calculated using the current compression ratio of the compressed data stored in the RAID array and the physical storage capacity of the RAID array. In other words, the virtual storage capacity of the RAID array is periodically updated during actual use based on changes in the compression ratio of the compressed data stored in the RAID array, thereby improving the operating efficiency of the computer-implemented method.
[0009] Furthermore, in some practices, a percentage of the physical storage capacity of the RAID array is overprovisioned. In other words, a predetermined amount of the physical storage capacity of the RAID array is designated as unavailable and therefore not considered in the process of establishing effective storage capacity. Implementing overprovisioning in such practices can further improve performance. For example, overprovisioning implemented in an SSD can increase durability by distributing the total number of write and / or erase operations over a larger number of blocks and / or pages over time. Overprovisioning of an SSD can further improve performance by providing additional buffer space to manage program / erase (P / E) cycles.
[0010] According to another approach, a computer program product for implementing a RAID array includes a computer-readable storage medium, wherein the computer-readable storage medium implements program instructions. The program instructions are readable and / or executable by a processor to enable the processor to perform the aforementioned method.
[0011] According to yet another approach, a system includes: a processor, and logic integrated with the processor, executable by the processor, or integrated with the processor and executable by the processor. The logic is configured to: perform the aforementioned method in addition to over-allocating a percentage of the physical storage capacity of the RAID array. As mentioned above, implementing over-allocation in such an approach can significantly improve performance. For example, over-allocation implemented in an SSD can increase durability by distributing the total number of write and / or erase operations over a larger number of blocks and / or pages over time. Over-allocation of the SSD can further improve performance by providing additional buffer space to manage program / erase (P / E) cycles.
[0012] Other aspects and embodiments of the present invention will become apparent from the following detailed description, which, when taken in conjunction with the accompanying drawings, illustrate by way of example the principles of the invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Figure 1 It is a network architecture based on a practice.
[0014] Figure 2 is based on a practice that can be Figure 1 A representative hardware environment associated with a server and / or client.
[0015] Figure 3 It is a hierarchical data storage system based on a practice.
[0016] Figure 4 is a partial representation of a data storage system according to an approach.
[0017] Figure 5A is a flow chart of a method according to an approach.
[0018] Figure 5B is a flowchart of a background method according to an approach. DETAILED DESCRIPTION
[0019] The following description is made to illustrate the general principles of the invention and is not meant to limit the inventive concepts claimed herein.In addition, the specific features described herein may be used in combination with other described features in each of the various possible combinations and permutations.
[0020] Unless expressly defined otherwise herein, all terms should be given their broadest possible interpretation, including the meaning implicit from the specification and the meaning understood by those skilled in the art and / or the meaning as defined in dictionaries, papers, etc.
[0021] It must also be noted that the singular forms "a", "an" and "the" used in the specification and the appended claims include plural referents unless otherwise specified. It will also be understood that the terms "comprises" and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.
[0022] The following description discloses several preferred practices for effectively and efficiently implementing systems, methods, and computer program products for RAID arrays supporting data compression. Thus, some practices included herein can store compressed data in a RAID array without suffering performance delays and / or data loss caused, for example, by storage capacity issues, for example, as will be described in more detail below.
[0023] In one common approach, a computer-implemented method for implementing a RAID array includes predicting a compression ratio of data to be stored in the RAID array and calculating a maximum virtual storage capacity of the RAID array using the predicted compression ratio and the physical storage capacity of the RAID array. The maximum virtual storage capacity is used to establish an effective storage capacity of the RAID array. One or more instructions to store compressed data in the RAID array are also sent. In response to the occurrence of a predetermined event, the current compression ratio of the compressed data stored in the RAID array and the physical storage capacity of the RAID array are used to calculate the current virtual storage capacity of the RAID array. In addition, the effective storage capacity of the RAID array is scaled based on the current virtual storage capacity.
[0024] In another general approach, a computer program product for implementing a RAID array includes a computer-readable storage medium, wherein the computer-readable storage medium implements program instructions. The program instructions are readable and / or executable by a processor to enable the processor to perform the aforementioned method.
[0025] In yet another general approach, a system includes: a processor, and logic integrated with the processor, executable by the processor, or integrated with the processor and executable by the processor. The logic is configured to: predict, by the processor, a compression ratio of data to be stored in a RAID array; and calculate, by the processor, a maximum virtual storage capacity of the RAID array using the predicted compression ratio and the physical storage capacity of the RAID array. The processor over-allocates a percentage of the physical storage capacity of the RAID array, and the processor establishes an effective storage capacity of the RAID array using the maximum virtual storage capacity. The processor also sends one or more instructions to store compressed data in the RAID array. In response to the occurrence of a predetermined event, the processor calculates the current virtual storage capacity of the RAID array using the current compression ratio of the compressed data stored in the RAID array and the physical storage capacity of the RAID array. In addition, the processor scales the effective storage capacity of the RAID array based on the current virtual storage capacity.
[0026] Figure 1 1 illustrates an architecture 100 according to one approach. Figure 1 As shown, a plurality of remote networks 102 are provided, including a first remote network 104 and a second remote network 106. A gateway 101 may be coupled between the remote network 102 and a neighboring network 108. In the context of the present architecture 100, the networks 104, 106 may each take any form, including but not limited to a local area network (LAN), a wide area network (WAN) such as the Internet, a public switched telephone network (PSTN), an internal telephone network, and the like.
[0027] In use, gateway 101 serves as an entry point from remote network 102 to adjacent network 108. As such, gateway 101 may function as both a router capable of directing a given data packet arriving at gateway 101, as well as a switch providing the actual path in and out of gateway 101 for a given packet.
[0028] Also included is at least one data server 114 coupled to the adjacent network 108, and the data server 114 can be accessed from the remote network 102 via the gateway 101. It should be noted that (one or more) data servers 114 can include any type of computing device / component. Coupled to each data server 114 are multiple user devices 116. The user devices 116 can also be directly connected through one of the networks 104, 106, 108. Such user devices 116 can include desktop computers, laptop computers, handheld computers, printers, or any other type of logic. It should be noted that in one approach, the user device 111 can also be directly coupled to any network.
[0029] A peripheral device 120 or a series of peripheral devices 120 (e.g., a fax machine, a printer, a networked and / or local storage unit or system, etc.) may be coupled to one or more of the networks 104, 106, 108. It should be noted that the database and / or additional components may be used with or integrated into any type of network element coupled to the networks 104, 106, 108. In the context of this description, a network element may refer to any component of a network.
[0030] According to some practices, the development and systems described herein may be implemented with and / or on a virtual system and / or a virtual system that simulates one or more other systems (such as a UNIX system that simulates an IBM z / OS environment, a UNIX system that virtually hosts a MICROSOFT WINDOWS environment, a MICROSOFT WINDOWS system that simulates an IBM z / OS environment, etc.) In some practices, such virtualization and / or simulation may be enhanced by using VMWARE software.
[0031] In further practice, one or more networks 104, 106, 108 may represent a cluster of systems often referred to as a "cloud." In cloud computing, shared resources (such as processing power, peripherals, software, data, servers, etc.) are provided to any system in the cloud on an on-demand basis, allowing services to be accessed and distributed across many computing systems. Cloud computing typically involves Internet connections between systems running in the cloud, but other technologies for connecting systems may also be used.
[0032] Figure 2 shows that according to one approach Figure 1 1 and 12. The diagram illustrates a representative hardware environment associated with a user device 116 and / or server 114. The diagram illustrates a typical hardware configuration of a workstation having a central processing unit 210 (such as a microprocessor) and a number of other units interconnected via a system bus 212.
[0033] Figure 2 The workstation shown in the figure includes random access memory (RAM) 214, read only memory (ROM) 216, an input / output (I / O) adapter 218 for connecting peripheral devices such as a disk storage unit 220 to the bus 212, a user interface adapter 222 for connecting a keyboard 224, a mouse 226, a speaker 228, a microphone 232 and / or other user interface devices (such as a touch screen and a digital camera (not shown)) to the bus 212, a communications adapter 234 for connecting the workstation to a communications network 235 (e.g., a data processing network), and a display adapter 236 for connecting the bus 212 to a display device 238.
[0034] The workstation may have an operating system resident on it, such as Microsoft Operating system (OS), MAC OS, UNIX OS, etc. It will be appreciated that the preferred practices may also be implemented on platforms and operating systems other than those mentioned. The preferred practices may be written using Extensible Markup Language (XML), C and / or C++ languages or other programming languages and object-oriented programming methods. Object-oriented programming (OOP) may be used, which has been increasingly used to develop complex applications.
[0035] Reference now Figure 3 , shows a storage system 300 according to one approach. Note that according to various approaches, Figure 3 Some of the elements shown in the figure may be implemented as hardware and / or software. The storage system 300 may include a storage system manager 312 for communicating with multiple media and / or drives on at least one higher storage layer 302 and at least one lower storage layer 306. The (one or more) higher storage layers 302 preferably include one or more random access and / or direct access media 304, such as hard disks in hard disk drives (HDDs), non-volatile memory (NVM), solid state memory in solid state drives (SSDs), flash memory, SSD arrays, flash memory arrays, etc., and / or other drives described herein or known in the art. The (one or more) lower storage layers 306 may preferably include one or more lower performance storage media 308, including sequential access media (such as tapes in tape drives) and / or optical media, slower access HDDs, slower access SSDs, etc.; and / or other media described herein or known in the art. One or more additional storage layers 316 may include any combination of storage media desired by the designer of the system 300. Furthermore, any of the upper storage tier 302 and / or the lower storage tier 306 may include some combination of storage devices and / or storage media.
[0036] Storage system manager 312 can access the network 310 (such as Figure 3The storage system manager 312 may communicate with the drives and / or storage media 304, 308 on the upper storage tier(s) 302 and the lower storage tier(s) 306 using a storage area network (SAN) as shown or some other suitable network type. The storage system manager 312 may also communicate with one or more host systems (not shown) through a host interface 314, which may or may not be a part of the storage system manager 312. The storage system manager 312 and / or any other components of the storage system 300 may be implemented in hardware and / or software and may utilize a processor (not shown) to execute commands of a type known in the art, such as a central processing unit (CPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc. Of course, any arrangement of storage systems may be used, as will be apparent to one skilled in the art after reading this description.
[0037] In more practices, the storage system 300 may include any number of data storage tiers, and may include the same or different storage media within each storage tier. For example, each data storage tier may include the same type of storage memory media, such as HDD, SSD, sequential access media (tapes in a tape drive, optical discs in an optical disc drive, etc.), direct access media (CD-ROM, DVD-ROM, etc.), or any combination of media storage types. In one such configuration, the higher storage tier 302 may include the majority of SSD storage media for storing data in a higher performance storage environment, and the remaining storage tiers including the lower storage tier 306 and the additional storage tier 316 may include any combination of SSD, HDD, tape drives, etc. for storing data in a lower performance storage environment. In this way, more frequently accessed data, data with a higher priority, data that needs to be accessed faster, etc. can be stored in the higher storage tier 302, while data that does not have one of these attributes can be stored in the additional storage tier 302, including the lower storage tier 306. Of course, according to the approach given in this article, those skilled in the art can design many other combinations of storage medium types to implement different storage solutions after reading this description.
[0038] According to some practices, a storage system such as 300 may include logic configured to receive a request to open a data set, logic configured to determine whether the requested data set is stored in multiple associated parts in a lower storage tier 306 of the tiered data storage system 300, logic configured to move each associated part of the requested data set to a higher storage tier 302 of the tiered data storage system 300, and logic configured to assemble the requested data set from the associated parts onto the higher storage tier 302 of the tiered data storage system 300.
[0039] Of course, according to various practices, this logic may be implemented as a method on any device and / or system or as a computer program product.
[0040] As mentioned previously, while RAID arrays offer many improvements to data storage, they still cannot effectively support compressed data. Again, the compressibility of data varies greatly depending on many factors, including the type of data itself. Each of the storage drives included in a RAID array, and even the different storage components included therein (e.g., different disks in a hard drive), can also have a significant impact on the compressibility of the data stored thereon. Therefore, the actual amount of compressed data that can be stored in a given portion of storage will vary greatly.
[0041] These differences in achievable data compression also directly impact the overall capacity of the RAID array, subjecting the RAID array to data overflow situations. This is particularly problematic in situations where compressed data already stored in the RAID array is modified and rewritten using a different compression ratio. Again, conventional RAID arrays are thus unable to support compressed data.
[0042] In stark contrast to the aforementioned problems experienced by conventional products, various approaches included herein are capable of effectively and efficiently implementing a RAID array that supports data compression. Thus, some of the approaches included herein are capable of storing compressed data in a RAID array without experiencing performance delays and / or data loss caused by storage capacity issues, for example, as will be described in more detail below.
[0043] Again, RAID arrays typically include multiple (e.g., more than one) different physical storage devices organized into a logical array. Thus, different schemes are used to stripe and / or mirror data across different physical storage devices in the logical array. With respect to data storage in a given RAID array, each of these schemes provides different benefits. For example, data stored in a RAID-0 configuration is striped between storage devices, but data mirroring and parity data are not implemented. Thus, applying this scheme improves data processing speed by utilizing various storage devices, but does not address data retention. According to another example, a RAID-1 configuration implements data mirroring, which improves data access speed by utilizing more than one storage device, while also providing some data retention, but introducing some write latency in order to maintain data mirroring.
[0044] In yet other examples, some RAID configurations (e.g., RAID-5, RAID-6, etc.) involve striping data across all storage devices in the array in addition to reserving one or more cells of each data stripe to store parity data, wherein the parity data corresponds to other data in the stripe. The parity data is thus distributed and / or rotated throughout the array. Therefore, a given update operation (e.g., a new write operation, a modify operation, etc.) has an equal chance of being executed on any storage device in the array. However, any such update operation also results in an update being performed at the storage device having the corresponding parity data.
[0045] Figure 4 A data storage system 400 having a RAID configuration implemented therein according to one approach is depicted. As an option, the present data storage system 400 may be implemented in conjunction with features from any other approach listed herein, such as with reference to other figures (such as Figure 1-3 ) described herein. However, this data storage system 400 and other data storage systems presented herein may be used in a variety of applications and / or permutations that may or may not be specifically described in the illustrative practices listed herein. In addition, the data storage system 400 presented herein may be used in any desired environment. Therefore, Figure 4 (and other figures) may be considered to include any possible permutations.
[0046] As shown, data storage system 400 actually includes storage location 402 connected to network 404. In the present approach, user 406 is also connected to network 404, thereby allowing user 406 to communicate with storage location 402 (e.g., send read requests to it, receive data from it, write data to it, etc.).
[0047] Network 404 can be of any type, for example, depending on the desired practice. For example, in some practices, network 404 is a WAN, such as the Internet, for example. However, an illustrative list of other network types that network 404 can implement includes, but is not limited to, a LAN, a PSTN, a SAN, an internal telephone network, etc. Thus, local storage location 402 is able to communicate with remote users 406 and / or any other entity that can be connected to network 404 regardless of the amount of separation that exists between them, for example, despite being located in different geographical locations.
[0048] The storage location 402 also includes a controller 408 that is coupled to a plurality of different physical storage devices 412. In some implementations, each of the physical storage devices 412 includes the same type of memory. For example, in some implementations, each of the physical storage devices 412 is an HDD. However, in other implementations, the physical storage devices 412 include more than one different type of memory, such as, for example, an HDD, an SSD, a tape, etc. Each of the physical storage devices 412 may also be capable of compressing data before storing the data in the corresponding physical storage device 412. In other words, each of the physical storage devices 412 (e.g., an HDD) may be capable of performing drive-level data compression and / or decompression in some implementations.
[0049] Still reference Figure 4 , the physical storage devices 412 are organized into logical arrays 410. In other words, in some practices, the physical storage devices 412 are collectively interpreted by the controller 408 as a single logical volume of storage. Thus, data stored in the same logical array 410 may actually be stored on different physical storage devices 412. For example, an exemplary RAID stripe 414 is shown as extending across all storage devices 412 in the logical array 410. In other words, the logical array 410 acts as a RAID array that spans more than one of the physical storage devices 412. As mentioned above, the specific RAID configuration implemented also determines how information is actually organized in the RAID stripe 414. For example, in some practices, a portion of the RAID stripe 414 located at the rightmost storage device 412 (indicated by hatching) is reserved for storing parity data that corresponds to the rest of the data stored in the RAID stripe 414.
[0050] Note again that while RAID arrays offer many improvements to data storage, conventional RAID implementations are unable to effectively support compressed data. The compressibility of data varies greatly depending on many factors, including the type of data itself, the storage drives included in the RAID array, and even the different storage components included therein. Therefore, the actual amount of compressed data that can be stored in a given RAID stripe or storage device itself will vary significantly. These differences in achievable data compression also directly impact the overall capacity of the RAID array, subjecting the RAID array to data overflow situations. This is particularly problematic when revising and rewriting compressed data already stored in the RAID array using a compression ratio that is different from the compression ratio achieved when the compressed data was previously written.
[0051] In stark contrast to the aforementioned problems experienced by conventional implementations, various approaches included herein enable effective and efficient implementation of RAID arrays that support data compression. Thus, some of the approaches included herein enable storage of compressed data in a RAID array without experiencing performance delays and / or data loss caused by storage capacity issues. For example, referring now to Figure 5A , shows a flow chart of a method 500 for implementing a RAID array according to one approach. According to the present invention, the method 500 may be Figure 1-Figure 4 Of course, as those skilled in the art will understand after reading this specification, the same Figure 5A More or fewer operations may be included in method 500 than those specifically described in detail.
[0052] Each step of method 500 can be performed by any suitable component of the operating environment. For example, in various practices, method 500 can be performed in part or in whole by a controller, a processor, a computer, etc., or some other device having one or more processors therein. Therefore, in some practices, method 500 can be a computer-implemented method. Moreover, the terms "computer", "processor" and "controller" can be used interchangeably with respect to any practice herein, and such components are considered equivalent in many different permutations of the present invention.
[0053] Moreover, for those practices with a processor, a processor (e.g., processing circuit(s), chip(s), and / or module(s) implemented in hardware and / or software and preferably having at least one hardware component) may be used in any device to perform one or more steps of method 500. Illustrative processors include, but are not limited to, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc., combinations thereof, or any other suitable computing device known in the art.
[0054] like Figure 5A As shown in , operation 502 of method 500 includes predicting a compression ratio for data to be stored in the RAID array. In other words, operation 502 includes predicting the amount of compression that will be achieved for future data that has not yet been stored in the RAID array. According to an illustrative example that is in no way intended to limit the present invention, for data to be stored in the RAID array, a compression ratio of 4:1 is predicted (e.g., assumed).
[0055] The process of predicting the compression ratio of data not yet received can be performed differently and / or based on different types of available information (e.g., depending on the desired approach). For example, in some approaches, the compression ratio is predicted based on the type of storage environment in which the RAID array is implemented and / or the type of data associated with the storage environment. In other approaches, the predicted compression ratio is based on the data compression ratio previously achieved by the same or other RAID arrays. In some approaches, predicting the compression ratio involves checking the compression ratios achieved by each different storage drive (e.g., HDD) in the RAID array and / or the different storage components included in each storage drive (e.g., different disks in the HDD), and identifying the lowest compression ratio. Although this lowest compression ratio translates into a lower overall storage capacity of the RAID array, it also represents the highest compression ratio that all storage drives and storage components included in the RAID array can successfully achieve and maintain, for example, as will be recognized by those skilled in the art after reading this description.
[0056] In still other approaches, the compression ratio is predicted based on a first portion of the data received by the RAID array (e.g., such as a data sample). In some approaches, the process of predicting the compression ratio actually involves using a default compression ratio while also providing an opportunity to adjust it, for example, by a user. The default compression ratio may be predetermined based on industry standards, historical usage data, user preferences, storage capacity standards, etc. Moreover, the default compression ratio may be adjusted based on any of the foregoing information.
[0057] Continue to refer Figure 5A , operation 504 includes calculating the maximum virtual storage capacity of the RAID array using the predicted compression ratio and the physical storage capacity of the RAID array. In a preferred practice, the maximum virtual storage capacity of the RAID array is calculated by multiplying the compression ratio predicted in operation 502 by the physical storage capacity of the RAID array. According to another example, which is also not intended to limit the present invention, a RAID array with a physical storage capacity of 100 gigabytes (GB) and a predicted compression ratio of 4:1 is calculated to have a maximum virtual storage capacity of 400GB. In other words, because the predicted data will be compressed to one-quarter of its original size, the RAID array can effectively store four times the data, for example, assuming that the predicted compression ratio is accurate.
[0058] Operation 506 also includes using the maximum virtual storage capacity to establish the effective storage capacity of the RAID array. The effective storage capacity essentially represents the working capacity of the RAID array, which combines the expected compressibility of the data to be stored therein. Looking at the example given above again, a RAID array with a 100GB physical storage capacity and a 4:1 predicted compression ratio will have a maximum virtual storage capacity of 400GB. Thus, although the physical storage capacity of the RAID array is 100GB, the effective storage capacity of the array can be set to 400GB. Again, because the predicted data will be compressed to a quarter of its original size, the RAID array can effectively store four times the data, for example, assuming that the predicted compression ratio is accurate.
[0059] With respect to the present description, establishing effective storage capacity preferably ensures that the RAID array does not experience data overflow. The process of actually establishing effective storage capacity may only involve logically allocating effective storage capacity to relevant applications in some practices. For example, a storage architecture using thin provisioning allows over-allocation of physical storage capacity based on effective storage capacity. In other practices, effective storage capacity is established by applying it to a storage controller that manages the RAID array. For example, effective storage capacity can be used by a memory management unit located in and / or coupled to a storage controller to set storage limits and appropriately associate logical and physical memory addresses, for example, as will be recognized by those skilled in the art after reading this description.
[0060] In other practices, the effective storage capacity of the RAID array includes over-configuration. Thus, in some practices, operation 506 includes an optional sub-operation of a predetermined percentage of the physical storage capacity of the over-configuration RAID array. In other words, the predetermined amount of the physical storage capacity of the RAID array is designated as unavailable, and is therefore not considered in the process of establishing the effective storage capacity. The mode of realizing over-configuration also depends on the (one or more) specific types of the memory that realizes the RAID array. For example, the over-configuration realized in the SSD can improve durability by distributing the total number of write and / or erase operations across a larger amount of blocks and / or pages over time. The SSD over-configuration can also improve performance by providing additional buffer space to manage program / erase (P / E) cycles. The actual amount of the physical storage capacity of the over-configured RAID array can be predetermined by the user, according to industry standards, based on previous use, etc.
[0061] Continue to refer Figure 5A , operation 508 includes sending one or more instructions to store the compressed data in the RAID array. As mentioned above, one or more of the steps included in method 500 can be performed by any suitable component of the operating environment. Therefore, Figure 5AVarious of the processes included in operation 508 may be performed by a processor (e.g., a controller) that is actually included at a storage location where a RAID array is present, directly coupled to a storage location where a RAID array is present, in communication (e.g., using a network connection) with a storage location where a RAID array is present, etc. Thus, depending on the desired approach, the one or more instructions sent in operation 508 may be sent using different communication channels and / or to different locations. According to exemplary approaches that are in no way intended to limit the present invention, one or more instructions to store compressed data in a RAID array are sent to a storage controller that manages the RAID array and the data stored therein.
[0062] The process of storing compressed data in a RAID array can be implemented in different ways depending on the approach. For example, in some approaches, the data received at the storage location may have been compressed, in which case the compressed data can be simply evaluated (e.g., to determine the compressibility of the data) and stored in the RAID array. In other approaches, the data is compressed after being received at the storage location. For example, drive-level compression is implemented in some approaches to compress the data before storing it in the RAID array. The data retrieved from the RAID array (e.g., read therefrom) can also be decompressed using a drive-level compression component before further use. In fact, drive-level compression can be implemented in some approaches by a dynamic drive compression utility. Moreover, the drive compression utility can automatically operate in the background to avoid any interference with data storage operations.
[0063] Operation 510 includes continuing to monitor the performance of the RAID array and the compressed data stored therein. However, the scope and / or type of the information monitored in operation 510 may vary depending on a given approach. For example, in some approaches, the virtual storage capacity of the RAID array is periodically updated over time, for example, to account for changes in the compression ratio of the data stored in the array. According to a specific example, the virtual storage capacity of the RAID array is updated once per hour. Therefore, operation 510 may include monitoring the amount of time that has passed since making a previous data compression prediction. In other approaches, the unused amount of the effective storage capacity is monitored to maintain an accurate amount of how full the RAID array is.
[0064] In other practices, operation 510 may include monitoring the current compression ratio of the compressed data stored in the RAID array. The current compression ratio provides an accurate representation of the compression ratio actually achieved. Moreover, the current compression ratio may be compared with a previously predicted compression ratio to measure how accurately the prediction represents the condition of the data currently stored in the RAID array. The effective storage capacity of the RAID array may thus be adjusted to compensate for any differences between the predicted data compression ratio and the current compression ratio, for example, as will soon become apparent.
[0065] Proceeding to decision 512, it is determined whether a predetermined amount of time has elapsed since the effective storage capacity of the RAID array was last established and / or updated. As mentioned above, in some practices, the virtual storage capacity of the RAID array is periodically updated over time, for example, to account for changes in the compression ratio of the data stored in the RAID array. The amount of time (e.g., time period) separating each repeated update of the virtual storage capacity can be predetermined by a user, set equal to a default value, predetermined based on the type of storage, the size of the RAID array, the type or RAID scheme implemented, etc.
[0066] In response to determining that a predetermined time has passed since the last time the effective storage capacity of the RAID array was established and / or updated, method 500 directly proceeds to operation 516. There, operation 516 includes using the current compression ratio of the compressed data stored in the RAID array and the physical storage capacity of the RAID array to calculate the current virtual storage capacity of the RAID array. In other words, based on the change in the compression ratio of the compressed data stored in the RAID array, the virtual storage capacity of the RAID array is periodically updated during actual use. The current virtual storage capacity of the RAID array is preferably calculated by multiplying the current compression ratio of the compressed data stored in the RAID array by the physical storage capacity of the RAID array, such as according to any of the above practices. Moreover, in some practices, the current compression ratio is determined by calculating the average data compression ratio for all data currently stored in the RAID array. In other practices, the current compression ratio can be set to be equal to the ratio of the compressibility of a part of the data recently stored in the RAID array, the lowest experienced compression ratio, the highest experienced compression ratio, etc.
[0067] According to an example that is by no means intended to limit the present invention, a RAID array with a physical storage capacity of 200GB and a compression ratio of 4:1 initially predicted will be calculated as an initial maximum virtual storage capacity of 800GB. In other words, because the predicted data will be compressed to a quarter of its original size, the RAID array is effectively able to store four times the data. However, over time, the compression ratio of the data stored in the RAID array may be reduced so that when sampled at a certain time after the predicted initial compression ratio, the compression ratio of the data stored in the RAID array is 3:1. Therefore, the maximum virtual storage capacity of the RAID array has been reduced from 800GB to 600GB, thereby having a similar impact on the effective storage capacity of the RAID array. If this significant reduction in effective storage capacity is not taken into account, an undesirable data overflow event experienced by the RAID array may result.
[0068] However, it should also be noted that the virtual storage capacity of the RAID array can be updated in response to the occurrence of one or more predetermined events other than the predetermined amount of time. Returning to decision 512, method 500 advances to decision 514 in response to determining that the effective storage capacity of the RAID array has not passed the predetermined amount of time since the RAID array is established. There, decision 514 includes determining whether the compressibility of the data stored in the RAID array has changed by a predetermined amount. In other words, decision 514 includes determining whether the difference between the current compression ratio of the compressed data stored in the RAID array and the previous compression ratio is within a predetermined range. In some practices, the current compression ratio is compared with the compression ratio determined most recently. For example, in some practices, the compression ratio of the data stored in the RAID array (e.g., sampling) is determined based on repetition. Therefore, the current compression ratio is compared with the data compression ratio of the previous sampling. In other practices, the current compression ratio is compared with the compression ratio initially predicted in operation 502.
[0069] According to illustrative practices that are in no way intended to limit the present invention, the predetermined range is a difference of at least 10%, more preferably at least 20%, between the current compression ratio and the previous compression ratio of the compressed data stored in the RAID array. Moreover, in some practices, the amount of time that separates the event that determines the current compression ratio from the event that determines the previous compression ratio is a factor in the determination made in decision 514. This time separation amount may even affect the predetermined range. For example, a shorter time separation amount may cause an increase in sensitivity by lowering the threshold percentage (e.g., at least a 10% difference), while a longer time separation amount may cause a decrease in sensitivity by raising the threshold percentage (e.g., at least a 20% difference).
[0070] However, the predetermined range may be set by the user based on the physical storage capacity of the RAID array, based on industry standards, etc. It should also be noted that "within a certain range" is in no way intended to limit the present invention. Rather than determining whether a value is within a given range, an equivalent determination may be made, for example, as to whether a value is above a threshold, whether a value is outside a predetermined range, whether an absolute value is above a threshold, whether a value is below a threshold, etc., depending on the desired practice.
[0071] Still reference Figure 5A , the flowchart returns to operation 510 in response to determining that the compressibility of the data stored in the RAID array has not changed by a predetermined amount. In other words, method 500 continues to monitor the performance of the RAID array and the compressed data stored therein in response to determining that there is no current performance problem. Although decisions 512 and 514 involve checking the periodic update and compression ratio of the data stored in the RAID array, respectively, additional performance characteristics, settings, status information, etc. may be evaluated when determining whether the virtual storage capacity of the RAID array is to be updated, for example, as will be recognized by those skilled in the art after reading this description.
[0072] However, returning to decision 514, the flowchart does advance to operation 516 in response to determining that the compressibility of the data stored in the RAID array has changed by a predetermined amount. As mentioned above, operation 516 includes calculating the current virtual storage capacity of the RAID array using the current compression ratio of the compressed data stored in the RAID array and the physical storage capacity of the RAID array. Moreover, the current virtual storage capacity of the RAID array is preferably calculated by multiplying the current compression ratio of the compressed data stored in the RAID array by the physical storage capacity of the RAID array, for example, according to any of the approaches described above.
[0073] Operation 518 also includes scaling the effective storage capacity of the RAID array based on the current virtual storage capacity. In other words, the effective storage capacity of the RAID array is updated so that it accurately reflects the current virtual storage capacity. As mentioned above, the situation where the maximum virtual storage capacity of the RAID array, for example, drops from 800GB to 600GB has a similar impact on the effective storage capacity of the RAID array. If this significant reduction in effective storage capacity is not considered, it is likely to cause the RAID array to experience an unexpected data overflow event. Thus, operation 518 is expected to ensure that an accurate representation of the used and unused portions of the RAID array is maintained.
[0074] From operation 518, method 500 returns to operation 510. Again, this allows method 500 to continue monitoring the performance of the RAID array and the compressed data stored therein. Thus, the steps included in Figure 5AOne or more processes in the flowchart of to maintain the performance of the RAID array during continued use. Figure 5A Not shown, but method 500 may end in response to a power failure on a storage device where the RAID array resides, receiving a termination command, completing a predetermined number of performance cycles, expiring a predetermined time, etc.
[0075] Although method 500 is able to successfully implement and maintain operation of a RAID array, circumstances may arise in which the amount of compressed data stored in the RAID array becomes abnormally high, particularly with respect to the effective storage capacity of the RAID array. For example, over time, the cumulative amount of data received at the RAID array may approach the physical storage capacity limits of the storage device on which the RAID array resides. In order to avoid data overflow situations due to such circumstances, it is preferred that a running capacity management procedure be performed in the background of ongoing RAID array operations. For example, referring now to Figure 5B , shows a flow chart of a method 550 for implementing a running capacity management procedure for a RAID array according to one approach. According to the present invention, in various approaches, the method 550 may be particularly Figure 1-5A For example, you can execute in any environment depicted in Figure 5A The method 550 of the background execution of the RAID array operation in the method 500. Of course, as those skilled in the art will understand after reading this description, Figure 5B More or fewer operations may be included in method 550 than those specifically described in .
[0076] Each step of method 550 can be performed by any suitable component of the operating environment. For example, in various practices, method 550 can be performed in part or in whole by a controller, a processor, a computer, etc., or some other device having one or more processors therein. Therefore, in some practices, method 550 can be a computer-implemented practice. Moreover, the terms "computer", "processor" and "controller" can be used interchangeably with respect to any practice herein, and such components are considered equivalent in many different permutations of the present invention.
[0077] Moreover, for those practices with a processor, a processor (e.g., processing circuit(s), chip(s), and / or module(s) implemented in hardware and / or software and preferably having at least one hardware component) may be used in any device to perform one or more steps of method 550. Illustrative processors include, but are not limited to, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc., combinations thereof, or any other suitable computing device known in the art.
[0078] like Figure 5B As shown in, the operation 552 of method 550 includes monitoring the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array. In some practices, the effective storage capacity established in the operation 506 of method 500 can be monitored.
[0079] Again, method 550 is preferably performed in the background, so that desired information can be obtained from the ongoing process. In other practices, the effective storage capacity of the RAID array is monitored by checking one or more active (e.g., running) applications and their corresponding logical allocations. In other practices, the effective storage capacity of the RAID array is monitored by querying the storage controller that manages the RAID array. In some practices, operation 552 also involves determining whether over-allocation has been applied to the effective storage capacity of the RAID array.
[0080] Similarly, in some implementations, the amount of compressed data currently stored in the RAID array is monitored by checking the physical storage device. In other implementations, the amount of compressed data currently stored in the RAID array can be monitored by querying a storage controller that manages the RAID array, accessing an I / O module, checking network traffic received by the physical storage device, etc., for example, as will be recognized by those skilled in the art after reading this description.
[0081] Still reference Figure 5B , decision 554 includes determining whether the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array is within a first predetermined range. According to an illustrative approach that is in no way intended to limit the present invention, the first predetermined range is approximately 20% to approximately 10% of the effective storage capacity of the RAID array. In other words, the difference between the effective storage capacity of the RAID array equal to approximately 20% to approximately 10% of the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array is within the first predetermined range. Therefore, decision 554 includes determining whether the RAID array is at risk of experiencing a data overflow event.
[0082] The first predetermined range may be set by the user based on the physical storage capacity of the RAID array, based on industry standards, etc. It should also be noted that "within the first predetermined range" is in no way intended to limit the present invention. Rather than determining whether a value is within a given range, an equivalent determination may be made, for example, as to whether a value is above a threshold, whether a value is outside a predetermined range, whether an absolute value is above a threshold, whether a value is below a threshold, etc., depending on the desired practice. The first predetermined range may also be expressed differently depending on the desired practice, for example, such as a ratio, a unitless fraction, a measurable amount of storage capacity (such as a specific number of GB), etc.
[0083] In response to determining that the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array is not within the first predetermined range, method 550 returns to operation 552 so that the effective storage capacity of the RAID array and / or the amount of compressed data currently stored in the RAID array continues to be monitored. However, in response to determining that the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array is within the first predetermined range, method 550 proceeds to decision 556. There, decision 556 includes determining whether the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array is within a second predetermined range.
[0084] The second predetermined range preferably represents a situation where the effective storage capacity of the RAID array is more strained than the situation corresponding to the first predetermined range. For example, in some practices, the second predetermined range is between about 10% and about 0% of the effective storage capacity of the RAID array, which is in no way intended to limit the present invention. In other words, the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array, which is equal to between about 10% and about 0%, more preferably between about 5% and about 0%, of the effective storage capacity of the RAID array, is within the second predetermined range. Therefore, decision 556 includes determining whether the RAID array is at an even greater risk of experiencing a data overflow event, for example, as will be recognized by those skilled in the art after reading this description.
[0085] In response to determining that the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array is within a second predetermined range, method 550 advances to operation 558 from judgment 556. There, operation 558 includes sending one or more instructions that at least temporarily stop storing compressed data in the RAID array. According to some practices, one or more instructions are sent to a central storage controller, which can transfer incoming data to a specified storage queue, and the specified storage queue can retain the incoming data for an extended period of time. In other practices, one or more instructions are sent to an I / O module, which stores the incoming data in one or more spare parts of a memory, for example, at least until the RAID array has a sufficient amount of available storage capacity to maintain the accumulated incoming data. However, the incoming data received when the RAID array is effectively offline can be processed in a variety of different ways, for example, depending on the desired practice.
[0086] Operation 560 also includes sending one or more instructions that start to migrate the part of the compressed data currently stored in the RAID array out of the RAID array. In other words, operation 560 includes transferring the compressed data from the RAID array to one or more other storage locations. By migrating the compressed data out of the RAID array, operation 560 can incrementally reduce the amount of the compressed data currently stored in the RAID array, thereby desirably increasing the effective storage capacity of the RAID array and the difference between the amount of the compressed data currently stored in the RAID array. In other words, migrating the compressed data out of the RAID array desirably increases its available storage capacity.
[0087] Depending on the approach, compressed data can be migrated from a RAID array to any number of different storage locations. For example, in some approaches, portions of compressed data are migrated from a RAID array to one or more other RAID arrays with available storage capacity. In other approaches, compressed data is migrated to a queue that can, for example, at least temporarily store compressed data therein. In still other approaches, compressed data can be migrated to memory components in different storage systems that may not be RAID configurations. Moreover, specific data that is migrated from a RAID array can be selected randomly, by a user, according to a predetermined algorithm, using a predetermined order, etc.
[0088] Temporarily return to reference decision 556, it should be noted that method 550 directly advances to operation 560 from decision 556 in response to determining that the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array is not within the second predetermined range. Therefore, operation 558 can only be performed when the effective storage capacity of the RAID array is more serious than the situation involving the first predetermined range. However, the first predetermined range and the second predetermined range are by no means intended to be limiting. For example, in some cases, a single predetermined range can be used to decide whether data migration and / or storage suspension should be implemented.
[0089] Operation 562 also includes applying a predetermined time delay. The time delay is preferably applied so that the data migration operation can sufficiently affect the amount of compressed data stored in the RAID array. Depending on the approach, the time delay may be predetermined by the user, based on industry standards, based on the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array, based on data migration rates, etc.
[0090] Method 550 proceeds to decision 564 from operation 562, and this decision includes determining whether the difference between the effective storage capacity of the RAID array and the updated amount of the compressed data currently stored in the RAID array is within a first predetermined range after a certain amount of time. As mentioned above, the amount of time to perform data migration and other factors (such as data mobility) directly affect how much compressed data is actually removed from the RAID array. Therefore, the determination in decision 564 is performed for the updated amount of the compressed data currently stored in the RAID array. Moreover, any one or more practices described above about performing decision 554 can be applied to decision 564, for example, as those skilled in the art will recognize after reading this description.
[0091] In response to determining that the difference between the effective storage capacity of the RAID array and the updated amount of compressed data currently stored in the RAID array is still within the first predetermined range, method 550 proceeds to decision 566. There, decision 566 includes determining whether the difference between the effective storage capacity of the RAID array and the updated amount of compressed data currently stored in the RAID array is within a second predetermined range. Again, the determination made in decision 566 is performed with respect to the updated amount of compressed data currently stored in the RAID array. Moreover, any one or more of the practices described above with respect to performing decision 556 may be applied to decision 566, for example, as will be recognized by those skilled in the art after reading this description.
[0092] In response to determining that the difference between the effective storage capacity of the RAID array and the updated amount of compressed data currently stored in the RAID array is also still within the second predetermined range, method 550 returns to operation 562. Therefore, before repeating decisions 564 and 566, another predetermined time delay is applied.
[0093] Returning to decision 564, method 550 advances to operation 568 in response to determining that the difference between the effective storage capacity of the RAID array and the updated amount of compressed data currently stored in the RAID array is not within the first predetermined range. There, operation 568 includes sending one or more instructions to stop migration. In other words, operation 568 includes sending one or more instructions that stop the migration of data initiated in operation 560. Moreover, operation 570 includes sending one or more instructions to restore the compressed data to be stored in the RAID array. In other words, the RAID array can return to the nominal operating condition in response to determining that the amount of compressed data currently stored in the RAID array is low enough that it is unlikely to experience a data overflow event. Thus, method 550 returns to operation 552 from operation 570 so that continuous monitoring is performed.
[0094] Returning now to decision 566, method 550 advances to operation 572 in response to determining that the difference between the effective storage capacity of the RAID array and the updated amount of compressed data currently stored in the RAID array is not within the second predetermined range. There, operation 572 includes sending one or more instructions to restore the compressed data stored in the RAID array. Although operation 572 includes storing the compressed data in the RAID array again, it has been determined that the difference between the effective storage capacity of the RAID array and the updated amount of compressed data currently stored in the RAID array is still within the first predetermined range. Thus, although new compressed data is stored in the RAID array, the compressed data continues to migrate out of the RAID array, for example, as those skilled in the art will recognize after reading this description. Similarly, in response to determining that the difference between the effective storage capacity of the RAID array and the updated amount of compressed data currently stored in the RAID array has returned to the first and / or second predetermined ranges, one or more instructions to stop storing compressed data in the RAID array are sent.
[0095] Depending on the desired approach, operation 572 may be performed using a process that is the same, similar, or different than the process used to perform operation 570. From operation 572, the flow chart returns to operation 562 and decisions 564 and 566. Thus, processes 562, 564, 566, 568, 570, and / or 572 may be repeated any number of times until the difference between the effective storage capacity of the RAID array and the amount of compressed data currently stored in the RAID array is not within the first predetermined range and is not within the second predetermined range.
[0096] Therefore, various practices included herein can actively monitor the data compression ratio of each storage device level and adjust the virtual capacity of the overall logical array (e.g., RAID array) based on the compression performance of the device level. Desirably, this allows various practices included herein to effectively and efficiently implement a RAID array that supports data compression.
[0097] In addition, these achievements also allow storage systems to experience improved data redundancy and overall performance compared to traditional data storage schemes. For example, these improvements are advantageously achieved without experiencing performance delays and / or data loss caused by storage capacity issues, such as experienced by conventional implementations. As previously mentioned, while RAID arrays have made many improvements to data storage, they have not previously been able to effectively support compressed data.
[0098] The present invention may be a system, a method and / or a computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions for causing a processor to implement various aspects of the present invention.
[0099] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the above. More specific examples of computer-readable storage media (a non-exhaustive list) include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination of the above. The computer-readable storage medium used herein is not to be interpreted as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through a wire.
[0100] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.
[0101] The computer program instructions for performing the operation of the present invention may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages, such as Smalltalk, C++, etc., and procedural programming languages, such as "C" language or similar programming languages. Computer-readable program instructions may be executed entirely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be customized by utilizing the state information of the computer-readable program instructions, and the electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present invention.
[0102] Various aspects of the present invention are described herein with reference to the flow charts and / or block diagrams of the methods, devices (systems) and computer program products according to embodiments of the present invention. It should be understood that each box of the flow chart and / or block diagram and the combination of each box in the flow chart and / or block diagram can be implemented by computer-readable program instructions.
[0103] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0104] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0105] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple embodiments of the present invention. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of the module, program segment or instruction includes one or more executable instructions for realizing the specified logical function. In some alternative implementations, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or action, or can be implemented with a combination of special hardware and computer instructions.
[0106] Moreover, the system according to various embodiments may include a processor and logic integrated with the processor and / or executable by the processor, the logic being configured to perform one or more process steps described herein. The processor may have any configuration described herein, such as a discrete processor or a processing circuit including many components (such as processing hardware, memory, I / O interface, etc.). "Integrated with..." means that the processor has logic embedded as hardware logic, such as an application-specific integrated circuit (ASIC), FPGA, etc. "Executable by the processor" means that the logic is hardware logic; software logic, such as firmware, part of an operating system, part of an application; etc., or a combination of hardware and software logic that the processor can access and is configured to cause the processor to perform some functions when executed by the processor. As known in the art, the software logic can be stored on local and / or remote memory of any memory type. Any processor known in the art, such as a software processor module and / or a hardware processor, such as an ASIC, FPGA, a central processing unit (CPU), an integrated circuit (IC), a graphics processing unit (GPU), etc., can be used.
[0107] It will be apparent that the various features of the foregoing systems and / or methods may be combined in any manner, resulting in multiple combinations from the description given above.
[0108] It will be further appreciated that embodiments of the present invention may be provided as a service deployed on behalf of a client to provide services on demand.
[0109] Although various embodiments have been described above, it should be understood that they are given by way of example only and not limitation. Therefore, the breadth and scope of the preferred embodiment should not be limited by any of the above exemplary embodiments, but should only be defined in accordance with the appended claims and their equivalents.
Claims
1. A computer-implemented method for implementing a redundant array of independent disks (RAID) having compressed data stored therein, comprising: Predicting the compression ratio of data to be stored in a RAID array; Calculate the maximum virtual storage capacity of the RAID array using the predicted compression ratio and the physical storage capacity of the RAID array; Use the maximum virtual storage capacity to establish the effective storage capacity of the RAID array; sending one or more instructions to store the compressed data in the RAID array; Calculating a current virtual storage capacity of the RAID array using a current compression ratio of compressed data stored in the RAID array and a physical storage capacity of the RAID array in response to an occurrence of a predetermined event, wherein the occurrence of the predetermined event is the passage of a predetermined amount of time or the detection of a predetermined change in the current compression ratio of compressed data stored in the RAID array; as well as Scales the effective storage capacity of the RAID array based on the current virtual storage capacity.
2. The computer-implemented method of claim 1 , comprising: determining whether a difference between an effective storage capacity of the RAID array and an amount of compressed data currently stored in the RAID array is within a first predetermined range; as well as In response to determining that a difference between an effective storage capacity of the RAID array and an amount of compressed data currently stored in the RAID array is within a first predetermined range, sending one or more instructions to initiate migration of a portion of the compressed data currently stored in the RAID array out of the RAID array.
3. The computer-implemented method of claim 2, comprising: determining whether a difference between an effective storage capacity of the RAID array and an updated amount of compressed data currently stored in the RAID array is within a first predetermined range; as well as In response to determining that a difference between an effective storage capacity of the RAID array and an updated amount of compressed data currently stored in the RAID array is not within a first predetermined range, one or more instructions to stop migration are sent.
4. The computer-implemented method of claim 2, comprising: determining whether a difference between an effective storage capacity of the RAID array and an amount of compressed data currently stored in the RAID array is within a second predetermined range; as well as In response to determining that a difference between an effective storage capacity of the RAID array and an amount of compressed data currently stored in the RAID array is within a second predetermined range, sending one or more instructions to stop storing compressed data in the RAID array.
5. The computer-implemented method of claim 4, comprising: determining whether a difference between an effective storage capacity of the RAID array and an updated amount of compressed data currently stored in the RAID array is within a second predetermined range; as well as In response to determining that a difference between an effective storage capacity of the RAID array and an updated amount of compressed data currently stored in the RAID array is not within a second predetermined range, sending one or more instructions to resume storing compressed data in the RAID array.
6. The computer-implemented method of claim 5, comprising: determining whether a difference between an effective storage capacity of the RAID array and an updated amount of compressed data currently stored in the RAID array is within a first predetermined range; as well as In response to determining that a difference between an effective storage capacity of the RAID array and an updated amount of compressed data currently stored in the RAID array is not within a first predetermined range, one or more instructions to stop migration are sent.
7. The computer-implemented method of claim 1, comprising: The percentage by which the physical storage capacity of the RAID array is overprovisioned.
8. The computer implemented method of claim 1, wherein the RAID array spans more than one hard drive.
9. A computer-readable storage medium having program instructions implemented therein, the program instructions being readable and / or executable by a processor to cause the processor to perform the method according to any one of claims 1 to 8.
10. A system for implementing a redundant array of independent disks (RAID) having compressed data stored therein, comprising: processor; as well as Logic, integrated with a processor, executable by a processor, or integrated with a processor and executable by a processor, the logic being configured to perform the method of any one of claims 1 to 8.
11. A computer-implemented apparatus comprising means for performing the method of any one of claims 1 to 8.
Citation Information
Patent Citations
Method and system for maximizing protected data quality in RAID system
CN101047010A
Method and system for realizing disaster recovery utilizing collapsible virtualized capacity
CN102591741A
System expansion method and device of redundant array of independent disks (RAID)
CN103513938A
Controlling data storage in an array of storage devices
CN104123100A
Data replication based on compression ratio history
CN106844090A
