Data storage state display method and device, storage system, and storage medium

Abstract

The application provides a data storage state display method and device, a storage system and a storage medium. The method is applied to a data storage system, the data storage system comprises a first layer and a second layer, the read-write speed of the first layer is higher than that of the second layer, and the method comprises the following steps: obtaining state information of target data corresponding to a plurality of time intervals from a target time, the target data refers to data that is accessed for the last time in the corresponding time interval, and the target data is data stored in the first layer; displaying a target state interface and / or outputting abnormal prompt information according to the state information, the target state interface at least represents the data amount of the target data corresponding to each time interval and the data state of the target data corresponding to each time interval. The scheme can timely show the storage state of the data to the user, and meets the demand of the user for understanding the storage state of the data in some scenes.

Description

Technical Field

[0001] This application relates to the field of data storage technology, and in particular to a method, apparatus, storage system, and storage medium for displaying data storage status. Background Technology

[0002] To balance the needs of storing large amounts of data and enabling fast read / write operations, data storage systems are typically divided into at least two layers, such as a hot layer and a cold layer. The hot layer can be implemented using high-speed storage media (such as flash memory or ultra-fast solid-state drives) to support rapid data reading and writing, while the cold layer can be implemented using lower-speed but higher-capacity storage media (such as hard disk drives or high-speed solid-state drives) to support storing large amounts of data. Based on this layered structure, the data storage system can store large amounts of data in layers according to the user-configured storage strategy.

[0003] After applying the above hierarchical structure, the storage status of data within the system becomes quite complex. The current system is unable to display the storage status of data to users, making it difficult to meet the usage needs in some scenarios. Summary of the Invention

[0004] In view of this, this application provides a method and apparatus for displaying the storage status of data to meet the needs of users to observe the storage status of data in a data storage system.

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] This application provides a method for displaying data storage status, applied to a data storage system, the data storage system including a first layer and a second layer, wherein the read / write rate of the first layer is higher than the read / write rate of the second layer, the method comprising:

[0007] Starting from the target time, obtain the status information of the target data corresponding to multiple past time intervals. The target data refers to the data last accessed within the corresponding time interval, and the target data is the data stored in the first layer.

[0008] Based on the status information, a target status interface is displayed, and / or an exception prompt message is output. The target status interface at least represents the amount of target data corresponding to each time interval and the data status of the target data corresponding to each time interval. The exception prompt message is obtained when it is determined that the target data corresponding to the multiple time intervals meets the exception conditions. The exception prompt message is at least used to guide the target operation that matches the exception conditions.

[0009] Optionally, the target data corresponding to the plurality of time intervals meets the abnormal conditions, including the target data corresponding to the plurality of time intervals meeting at least one of the first abnormal condition, the second abnormal condition, and the third abnormal condition;

[0010] The first abnormal condition includes that, up to the current moment, the number of time intervals corresponding to the target data in the first layer is less than the lower limit of the number;

[0011] The second abnormal condition includes that the proportion of cold layer write-back of the target data is greater than the second threshold. The proportion of cold layer write-back represents the proportion of target data in the cold layer write-back state in all target data. The cold layer write-back state refers to the state of writing from the second layer to the first layer.

[0012] The third abnormal condition includes the presence of abnormal data in the target data, wherein the abnormal data refers to data that was not written from the first layer to the second layer within the specified time period.

[0013] Optionally, the target data includes at least first target data stored based on a first strategy and second target data stored based on a second strategy;

[0014] The method further includes:

[0015] If the first target data in the plurality of time intervals meets the first abnormal condition or the second abnormal condition, and the used capacity of the first layer is greater than or equal to the capacity threshold, the second available capacity corresponding to the pre-allocated second strategy is reduced.

[0016] Wherein, the number of time intervals corresponding to the second target data stored based on the second strategy is greater than the lower limit of the number.

[0017] Optional, also includes:

[0018] After any target data is written to the first layer and a write interval has elapsed, the target data is written to the second layer.

[0019] Optionally, the step of acquiring the status information of the target data corresponding to multiple past time intervals starting from the target time includes at least one of the following:

[0020] Based on the time interval, the status information of the target data corresponding to multiple past time intervals is periodically obtained, starting from the target time.

[0021] In response to the target operation command, starting from the target time, the status information of the target data corresponding to multiple past time intervals is obtained.

[0022] Optional, also includes:

[0023] If the number of first time intervals corresponding to target data contained in the first layer is greater than the upper limit, delete the target data corresponding to the earliest target first time interval from the first layer;

[0024] The upper limit of the quantity is determined based on the duration of the first time interval and the duration of the preset first cycle, and the product of the upper limit of the quantity and the duration of the first time interval is greater than the duration of the first cycle.

[0025] Optionally, the target status interface may also include the available capacity and used capacity of the first layer.

[0026] A second aspect of this application provides a display device for data storage status, applied to a data storage system, the data storage system including a first layer and a second layer, wherein the read / write rate of the first layer is higher than the read / write rate of the second layer, the device comprising:

[0027] The acquisition unit is used to acquire the status information of target data corresponding to multiple past time intervals starting from the target time. The target data refers to the data last accessed within the corresponding time interval, and the target data is the data stored in the first layer.

[0028] The processing unit is configured to display a target status interface and / or output an exception prompt message based on the status information. The target status interface at least represents the amount of target data corresponding to each time interval and the data status of the target data corresponding to each time interval. The exception prompt message is obtained when it is determined that the target data corresponding to the multiple time intervals meets the exception conditions. The exception prompt message is at least used to guide the target operation that matches the exception conditions.

[0029] A third aspect of this application provides a data storage system, comprising:

[0030] Memory used to store computer programs;

[0031] At least one processor for executing the computer program;

[0032] When the processor executes the computer program, it specifically performs the following:

[0033] Starting from the target time, obtain the status information of the target data corresponding to multiple past time intervals. The target data refers to the data last accessed within the corresponding time interval, and the target data is the data stored in the first layer.

[0034] Based on the status information, a target status interface is displayed, and / or an exception prompt message is output. The target status interface at least represents the amount of target data corresponding to each time interval and the data status of the target data corresponding to each time interval. The exception prompt message is obtained when it is determined that the target data corresponding to the multiple time intervals meets the exception conditions. The exception prompt message is at least used to guide the target operation that matches the exception conditions.

[0035] The fourth aspect of this application provides a computer storage medium for storing a computer program, which, when executed by a processor, implements the method for displaying the data storage status provided in any of the first aspects of this application.

[0036] This application provides a method, apparatus, storage system, and storage medium for displaying data storage status, applied to a data storage system. The data storage system includes a first layer and a second layer, where the read / write rate of the first layer is higher than that of the second layer. The method includes: starting from a target time, acquiring status information of target data corresponding to multiple past time intervals, where the target data refers to the data last accessed within the corresponding time interval, and the target data is data stored in the first layer; displaying a target status interface based on the status information, and / or outputting exception prompt information. The target status interface at least represents the data volume and data status of the target data corresponding to each time interval, and the exception prompt information is obtained when the target data corresponding to multiple time intervals meets exception conditions, and the exception prompt information is at least used to guide the target operation matching the exception conditions. This solution can promptly display the storage status of data and / or exception prompt information when exception conditions are met to the user, meeting the user's need to understand the storage status of data in some scenarios. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0038] Figure 1 This application discloses a method for displaying data storage status.

[0039] Figure 2 This is a schematic diagram of a target status interface disclosed in an embodiment of this application;

[0040] Figure 3 This is a schematic diagram of the structure of a data storage status display device disclosed in an embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the structure of a data storage system disclosed in an embodiment of this application. Detailed Implementation

[0042] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0044] Furthermore, in this document, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0045] This embodiment provides a method for displaying data storage status, applied to a data storage system. The data storage system includes a first layer and a second layer, where the read / write rate of the first layer is higher than that of the second layer. Please refer to [link to relevant documentation]. Figure 1 The method may include the following steps.

[0046] The method provided in this embodiment can be executed by a data storage system.

[0047] This data storage system can store data using a hierarchical architecture consisting of a first layer and a second layer. The first layer can have a higher read / write speed and a smaller storage capacity, while the second layer can have a lower read / write speed and a larger storage capacity. In some scenarios, the first layer can also be called the hot layer, and the second layer can also be called the cold layer.

[0048] The hot and cold layers can be implemented using different types of storage devices, and this embodiment does not limit the storage devices used in specific applications. As some examples, the hot layer can be a flash memory device, and the cold layer can be a conventional hard disk drive (HDD) or a solid-state drive (SSD), or a hybrid storage device combining flash memory and hard disk drives; alternatively, the hot layer can be a memory module of an SSD, and the cold layer can be a conventional storage area of ​​an SSD; alternatively, the hot layer can be an ultra-high-speed SSD, such as an SSD combining Triple-Level Cell (TLC) and Quad-Level Cell (QLC), and the cold layer can be a conventional high-speed SSD.

[0049] Before using this data storage system to store data, you can perform the following preparatory steps:

[0050] Configure the source, target, and storage policies of the data storage system, and mount the application to the data storage system.

[0051] The source end can be understood as the file system used to manage the data stored in the first layer (hot layer), and the target end can be understood as the file system used to manage the data stored in the second layer (cold layer).

[0052] A storage strategy may include several parameters related to data storage. In this embodiment, a storage strategy may include at least two parameters: a data retention period and a data tiering period. As an example, a storage strategy may include: a data retention period of 20 days (or 480 hours) and a data tiering period of 5 days (or 120 hours).

[0053] It should be noted that a data storage system can be configured with one or more storage policies, and the parameters contained in different storage policies may not be exactly the same. As an example, a data storage system can be configured with two different storage policies, referred to as Policy 1 and Policy 2, respectively. Policy 1 may include the parameter values ​​mentioned above, while Policy 2 may include: a data retention period of 10 days and a data tiering period of 3 days.

[0054] When configuring multiple storage policies, each storage policy can be pre-allocated the corresponding available capacity in the first tier. The sum of the available capacity of multiple storage policies should be less than or equal to the total available capacity of the first tier.

[0055] Each time a piece of data is stored in the data storage system, it can be managed according to the storage policy corresponding to that data. The available capacity of the storage policy indicates the maximum amount of data corresponding to that storage policy that can be stored in the first tier. For example, if the available capacity of the first policy is 5TB (terabytes), it means that the first tier can store a maximum of 5TB of data corresponding to the first policy.

[0056] The correspondence between storage policies and data can be determined based on the file directory to which the data belongs. Specifically, when configuring a storage policy, you can pre-set which file directories this storage policy applies to. When storing a piece of data in the data storage system, the storage policy applicable to the file directory to which this data belongs is the storage policy corresponding to this data.

[0057] Mounting an application to a data storage system can be understood as establishing a communication connection between the application and the configured file system after configuring the source and target ends. This allows the file system to store the data output by the application according to the corresponding storage strategy. In this embodiment, the application can be any program that provides a series of functions and generates data that needs to be stored. These applications can be deployed on a server or a personal user's terminal, without limitation.

[0058] Data retention period can be understood as the maximum time a piece of data can be stored in the first tier if it remains unaccessed for an extended period, or the length of time the user wants the data to remain in the hot tier. Taking a 20-day data retention period in the first strategy as an example, if a piece of data A corresponding to the first strategy is accessed once on a certain day (denoted as D0), and then remains unaccessed for 20 days, then according to the data retention period of the first strategy, data A can be deleted from the first tier. This allows for the timely cleanup of long-term unused data in the first tier, saving limited storage space.

[0059] The access operations in this embodiment include, but are not limited to, any one or more of writing, querying, modifying, and reading. These access operations can be initiated by any application.

[0060] The data tiering period can be understood as the time a user expects before a piece of data is flushed from the first tier to the second tier, starting from when the data is first written to the first tier. In other words, it's the desired time from when data is written to the first tier to when it's flushed to the second tier. For example, in the first strategy, if a piece of data A corresponding to the first strategy is written to the first tier on a certain day (denoted as D0), then after 5 days, data A should be flushed from the first tier to the second tier.

[0061] In this embodiment, "flash" can refer to the following operation:

[0062] Copy the data to be written in the first layer, and store the copy in the second layer. The original data in the first layer is retained.

[0063] In other words, when a piece of data is written to the second layer, it means that the data is stored in both the first and second layers.

[0064] S101, Starting from the target time, obtain the status information of the target data corresponding to multiple past time intervals. The target data refers to the data last accessed within the corresponding time interval, and the target data is the data stored in the first layer.

[0065] The data storage system (hereinafter referred to as the system) can execute step S101 based on different triggering conditions. For example, the system can execute step S101 every time data is written to the first layer. This embodiment does not limit the specific triggering conditions.

[0066] The time interval can be determined based on the pre-configured data retention period. Generally, the time interval can be 1 / N of the data retention period, where N is a preset positive integer and there is no limitation on the value of N.

[0067] As an example, N can be equal to 4, the data retention period can be 20 days, and the time interval can be 5 days.

[0068] The multiple time intervals in S101 can be of equal or unequal length. For example, each time interval can be 5 days, or some intervals can be 5 days and some can be 1 day. The specific duration can be pre-configured according to the actual situation and is not limited. This corresponds to the data status of the target data.

[0069] Optionally, the system may remain in an idle state for a certain time interval, meaning that no data is written to or read from the system during that time interval. In this case, the amount of data corresponding to that time interval can be 0, and the status information of the target data corresponding to that time interval can be idle, indicating that there is no data corresponding to that time interval.

[0070] The system can start calculating time intervals from the moment it is powered on. Using the example above, assuming the system is powered on on January 1st, the following 5 days, from January 1st to January 5th, can be considered the first time interval, denoted as time interval 0. The 6th to 10th days, from January 6th to January 10th, can be considered the second time interval, denoted as time interval 1, and so on.

[0071] The correspondence between a target data and a time interval can be defined as follows: the last access operation to this target data occurred within this time interval, or the time (equivalent to a timestamp) of the last access operation to this target data is within this time interval.

[0072] Continuing with the previous example, if the last access operation for target data B was writing data B to the first layer on January 2, then target data B corresponds to January 1 to January 5, i.e., time interval 0; if two access operations occurred for target data C, including writing data C to the first layer on January 3 and reading data C from the first layer on January 8, then target data C corresponds to January 6 to January 10, i.e., time interval 1.

[0073] In one embodiment, data is read from the first layer, and the read data remains stored in the first layer. If the data is not modified during reading, it can be read in a conventional manner, involving only data transfer—transferring the data from the first layer to the client, which then accesses the original data from the first layer. If the data is modified during reading, a copy-on-write (COW) mechanism can be used, creating a copy of the original data, and the modifications occur in this copy.

[0074] In this embodiment, the correspondence between target data and time intervals can be recorded in a variety of ways.

[0075] Optionally, the first layer can be divided into multiple partitions according to time intervals, with the target data corresponding to each time interval stored in the corresponding partition. Alternatively, for each piece of target data, the last access timestamp of that target data can be stored, and the corresponding time interval can be determined based on the last access timestamp, which indicates the time when the last access operation occurred.

[0076] Each piece of target data has corresponding status information, which indicates the status of the target data. In this embodiment, a piece of target data can be in any one of three states: unlayered state, read cache state, and cold layer write-back state. Target data in these states can be referred to as unlayered data, read cached data, and cold layer write-back data, respectively.

[0077] The un-tiered state means that the target data is stored in the first tier and not in the second tier.

[0078] Read cache state means that the target data is stored in the first tier and is also stored in the second tier.

[0079] Cold layer write-back state refers to the state where, after the target data is deleted from the first layer, the target data is written back to the first layer from the second layer, which is the state of writing from the second layer to the first layer.

[0080] For any piece of data, after deleting the data from the first layer based on the storage policy corresponding to the data, the system may receive a request to access the data. In this case, the system can search for the data in the second layer. If it is found, the data is written back from the second layer to the first layer to support access operations on the data. At this time, the data is in the cold layer write-back state. In the cold layer write-back state, the data can be stored in both the first and second layers at the same time, or it can be stored only in the first layer.

[0081] In some embodiments, the status information can be obtained by comparing the data in the first layer and the second layer. If the target data is stored only in the first layer and not in the second layer, it is determined to be in an unlayered state. If the target data is stored in both the first and second layers and there is no record of writing the target data from the second layer back to the first layer, it is determined to be in a read cache state. If the target data is stored in both the first and second layers and there is a record of writing the target data from the second layer back to the first layer, it is determined to be in a cold layer write-back state.

[0082] In some embodiments, the status information can be obtained by the system setting a status identifier for each target data. Specifically, when a piece of data provided by the application is written to the first layer for the first time, the status identifier of the data is configured as the identifier corresponding to the unlayered state. When a piece of data is flushed from the first layer to the second layer for the first time, the status identifier of the data is configured as the identifier corresponding to the read cache state. When a piece of data is written from the second layer back to the first layer, the status identifier of the data is configured as the identifier corresponding to the cold layer write-back state. Based on the above identifiers, the status information can be obtained in S101 according to the status identifier corresponding to the target data.

[0083] In other embodiments, the system may also partition and store target data in different states within the first layer to obtain the state information of the target data. This embodiment does not limit the specific method of obtaining the information.

[0084] S102, based on the status information, display the target status interface and / or output abnormal prompt information. The target status interface at least represents the amount of target data corresponding to each time interval and the data status of the target data corresponding to each time interval. The abnormal prompt information is obtained when it is determined that the target data corresponding to multiple time intervals meet the abnormal conditions. The abnormal prompt information is at least used to guide the target operation that matches the abnormal conditions.

[0085] In step S102, if the abnormal conditions are met, the system can display the target status interface and output an abnormal prompt message, or it can output only the abnormal prompt message without displaying the target status interface; if the abnormal conditions are not met, the system can display only the target status interface without outputting an abnormal prompt message.

[0086] In step S102, the system can determine the amount of target data corresponding to each time interval and the amount of target data in different states under each time interval based on the time interval and the status information of each target data, and display the target status interface based on the determined amount of data.

[0087] The target status interface can display the data volume of each dimension in any one or more forms such as bar charts, line charts, pie charts, and tables. This embodiment does not limit the specific display form.

[0088] As an example, the target status interface can be used... Figure 2 The bar chart shown illustrates the data volume for each of the above dimensions.

[0089] Figure 2 The horizontal axis represents different time intervals determined by dates. For example, 1.1 to 1.5 represents January 1 to January 5, and 1.6 to 1.10 represents January 6 to January 10.

[0090] Figure 2 In the chart, the height of the bar for each time interval represents the amount of target data for that time interval. Figure 2 For example, in the current first-tier storage, the target data corresponding to the time interval 1.1~1.5 is a total of 6TB.

[0091] Within each time interval, the different patterned sections and the numbers within those sections in the bar chart represent the amount of target data in different states during that time interval. Figure 2 For example, in the 6TB of data corresponding to the time interval 1.1~1.5, 1TB of data is in the cold layer write-back state, 3TB of data is in the read cache state, and 2TB of data is in the un-layered state.

[0092] It should be noted that the number of time intervals displayed in the target status interface depends on how many time intervals are stored in the first layer. For example, if the current date is February 4th, and the first layer only stores data corresponding to the most recent 4 time intervals, then... Figure 2 The target status interface shown can display only the bar charts corresponding to the four time intervals: 1.16~1.20, 1.21~1.25, 1.26~1.30, and 1.31~2.4.

[0093] In other examples, the amount of data in different states can also be distinguished by different colors or other methods, not limited to... Figure 2 The way to distinguish them.

[0094] It should be noted that since the time interval is determined based on the data retention period, and different storage strategies have different data retention periods, the above target status interface can be the target status interface corresponding to a specific storage strategy, and the target data can be the data stored in the first tier corresponding to that storage strategy.

[0095] When multiple storage policies are configured, the target status interface corresponding to each storage policy can be displayed according to the method of this embodiment, and the multiple target status interfaces corresponding to multiple storage policies can be displayed in a variety of ways.

[0096] Taking the configuration of the first strategy and the second strategy as an example, the target status interface corresponding to the first strategy and the target status interface corresponding to the second strategy can be displayed on the screen simultaneously in a split-screen manner (vertical or horizontal) or can be switched on the screen according to the user's operation, without limitation.

[0097] The beneficial effects of this embodiment are as follows:

[0098] This solution can promptly display the amount of data in different storage states corresponding to different time intervals to the user based on the data status information, and / or output the abnormal prompt information obtained when abnormal conditions are met, thus meeting the user's need to understand the storage status of data in some scenarios.

[0099] In some alternative embodiments, the system may also perform the following steps to manage the target data stored within the first layer.

[0100] If the number of time intervals corresponding to the target data contained in the first layer exceeds the upper limit, delete the target data corresponding to the earliest target time interval from the first layer.

[0101] The maximum quantity can be any positive integer; the specific value can be set as needed without restriction. As an example, the maximum quantity can be equal to 7.

[0102] In this embodiment, if at any time the system finds that the first layer stores data with a time interval exceeding the upper limit (excluding the upper limit itself), the data corresponding to the earliest time interval among the multiple time intervals can be eliminated according to the above method, that is, the data corresponding to the earliest time interval among the multiple time intervals can be deleted from the first layer.

[0103] Taking a maximum quantity of 7 as an example, assume that the first layer currently stores exactly 7 time intervals (referred to as interval 0 to interval 6 in sequence), and the date and data volume corresponding to each time interval are shown in Table 1.

[0104] Table 1

[0105] interval Interval 0 Interval 1 Interval 2 Interval 3 Interval 4 Interval 5 Interval 6 date January 1-5 January 6-10 January 11-15 January 16-20 January 21-25 January 26-30 January 31 - February 4 Data volume 5TB 5TB 5TB 5TB 5TB 5TB 5TB

[0106] At this point, the number of time intervals corresponding to the data in the first layer is equal to the upper limit. If the upper limit is not exceeded, the data does not need to be discarded.

[0107] Suppose that on February 6th, the application writes 0.5TB of data to the first layer. This data will be used as the target data for the 8th time interval, i.e., February 5th to February 9th, in the first layer. The system can determine that the number of time intervals corresponding to the data in the first layer is 8, which exceeds the upper limit. Therefore, the system will discard the data corresponding to the earliest interval 0 in the first layer.

[0108] Using the above method, the system can promptly delete target data that has not been accessed for a long time from the first layer, thereby saving storage space in the first layer and allowing the limited storage space in the first layer to be used primarily for storing data that has been recently accessed and has a high probability of being accessed again.

[0109] Optionally, the upper limit of the quantity is determined based on the duration of the time interval and the preset duration of the first cycle, and the product of the upper limit of the quantity and the duration of the time interval is greater than the duration of the first cycle.

[0110] In other words, the first period is equivalent to the data retention period in the aforementioned embodiment, and the upper limit of the number can be greater than the number of time intervals contained in a data retention period.

[0111] As examples, the duration of the time interval can be 1 / 4 of the duration of the data retention period, that is, the latter is 4 times the former. On this basis, in order to satisfy the condition that the product of the upper limit of quantity and the duration of the time interval is greater than the duration of the first period, the upper limit of quantity can be a positive integer greater than 4, such as 6, 7 or other values.

[0112] The advantage of setting the upper limit for the number of items in the above manner is that, if there is sufficient storage space in the first tier, data accessed over a longer period of time (exceeding the data retention period) can be retained within the first tier, thus making full use of the idle storage space in the first tier. At the same time, by using the additional retention time interval, the actual amount of storage space required to meet the data retention period can be observed, allowing users to configure the available capacity of the storage policy corresponding to the actual required storage space.

[0113] For example, if the data retention period is 4 times the time interval, and the maximum number is set to 7 to retain data for a maximum of 7 time intervals, the user can observe the amount of data corresponding to each of the 4 time intervals (i.e., each data retention period) from the target status interface, and determine the actual storage space required to meet the data retention period based on the amount of data.

[0114] In some alternative embodiments, the system may also flush the target data of the first layer to the second layer in the following manner.

[0115] After any target data is written to the first layer and a flush interval has elapsed, the target data is flushed to the second layer.

[0116] The duration of the write interval is equal to or different from the duration of the time interval in S101.

[0117] For example, the write interval and the time interval in S101 are both 5 days, or the write interval is 3 days and the time interval in S101 is 5 days.

[0118] The flush interval can be determined based on the data tiering period set in the storage policy. For example, the duration of the flush interval can be equal to the duration of the data tiering period, or the duration of the flush interval can be three times the duration of the data tiering period.

[0119] As an example, assuming the refresh interval is 5 days, if a target data A is written to the first tier on January 1, then 5 days after the date of writing to the first tier, that is, on January 6, the target data A should be refreshed to the second tier.

[0120] The system can also use other methods to write the target data of the first layer to the second layer, not limited to the methods mentioned above.

[0121] For example, starting from system startup, within each write interval, the target data written to the first layer in the previous write interval is written to the second layer. That is, no data is written in the first write interval, the data written to the first layer in the first write interval is written in the second write interval, the data written to the first layer in the second write interval is written in the third write interval, and so on. Taking a 5-day write interval as an example, after startup on January 1st, no data is written to the second layer from January 1st to January 5th. From January 6th to January 10th, the data written to the first layer from January 1st to January 5th is written to the second layer. From January 11th to January 15th, the data written to the first layer from January 6th to January 10th is written to the second layer, and so on.

[0122] Alternatively, the system can start from boot and, after N write intervals, write the data written to the first layer in the first N write intervals to the second layer. That is, no data is written in the first to N write intervals, and the data written to the first layer in the first to N write intervals is written in the (N+1) to 2N write intervals, and so on.

[0123] As explained above, data written to the second layer can still be retained in the first layer and is eliminated based on time intervals according to the method described in the previous embodiment.

[0124] By periodically flushing the target data from the first layer to the second layer in the manner described above, the data in the first layer can be backed up to the second layer in a timely manner. In this way, even if the target data in the first layer is removed from the first layer due to long-term inaccessibility, it can still be retrieved from the second layer when needed, thus avoiding data loss.

[0125] In some optional embodiments, the system may also perform the following steps:

[0126] If the target data meets the abnormal conditions, an abnormal prompt message is output. The abnormal prompt message is used to guide the target operation that matches the abnormal conditions.

[0127] In this embodiment, the system can determine whether the target data meets the abnormal conditions based on the status information of the target data and / or the data volume of each dimension counted when displaying the target status interface, and obtain the above-mentioned abnormal prompt information if it is determined that the abnormal conditions are met.

[0128] The abnormal conditions can include one or more. If there are multiple abnormal conditions, as long as at least one abnormal condition is met, the abnormal prompt information can be output in the above manner. If none of the abnormal conditions are met, the system can output a normal prompt information indicating that the storage status is normal, or it can not output a normal prompt information.

[0129] The target operation that matches the abnormal condition can be understood as an operation that can resolve, or at least alleviate, the abnormal condition after execution.

[0130] The system can pre-record each type of abnormal condition and the target operation corresponding to each abnormal condition. When it is determined that the target data meets at least one abnormal condition, the above records can be queried to obtain the target operation that matches the abnormal condition, and then the corresponding abnormal prompt information can be output based on the target operation.

[0131] Optionally, the exception message may also include information describing the exception conditions that are currently met, so that the user can understand the current situation.

[0132] The beneficial effect of this embodiment is that it can output corresponding abnormal prompt information for specific abnormal conditions, so that users can take reasonable actions in a timely manner for the current abnormal conditions, which is conducive to resolving the current abnormality in a timely manner.

[0133] Optionally, the target data meets anomaly conditions, including at least one of the following:

[0134] The first abnormal condition includes that, up to the current moment, the number of time intervals corresponding to the target data in the first layer is less than the lower limit of the number;

[0135] The second abnormal condition includes that the proportion of cold layer write-back of target data is greater than the second threshold. The proportion of cold layer write-back represents the proportion of target data in the cold layer write-back state in all target data. The cold layer write-back state refers to the state of writing from the second layer to the first layer.

[0136] The third abnormal condition includes the presence of abnormal data in the target data. Abnormal data refers to data that was not flushed from the first layer to the second layer within the specified time period.

[0137] In the first abnormal condition, the quantity lower limit can be set according to the relationship between the time interval and the data retention period. Generally, the quantity lower limit can be equal to the multiple of the data retention period relative to the time interval. For example, if the duration of the data retention period is 4 times the duration of the time interval, the quantity lower limit can be equal to 4.

[0138] If the number of time intervals corresponding to the target data is less than the lower limit, it indicates that the target data is retained for a shorter period in the first tier. In particular, if the lower limit is equal to a multiple of the data retention period relative to the time interval, then meeting the first anomaly condition means that the actual retention time of the data in the first tier is less than the data retention period.

[0139] Taking a minimum quantity of 4 as an example, assuming that there are only 3 time intervals corresponding to the target data in the first layer, and the current date is February 4, it means that there are only three time intervals corresponding to the target data in the first layer: January 21 to January 25, January 26 to January 30, and January 31 to February 4. The target data that was last accessed on or before January 20 has been removed from the first layer.

[0140] As can be seen, under the first abnormal condition, only data that has been accessed in a short period of time is retained in the first layer. This may cause the application to take a long time to initiate access operations on the data in the first layer, thus causing the application to be unable to respond to the user's needs in a timely manner.

[0141] The above situation is generally caused by insufficient storage capacity. Therefore, the target operation matched by the first abnormal condition can be to increase the available capacity of the storage policy, or to expand the first tier to increase the overall available capacity of the first tier.

[0142] Furthermore, if the first abnormal condition is met, the output abnormal message may be "The data corresponding to the current storage policy is retained in the hot layer for too short a time. Please increase the available capacity of the current storage policy or expand the hot layer of the system."

[0143] In this embodiment, when the actual retention time of data in the first layer is too short, the system can output corresponding target prompt information to guide the user to increase the available capacity, thereby solving the problem of the actual retention time of data being too short.

[0144] In the second abnormal condition, the total amount of data written back to the cold layer can be counted (regardless of the corresponding time interval). The total amount of data written back to the cold layer is divided by the total amount of target data stored in the first layer, and the result is used as the proportion of cold layer write-back.

[0145] If the proportion of cold layer write-back of target data is greater than the second threshold, it means that a large proportion of the data accessed by each application is provided to the application only after being written back from the second layer to the first layer. This will also cause the application to take a long time to initiate access operations to the data in the first layer, thus causing the application to be unable to respond to the user's needs in a timely manner.

[0146] The above situation is generally caused by a short data retention period. Therefore, the target operation corresponding to the second abnormal condition can be to increase the data retention period in the current storage policy. Correspondingly, if the second abnormal condition is met, the output abnormal message can be "The current data retention period is too short. Please increase the data retention period".

[0147] In this embodiment, when the data retention period is too short to meet the application's usage requirements, the system can guide the user to increase the data retention period through an error message, thereby solving the problem of the data retention period being too short.

[0148] The specified time period in the third abnormal condition can be determined according to the method of writing data to the second layer in the aforementioned embodiments.

[0149] In some embodiments, if it is specified that the target data should be written to the second layer after a certain number of write intervals, starting from the time the target data is written to the first layer, then the specified time interval can be the second write interval after the time the target data is written to the first layer.

[0150] As an example, the write interval can be 5 days. If the target data is written to the first layer on January 1, according to the example above, the target data should be written to the second layer on January 6. Correspondingly, the specified time period can be the second write interval after January 1, that is, from January 6 to January 10.

[0151] If the target data is not written to the second layer within the specified time period, it means that the data in the first layer was not flushed to the second layer (cold layer) in a timely manner. This situation is generally caused by insufficient capacity in the second layer or too low data transmission rate between the first and second layers. It is necessary to check the network connection between the two layers and the capacity usage of the second layer. Therefore, the output error message can be "Data in the hot layer was not flushed to the cold layer in a timely manner. Please check the capacity usage and network connection of the cold layer."

[0152] In this embodiment, when data fails to be written to the cold layer in a timely manner, the system can guide the system to check the capacity usage and network connection status of the cold layer through an error message, thereby solving the problem of untimely data writing.

[0153] Based on the above abnormal conditions, if the number of time intervals corresponding to the target data in the current first layer is greater than or equal to the lower limit, for example, greater than or equal to 4, the proportion of cold layer write-back is less than the second threshold, and the data in the first layer is promptly written to the second layer, then it means that the current target data does not meet the abnormal conditions and there is no need to output abnormal prompt information.

[0154] In some alternative embodiments, the system may also automatically execute the matching target operation based on the currently met abnormal conditions after user confirmation, or it may directly execute the matching target operation after determining that the target data meets the abnormal conditions without user confirmation.

[0155] It should be noted that the above embodiments are all implementation processes of the method in this embodiment under a single storage policy scenario. If the system is configured with multiple storage policies, the above methods can be executed separately for each storage policy to realize the status display and management of the data corresponding to each storage policy.

[0156] Furthermore, when multiple storage policies are configured, if the target data corresponding to any one of the storage policies meets the abnormal conditions, the system can also perform joint processing on multiple storage policies in the following manner.

[0157] The target data includes at least first target data stored based on the first strategy and second target data stored based on the second strategy;

[0158] The method also includes:

[0159] If the first target data meets the first or second anomaly condition in multiple time intervals, and the used capacity of the first layer is greater than or equal to the capacity threshold, the second available capacity corresponding to the pre-allocated second strategy is reduced.

[0160] Among them, the number of time intervals corresponding to the second target data stored based on the second strategy is greater than the lower limit of the number.

[0161] The method in this embodiment can be executed only when capacity squeezing occurs. If the target data corresponding to the first strategy meets the abnormal conditions but capacity squeezing has not occurred, the corresponding abnormal prompt information can be output directly according to the method in the aforementioned embodiment.

[0162] Whether capacity throttling has occurred can be determined based on the used capacity of the first tier. If the used capacity of the first tier is greater than or equal to the capacity threshold, then capacity throttling has occurred; if the used capacity of the first tier is less than the capacity threshold, then capacity throttling has not occurred. The capacity threshold can be equal to the total available capacity of the first tier, or equal to a certain percentage of that available capacity, such as 95% of the available capacity.

[0163] The second strategy can be defined as a storage strategy where the target data does not meet the aforementioned abnormal conditions, or it can be defined as a storage strategy where the target data does not meet the aforementioned first abnormal condition. In other words, if in the first layer, the number of time intervals corresponding to the target data based on a certain storage strategy is greater than the lower limit, then that storage strategy can be determined as the second strategy.

[0164] As an example, assuming the minimum quantity is 4, if there is a storage strategy in the first layer that contains data corresponding to 5 or more time intervals, then that storage strategy can be used as the second strategy if the first strategy meets the abnormal conditions.

[0165] As an example, suppose the system has pre-configured storage policy Y and storage policy X. If on February 4th, the target data corresponding to storage policy Y is found to meet the aforementioned abnormal conditions, and the data stored in the first tier based on storage policy X includes data corresponding to the most recent 6 time intervals, namely, data corresponding to January 6th to 10th, January 11th to 15th, January 16th to 20th, January 21st to 25th, January 26th to 30th, and January 31st to February 4th, then storage policy X can be determined as the second policy, and the available capacity of the policy pre-allocated to storage policy X will be reduced.

[0166] The reduction range can be a preset value or can be set by the user, without limitation.

[0167] Optionally, the system may not directly reduce the second available capacity corresponding to the pre-allocated second strategy, but instead output a reallocation prompt message to prompt the user to perform the operation of reducing the second available capacity corresponding to the pre-allocated second strategy.

[0168] As an example, the reallocation prompt message could be "The available capacity allocated to storage policy X is too large. Please reduce the available capacity of storage policy X," where storage policy X is the second policy determined by the aforementioned method.

[0169] The reallocation prompt message can be output together with the aforementioned exception prompt message, or it can be output before the exception prompt message. The exception prompt message can be output only after the user performs the corresponding operation based on the reallocation prompt message.

[0170] The above embodiments are for the case where two storage policies are configured. When three or more storage policies are configured, the second policy can be any one or more of the three or more storage policies in which the number of time intervals of the corresponding target data is greater than the lower limit.

[0171] For example, there are 3 storage strategies, referred to as strategy 1, strategy 2 and strategy 3 respectively. The target data corresponding to strategy 1 meets the abnormal conditions. Furthermore, the target data corresponding to strategy 2 occupies 7 time intervals, which is greater than the lower limit of 4 for strategy 2. The target data corresponding to strategy 3 also occupies 7 time intervals, which is greater than the lower limit of 4 for strategy 3. Therefore, strategy 2 and strategy 3 can both be used as the second strategy mentioned above, reducing the available capacity corresponding to strategy 2 and strategy 3.

[0172] The minimum quantity for different storage strategies can be the same or different. For example, in the above example, the minimum quantity for strategies 1 to 3 can all be 4, or they can be 4, 5 and 6 respectively, without any limitation.

[0173] Through the methods described in the above embodiments, when capacity crowding occurs, the system can prioritize reducing the available capacity of the second strategy, which retains more data, thereby releasing a portion of the capacity occupied by the second strategy in the first layer, alleviating the capacity crowding problem. Then, abnormal conditions are handled in accordance with the aforementioned method, thereby better alleviating the data storage problem of the first strategy that meets the abnormal conditions.

[0174] Optionally, the target status interface may also include the available capacity and used capacity of the first tier.

[0175] The display method for available and used capacity is not limited. As some examples, it can be displayed by... Figure 2 The available capacity and used capacity are displayed in a specific way.

[0176] The available capacity of the first tier refers to the maximum amount of data that the first tier can store. Figure 2 For example, the available capacity of the first tier is 50TB, meaning that the first tier can store a maximum of 50TB of data.

[0177] Used capacity represents the total amount of data currently stored in the first tier. Figure 2 For example, the used capacity is 42TB, which means that the first tier currently stores a total of 42TB of data.

[0178] By displaying the available and used capacity of the first tier in the target status interface, users can understand the current capacity usage of the first tier and thus expand the capacity in advance before it becomes insufficient.

[0179] Optionally, the triggering conditions for step S101 may include any one or two of the following:

[0180] Based on time intervals, the status information of target data corresponding to multiple past time intervals is periodically obtained, starting from the target time.

[0181] In response to the target operation command, starting from the target time, the status information of the target data corresponding to multiple past time intervals is obtained.

[0182] In the first triggering condition, the system can execute the above method once every time interval, and display the status of the target data corresponding to multiple time intervals starting from the target time through the target status interface.

[0183] For example, if the time interval is 5 days, the system can execute the above method once every 5 days.

[0184] After each execution of the above method, the target status interface can be continuously displayed for the subsequent time interval until another time interval has elapsed, after which the system displays a new target status interface according to the above method.

[0185] This trigger condition allows the system to periodically and automatically display the status of currently stored data to the user.

[0186] In the latter triggering condition, the target operation instruction refers to the operation instruction used to view the data status. As an example, the system can display a virtual button on the screen for viewing the data status. If the user triggers the virtual button, the system receives the target operation instruction and then displays the target status interface as described above.

[0187] Based on this triggering condition, the frequency of the system displaying the target status interface can be reduced, and it can only be displayed when the user needs to view it, thereby reducing the consumption of system processing resources.

[0188] This embodiment also provides a data storage status display device applied to a data storage system. The data storage system includes a first layer and a second layer, wherein the read / write rate of the first layer is higher than that of the second layer. Please refer to [link to relevant documentation]. Figure 3 The device may include:

[0189] The obtaining unit 301 is used to obtain the status information of the target data corresponding to multiple past time intervals starting from the target time. The target data refers to the data that was last accessed within the corresponding time interval, and the target data is the data stored in the first layer.

[0190] The processing unit 302 is used to display a target status interface and / or output an exception prompt message based on the status information. The target status interface at least represents the data volume of the target data corresponding to each time interval and the data status of the target data corresponding to each time interval. The exception prompt message is obtained when it is determined that the target data corresponding to multiple time intervals meets the exception conditions based on the status information and / or the data volume. The exception prompt message is used at least to guide the target operation that matches the exception conditions.

[0191] Optionally, the target data corresponding to multiple time intervals meet the abnormal conditions, including the target data corresponding to multiple time intervals meeting at least one of the first abnormal condition, the second abnormal condition, and the third abnormal condition;

[0192] The first abnormal condition includes that, up to the current moment, the number of time intervals corresponding to the target data in the first layer is less than the lower limit of the number;

[0193] The second abnormal condition includes that the proportion of cold layer write-back of target data is greater than the second threshold. The proportion of cold layer write-back represents the proportion of target data in the cold layer write-back state in all target data. The cold layer write-back state refers to the state of writing from the second layer to the first layer.

[0194] The third abnormal condition includes the presence of abnormal data in the target data. Abnormal data refers to data that was not flushed from the first layer to the second layer within the specified time period.

[0195] Optionally, the target data includes at least first target data stored based on the first strategy and second target data stored based on the second strategy;

[0196] Processing unit 302 is also used for:

[0197] If the first target data meets the first or second anomaly condition in multiple time intervals, and the used capacity of the first layer is greater than or equal to the capacity threshold, the second available capacity corresponding to the pre-allocated second strategy is reduced.

[0198] Among them, the number of time intervals corresponding to the second target data stored based on the second strategy is greater than the lower limit of the number.

[0199] Optionally, the processing unit 302 is also used for:

[0200] After any target data is written to the first layer and a flush interval has elapsed, the target data is flushed to the second layer.

[0201] Optionally, the obtaining unit 301 acquires the status information of the target data corresponding to multiple past time intervals, starting from the target time, including at least one of the following:

[0202] Based on time intervals, the status information of target data corresponding to multiple past time intervals is periodically obtained, starting from the target time.

[0203] In response to the target operation command, starting from the target time, the status information of the target data corresponding to multiple past time intervals is obtained.

[0204] Optionally, the processing unit 302 is also used for:

[0205] If the number of first time intervals corresponding to target data contained in the first layer is greater than the upper limit, the target data corresponding to the earliest target first time interval will be deleted from the first layer.

[0206] The upper limit of the quantity is determined based on the duration of the first time interval and the preset duration of the first cycle, and the product of the upper limit of the quantity and the duration of the first time interval is greater than the duration of the first cycle.

[0207] Optionally, the target status interface may also include the available capacity and used capacity of the first tier.

[0208] The working principle of the above data storage status display device can be found in the relevant steps of the data storage status display method in the foregoing embodiments, and will not be repeated here.

[0209] This embodiment also provides a data storage system; please refer to [link / reference]. Figure 4 ,include:

[0210] Memory 401 for storing computer programs;

[0211] At least one processor 402 for executing computer programs;

[0212] When a processor executes a computer program, it specifically performs the following:

[0213] Starting from the target time, obtain the status information of the target data corresponding to multiple past time intervals. The target data refers to the data that was last accessed within the corresponding time interval, and the target data is the data stored in the first layer.

[0214] Based on the status information, display the target status interface and / or output exception prompt information. The target status interface at least represents the data volume and data status of the target data corresponding to each time interval. The exception prompt information is obtained when it is determined that the target data corresponding to multiple time intervals meets the exception conditions based on the status information and / or data volume. The exception prompt information is at least used to guide the target operation that matches the exception conditions.

[0215] This embodiment also provides a computer storage medium for storing a computer program. When the computer program is executed by a processor, it is used to implement the data storage status display method provided in any embodiment of this application. The working principles of the above system and storage medium can be found in the data storage status display method of the foregoing embodiments, and will not be repeated here.

[0216] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0217] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0218] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for displaying data storage status, characterized in that, Applied to a data storage system, the data storage system comprising a first layer and a second layer, wherein the read / write rate of the first layer is higher than that of the second layer, the method comprises: Starting from the target time, obtain the status information of the target data corresponding to multiple past time intervals. The target data refers to the data last accessed within the corresponding time interval, and the target data is the data stored in the first layer. Based on the status information, a target status interface is displayed, and an exception prompt message is output. The target status interface at least represents the amount of target data corresponding to each time interval and the data status of the target data corresponding to each time interval. The exception prompt message is obtained when it is determined that the target data corresponding to the multiple time intervals meets the exception conditions. The exception prompt message is at least used to guide the target operation that matches the exception conditions. The target data corresponding to the plurality of time intervals meet the abnormal conditions, including the target data corresponding to the plurality of time intervals meeting at least one of the first abnormal condition, the second abnormal condition, and the third abnormal condition; The first abnormal condition includes that, up to the current moment, the number of time intervals corresponding to the target data in the first layer is less than the lower limit of the number; The second abnormal condition includes that the proportion of cold layer write-back of the target data is greater than the second threshold, wherein the proportion of cold layer write-back represents the proportion of target data in the cold layer write-back state in all target data, and the cold layer write-back state refers to the state of writing from the second layer to the first layer. The third abnormal condition includes the presence of abnormal data in the target data, wherein the abnormal data refers to data that was not written from the first layer to the second layer within the specified time period.

2. The method according to claim 1, characterized in that, The target data includes at least first target data stored based on a first strategy and second target data stored based on a second strategy; The method further includes: If the first target data in the plurality of time intervals meets the first abnormal condition or the second abnormal condition, and the used capacity of the first layer is greater than or equal to the capacity threshold, the second available capacity corresponding to the pre-allocated second strategy is reduced. Wherein, the number of time intervals corresponding to the second target data stored based on the second strategy is greater than the lower limit of the number.

3. The method according to claim 1, characterized in that, Also includes: After any target data is written to the first layer and a write interval has elapsed, the target data is written to the second layer.

4. The method according to claim 1, characterized in that, The process of acquiring the status information of target data corresponding to multiple past time intervals starting from the target time includes at least one of the following: Based on the time interval, the status information of the target data corresponding to multiple past time intervals is periodically obtained, starting from the target time. In response to the target operation command, starting from the target time, the status information of the target data corresponding to multiple past time intervals is obtained.

5. The method according to claim 1, characterized in that, Also includes: If the number of first time intervals corresponding to target data contained in the first layer is greater than the upper limit, delete the target data corresponding to the earliest target first time interval from the first layer; The upper limit of the quantity is determined based on the duration of the first time interval and the duration of the preset first cycle, and the product of the upper limit of the quantity and the duration of the first time interval is greater than the duration of the first cycle.

6. The method according to claim 1, characterized in that, The target status interface also includes the available capacity and used capacity of the first layer.

7. A display device for data storage status, characterized in that, An apparatus for use in a data storage system, the data storage system comprising a first layer and a second layer, wherein the read / write rate of the first layer is higher than that of the second layer, the apparatus comprising: The acquisition unit is used to acquire the status information of target data corresponding to multiple past time intervals starting from the target time. The target data refers to the data last accessed within the corresponding time interval, and the target data is the data stored in the first layer. The processing unit is configured to display a target status interface and output an exception prompt message based on the status information. The target status interface at least represents the amount of target data corresponding to each time interval and the data status of the target data corresponding to each time interval. The exception prompt message is obtained when it is determined that the target data corresponding to the multiple time intervals meets the exception conditions. The exception prompt message is at least used to guide the target operation that matches the exception conditions. The target data corresponding to the plurality of time intervals meet the abnormal conditions, including the target data corresponding to the plurality of time intervals meeting at least one of the first abnormal condition, the second abnormal condition, and the third abnormal condition; The first abnormal condition includes that, up to the current moment, the number of time intervals corresponding to the target data in the first layer is less than the lower limit of the number; The second abnormal condition includes that the proportion of cold layer write-back of the target data is greater than the second threshold, wherein the proportion of cold layer write-back represents the proportion of target data in the cold layer write-back state in all target data, and the cold layer write-back state refers to the state of writing from the second layer to the first layer. The third abnormal condition includes the presence of abnormal data in the target data, wherein the abnormal data refers to data that was not written from the first layer to the second layer within the specified time period.

8. A data storage system, characterized in that, include: Memory used to store computer programs; At least one processor for executing the computer program; When the processor executes the computer program, it specifically performs the following: Starting from the target time, obtain the status information of the target data corresponding to multiple past time intervals. The target data refers to the data last accessed within the corresponding time interval, and the target data is the data stored in the first layer. Based on the status information, a target status interface is displayed, and an exception prompt message is output. The target status interface at least represents the amount of target data corresponding to each time interval and the data status of the target data corresponding to each time interval. The exception prompt message is obtained when it is determined that the target data corresponding to the multiple time intervals meets the exception conditions. The exception prompt message is at least used to guide the target operation that matches the exception conditions. The target data corresponding to the plurality of time intervals meet the abnormal conditions, including the target data corresponding to the plurality of time intervals meeting at least one of the first abnormal condition, the second abnormal condition, and the third abnormal condition; The first abnormal condition includes that, up to the current moment, the number of time intervals corresponding to the target data in the first layer is less than the lower limit of the number; The second abnormal condition includes that the proportion of cold layer write-back of the target data is greater than the second threshold, wherein the proportion of cold layer write-back represents the proportion of target data in the cold layer write-back state in all target data, and the cold layer write-back state refers to the state of writing from the second layer to the first layer. The third abnormal condition includes the presence of abnormal data in the target data, wherein the abnormal data refers to data that was not written from the first layer to the second layer within the specified time period.

9. A computer storage medium, characterized in that, Used to store a computer program, which, when executed by a processor, is used to implement the method for displaying the data storage state as described in any one of claims 1 to 6.

Images