WO2013149524A1

WO2013149524A1 - Method and system for writing data

Info

Publication number: WO2013149524A1
Application number: PCT/CN2013/071975
Authority: WO
Inventors: 冯欢
Original assignee: 华为技术有限公司
Priority date: 2012-04-01
Filing date: 2013-02-28
Publication date: 2013-10-10
Also published as: CN102650931B; CN102650931A

Abstract

The embodiments of the present invention provide a method and system for writing data. The method comprises: receiving a command for requesting to write data; determining whether to allocate a compacted pool storage space to all logical addresses to be written into a compacted LUN; if yes, writing the to-be-written data into a storage space allocated by the compacted pool; and if not, determining the length of the data that can be written into continuous logical addresses, to which the compacted pool storage space is not allocated, among the logical addresses and applying, according to an integral multiple of the size of a minimum storage unit that can be provided by a memory, to the compacted pool for the storage space greater than or equal to the length of the data that can be written into the continuous logical addresses; and receiving information of a storage space allocated by the compacted pool in response to the application and writing the to-be-written data into the corresponding storage space. By using the present invention, effective utilization of system resources is achieved.

Description

Method and system for writing data

This application is submitted to the Chinese Patent Office on April 1, 2012, and the application number is

201210095935.3, the priority of the Chinese patent application entitled "Method and System for Writing Data", the entire contents of which are hereby incorporated by reference.

Technical field

The present invention relates to the field of data storage technologies, and more particularly to a method and system for writing data.

Background technique

With the development of technology and the widespread use of the Internet, the amount of data generated by enterprises, governments, and other institutions is increasing. It is imperative to plan storage space for these data as a current storage solution. Often in many storage solutions, thin provisioning is widely used due to its on-demand allocation of storage space management.

The thin provisioning system provided by the prior art includes: a thin pool, a LUN (Logical Unit Number) and a mapping table; wherein, the thin pool is a physical storage space under the thin configuration system, and the allocation granularity is fixed; The LU is a logical hard disk built on the thin pool; the mapping table includes a plurality of mapping tags, which are used to record the physical address of the data stored in the thin pool and the corresponding relationship of the reduced LU logical addresses corresponding to the data. The process of the data being written to the storage by the thin provisioning system is as follows: The command to write data according to the request sent by the host is used to apply for storage space to the thin pool by the integer multiple of the fixed allocation granularity of the thin pool, and the storage space is allocated by the thin pool. The data to be written is written into the storage space allocated by the thin pool. After the data to be written is written into the storage space allocated by the thin pool, the mapping table records the logical address corresponding to the data to be written on the thin LU, and is simplified. The corresponding physical address in the pool to indicate the storage space actually allocated by the data to be written. In the prior art, the size of the storage space that can be recorded by one mapping tag of the mapping table is based on the allocation granularity of the thin pool. Therefore, when the allocation granularity of the thin pool is fixed, only one mapping tag can record one size for the fixed value. Allocating a granular storage space, if the requested storage space is N times the fixed allocation granularity (N is a positive integer greater than 1), then N mapping marks are generated. The thin pool of the existing thin provisioning system allocates storage space with its own fixed allocation granularity, and the demand for the integrated big data service and the small data service is relatively moderate (usually mega-level), so there is waste. The system resource and system resource utilization rate are low. Even if the allocation granularity is too small, multiple mapping tags are used to record the large storage demand service, which causes waste of system memory resources. Summary of the invention

In view of the above, the embodiments of the present invention provide a method and a system for writing data, so as to solve the problem of wasting system resources and system resource utilization caused by the thin provisioning system allocates storage space by using a fixed allocation granularity of the existing thin provisioning system. Low problem.

To achieve the above object, the present invention provides the following technical solutions:

A method of writing data, including:

Receiving a command for requesting to write data, the command for requesting to write data includes data to be written, length of the data to be written, and a logical address of the LUN to be written to the reduced logical unit number;

Determining whether the thin pool storage space is completely allocated to the logical address to be written into the thin LU; if yes, writing the data to be written into the allocated storage space of the thin pool;

If not, determining a length of data that can be written by consecutive logical addresses of the logical address that are not allocated the thin pool storage space, and applying to the thin pool by an integer multiple of a minimum storage unit that the memory can provide Or a storage space equal to the length of the data that can be written by the consecutive logical addresses; receiving the information of the storage space allocated by the thin pool in response to the application, and writing the data to be written into the corresponding storage space.

The invention also provides a system for writing data, comprising:

a receiving module, configured to receive a command for requesting to write data, where the command for writing data includes a data to be written, a length of the data to be written, and a logical address of the LUN to be written into the reduced logical unit number;

a judging module, configured to determine whether to completely allocate the logical address to be written to the thin LU Simple pool storage space;

a determining module, configured to determine, in a case where the determining result of the determining module is negative, a length of data that can be written by consecutive logical addresses of the logical pool that are not allocated the thin pool storage space; Applying, to the thin pool, a storage space greater than or equal to a length of data that can be written by the consecutive logical addresses, in an integer multiple of a minimum storage unit that can be provided by the memory; and storing an information receiving module for receiving the streamlining The pool responds to information about the storage space allocated by the application of the application module;

a writing module, configured to write the to-be-written data into the allocated storage space of the thin pool, or receive the thin pool in the storage information receiving module, if the determination result of the determining module is yes After the allocated storage space information, the data to be written is written into the corresponding storage space.

Based on the foregoing technical solution, the method for writing data provided by the embodiment of the present invention cancels the fixed allocation granularity of the thin pool in the prior art, and applies for storage space to the thin pool by an integer multiple of the minimum storage unit that the memory can provide. Because the storage space of the application is based on the minimum storage unit that the storage can provide, the storage space in the thin pool that is applied can be infinitely close to the storage space required by the data, and the system in the thin pool is avoided. Secondly, the storage space allocated by the thin pool is used as an overall allocation granularity of the thin pool, and is not differentiated by the fixed allocation granularity of the prior art thin pool, so that the logical address to be written into the thin LUN corresponds to the thin pool. The physical address can be recorded in the mapping table in the form of a mapping tag, which saves memory resources. The invention solves the problem that the existing thin provisioning system allocates storage space by using the fixed allocation granularity of the thin pool, and wastes system resources and system resource utilization, thereby realizing effective utilization of system resources. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work. 1 is a flowchart of a method for writing data according to an embodiment of the present invention; FIG. 3 is a structural block diagram of a system for writing data according to an embodiment of the present invention;

4 is a structural block diagram of a determining module according to an embodiment of the present invention;

FIG. 5 is a structural block diagram of a determining module according to an embodiment of the present invention;

FIG. 6 is a structural block diagram of an application module according to an embodiment of the present invention;

FIG. 7 is another structural block diagram of a system for writing data according to an embodiment of the present invention;

FIG. 8 is a hardware architecture diagram of a system for writing data according to an embodiment of the present invention; FIG.

FIG. 9 is another hardware architecture diagram of a system for writing data according to an embodiment of the present invention. detailed description

An embodiment of the present invention provides a method and system for writing data based on a thin provisioning system, dismounting a fixed allocation granularity set in a thin pool, and writing a logical address of an unallocated storage space in a data command according to a request issued by a host. The length of the continuous data is applied to the thin pool by the integer multiple of the minimum storage unit that the memory can provide, so that the resources of the thin provisioning system are effectively utilized.

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without the creative work are all within the scope of the present invention.

FIG. 1 is a flowchart of a method for writing data according to an embodiment of the present invention. Referring to FIG. 1, the method may include:

Step S100: Receive a command to request to write data, where the command to write data includes a data to be written, a length of the data to be written, and a logical address to be written into the reduced logical unit number LUN; requesting to write data The command is issued by the host, and includes data to be written, a length of the data to be written, and a logical address to be written into the thin LUN, where the length of the data to be written is used to represent The storage capacity information to be written to the data, the logical address to be written to the thin LUN is used to indicate the corresponding thin pool physical space that needs to be written to the data to be written. The method of receiving the command for requesting the writing of the data may be the same as the prior art, and is completed by the production volume. The receiving device may also be configured to directly receive the command for requesting the data to be written by the host. The method of receiving data commands is not limited.

Step S200, determining whether the thin pool storage space is completely allocated to the logical address to be written into the reduced LU, and if so, executing step S300, if not, executing step S400;

The situation in which the logical address of the thin LUN to be written is allocated to the thin pool storage space includes three cases: first, the logical address portion of the thin LUN to be written has been allocated a thin pool storage space; second, the to-be-written The logical address of the thin LUN has been allocated to the thin pool storage space. The third logical address of the thin LUN to be written is not allocated the thin pool storage space. If the second case is the case where the determination result is yes, step S300 is performed, and if the first and third cases are the determination result, the process proceeds to step S400.

Step S300, the data to be written is written into the allocated storage space of the thin pool; when the logical address of the thin LUN to be written has been all allocated the thin pool storage space, referring to the prior art processing method, The data to be written is directly written into the allocated storage space.

Step S400: Determine a length of data that can be written by consecutive logical addresses of the logical address that are not allocated the thin pool storage space, and apply for the thin pool to be larger than an integer multiple of a minimum storage unit that can be provided by the memory. Or a storage space equal to the length of the data that the consecutive logical addresses can write;

The memory here can be a disk, a tape or a solid state drive.

The case where the result of the determination in step S200 is NO includes the following two: the logical address of the to-be-written thin LUN is completely unallocated with the thin pool storage space; and the logical address portion of the to-be-written thin LU is allocated the thin pool storage space portion allocation . In practical applications, only one of these two situations will occur. After determining the corresponding situation in the actual application, it is determined that the logical address in the corresponding case is not allocated the thin pool ^^ ^ m ^ i car ^ ό ^ ι & iML , into n ό t— After determining the length of the data that can be written by the consecutive logical addresses, according to the formula: the size of the smallest memory unit that the memory can provide, x N, greater than or equal to the data that can be written by the consecutive logical addresses. Length; obtains an N value, and applies storage space to the thin pool by the size of the smallest storage unit that the N memories can provide.

Preferably, in the case that the storage requirement of the data that can be written by the consecutive logical addresses is satisfied, the storage space of the length of the data that can be written to the continuous logical address is applied to the thin pool.

Preferably, applying for the storage space to the thin pool may be performed by the thin LUN. Specifically, the minimum value of the allocation granularity may be predefined on the thin LU, where the minimum value of the allocation granularity is the minimum storage unit size that the memory can provide. Applying, to the thin pool, a length greater than or equal to the length of data that can be written by the consecutive logical addresses, in an integer multiple of a minimum value of the minimum size of the thin LUN allocation, the size of the storage space of the thin pool of the application The difference between the length of the data to be written is less than a preset threshold.

Currently, the smallest memory unit that a memory can provide is a sector with a size of 512 bytes.

Step S500: The receiving the thin pool responds to the information about the storage space allocated by the application, and writes the data to be written into the corresponding storage space.

After receiving the storage space request, the thin pool allocates the storage space of the same size as the storage space of the application in response to the application, and sends information about the allocated storage space, where the information of the allocated storage space is allocated by the thin pool. Position information and size information of the storage space; after obtaining the information of the allocated storage space, the location and size of the storage space in which the data in the consecutive logical addresses should be written can be obtained from the information. Writing data to be written corresponding to the consecutive logical addresses is written into a corresponding storage space.

The method for writing data shown in FIG. 1 is, after receiving a command requesting to write data, determining whether the thin pool storage space is completely allocated to the logical address of the LU to be written, and if so, directly to be written The data is written into the allocated storage space. If not, it is determined that the logical address is not allocated to the Fi pool, and the address is 0. An integer multiple of a minimum storage unit, applying to the thin pool for a storage space that is greater than or equal to a length of data that can be written by the consecutive logical addresses, and after being obtained by the information of the storage space allocated by the thin pool, is to be written The data is written to the corresponding storage space.

The thin pool of the existing thin provisioning system allocates storage space with its own fixed allocation granularity, and the demand for the integrated big data service and the small data service is relatively moderate (usually mega-level), so there is waste. System resources, low system resource utilization, specific:

(1) The fixed allocation granularity is too large compared to the small data service; since the thin LUN can only apply for storage space with a positive integer multiple of the fixed allocation granularity of the thin pool, then for small data services, such as the bank's depositor database, The minimum storage space (a storage space with a fixed allocation granularity) applied by the thin LUN is also much larger than the data to be written by the host. This causes the storage space allocated by the thin pool to be reasonably utilized, and there is a waste of thin pool storage resources. Case;

(2) For the storage space allocated by the big data service, multiple mapping tags are used for recording; for big data services, such as video libraries, etc., the allocation space of the reduced LU application is multiple of the fixed allocation granularity, and The large storage requirement service is recorded by using multiple mapping tags, which causes waste of system memory resources.

However, the present invention eliminates the fixed allocation granularity of the thin pool in the prior art, and applies the storage space to the thin pool by the integer multiple of the minimum storage unit that the memory can provide, since the applied storage space is the minimum that the storage can provide. The storage unit is based on the storage unit, so that the storage space in the thin pool can be infinitely close to the storage space required by the data, and the waste of system resources in the thin pool is avoided as much as possible. Secondly, the storage space allocated by the thin pool is used as the thin pool. An overall allocation granularity is no longer distinguished by the prior art thin pool fixed allocation granularity, so that the logical address to be written into the thin LU, and the physical address corresponding to the thin pool, can be recorded in the mapping table in the form of a mapping mark. Medium, saving memory resources. The invention solves the problem that the existing thin provisioning system allocates storage space by using the fixed allocation granularity of the thin pool, and wastes system resources and system resource utilization, thereby realizing effective utilization of system resources. In step S200, it is determined whether the thin pool storage space is completely allocated to the logical address of the LU to be written, which can be implemented by detecting the record of the logical address of the LU to be written in the mapping table. The specific method can be as shown in FIG. 2, and the method includes the following steps:

Step S210, detecting a record of the logical address to be written into the thin LUN in the mapping table; Step S220, if the logical address of the to-be-written thin LU is completely recorded in the mapping table, determining that the given The logical address of the to-be-written thin LUN is completely allocated to the thin pool storage space; step S230, if the logical address portion of the to-be-written thin LU is not recorded in the mapping table, it is determined that the to-be-written is not given The logical address of the thin LUN is completely allocated to the thin pool storage space.

The specific method for determining the length of the data that can be written by the consecutive logical addresses of the thin pool storage space in the logical address in step S400 shown in FIG. 1 can be as follows:

For the case where the thin pool storage space is not allocated to the logical address to be written to the thin LUN, that is, the logical address of the to-be-written thin LUN is completely unallocated with the thin pool storage space, the unallocated thin pool storage space is not allocated. The length of the data that can be written by the consecutive logical addresses is the length of the data to be written in the command for writing the requested data;

For the case where the thin pool storage space is not completely allocated to the logical address to be written to the thin LUN, that is, the logical address portion of the thin LUN to be written is allocated the thin pool storage space portion allocation, and the entire data to be written needs to be performed. The splitting may be performed by: splitting a logical address to be written into the reduced LU by using a logical contiguous address corresponding to the allocated storage space, and splitting the logical logic to be written into the thin LUN after the splitting The address includes: a contiguous logical address to which the storage space has been allocated and a contiguous logical address to which the storage space is not allocated, wherein the contiguous logical address to which the storage space has been allocated has a record in the mapping table, and the storage space is not allocated The continuous logical address does not have a record in the mapping table; the length of the data that can be written by the continuous logical address of the unallocated storage space after the split is calculated, and the specific calculation method can refer to the existing data length calculation method, where No more details; the split logical address of the unallocated pool storage space can be written to the data Degree is determined to be

^ ^ ^商旮H ^ I'曰" 1 ^ i car ^ ^ ^ ^ ϋ金 ^ ^ into H For the case where the thin pool storage space is not completely allocated to the logical address to be written to the thin LUN, the logical address of the thin LUN to be written after the split includes: a continuous logical address of the allocated storage space and The contiguous logical address of the storage space is not allocated. Therefore, the step S500 shown in FIG. 1 may be used to write the data corresponding to the consecutive logical addresses of the unallocated storage space, and may also include the storage space allocated by the pool. step:

The data to be written corresponding to the consecutive logical addresses of the allocated storage space is written into the allocated storage space.

Step S500 shown in FIG. 1 may further include the steps:

The logical address to be written into the thin LUN is recorded in the mapping table in the form of a mapping mark corresponding to the physical address corresponding to the thin pool;

Preferably, it can be recorded in the form of a mapping mark.

During the practice of the present invention, the inventors have found that, in the case of the most d, the integer multiple of the storage unit, the memory can apply to the thin pool for greater than or equal to the length of the data that can be written by the consecutive logical addresses. The storage space may be preferably: a storage space that is greater than or equal to the length of data that can be written by the consecutive logical addresses is applied to the thin pool by a power of two of the memory sectors. Such numerical settings are based on a common binary data recording method, so that data can be recorded more conveniently than existing storage, such as a hard disk.

The present invention applies the storage space to the thin pool by an integer multiple of the minimum storage unit that the memory can provide. Compared with the small data service, the present invention can allocate a minimum storage unit that can be provided by a memory to the small data service, thereby Maximize the utilization of storage space. Compared with the existing thin pool mega-level fixed allocation granularity, the present invention can greatly reduce the space wasted by the thin pool in small data services.

The present invention removes the fixed allocation granularity set in the thin pool, and the storage space allocated by the thin pool is no longer segmented by the existing fixed allocation granularity, but the storage space allocated by the thin pool is used as an overall allocation granularity of the thin pool. Allocating a complete storage space, thereby making a mapping in the mapping table of the present invention

The number of mapped tags used avoids wasting system memory resources.

For the method of writing data based on the thin provisioning system shown above, a corresponding system for writing data will be shown below.

3 is a structural block diagram of a system for writing data according to the present invention. Referring to Figure 3, the system can include:

The receiving module 100 is configured to receive a command for requesting to write data, where the command for writing data includes a data to be written, a length of the data to be written, and a logical address of the LUN to be written into the reduced logical unit number;

The determining module 200 is configured to determine whether the thin pool storage space is completely allocated to the logical address of the thin LUN to be written;

a determining module 300, configured to determine, in a case where the determining result of the determining module is negative, a length of the logical address in which the continuous logical address of the thin pool storage space is not allocated;

The application module 400 is configured to apply, to the thin pool, a storage space that is greater than or equal to a length of data that can be written by the consecutive logical addresses, in an integer multiple of a minimum storage unit that can be provided by the storage;

The storage information receiving module 500 is configured to receive information about a storage space allocated by the thin pool in response to the application of the application module;

The writing module 600 is configured to write the to-be-written data into the allocated storage space of the thin pool if the determination result of the determining module is yes, or receive the streamlining in the storage information receiving module After the storage space information allocated by the pool, the data to be written is written into the corresponding storage space.

The structure of the determining module 200 can be as shown in FIG. 4, and includes:

The detecting unit 210 is configured to detect a record of the logical address of the to-be-written thin LUN in the mapping table;

a determining unit 220, configured to detect, in the detecting unit, the logical place to be written into the thin LUN

^ Η^- , give iz ^g into fi TJT ^& ^ Fully allocating the thin pool storage space, or determining that the logic to be written into the thin LU is not given when the detecting unit detects that the logical address portion of the thin LU to be written is not recorded in the mapping table The address is fully allocated to the thin pool storage space.

The structure of the determining module 300 can be as shown in FIG. 5, including:

The first determining unit 310 is configured to determine, when the thin pool storage space is not allocated to the logical address to be written into the thin LUN, the length of the data to be written is determined, where the thin pool storage space is not allocated. The length of data that can be written by consecutive logical addresses;

The splitting unit 320 is configured to allocate a thin pool storage space to the logical address of the to-be-written thin LUN, and use a logical address corresponding to the allocated storage space as a split point for the to-be-written LU The logical address is split;

The second determining unit 330 is configured to determine, according to the length of the split logical address that is not allocated the thin pool storage space, data that can be written into the continuous logical address of the unallocated thin pool storage space. The length of data that can be written.

The write module 600 can also be used to write the consecutive logical addresses of the allocated storage space after the split unit 320 is split, and the corresponding data is written into the allocated storage space.

The structure of the application module 400 can be as shown in FIG. 6, and includes:

a predefined unit 410, configured to pre-define a minimum value of the reduced LU allocation granularity, where a minimum value of the allocated granularity is a size of a minimum storage unit that the memory can provide;

The application unit 420 is configured to apply, to the thin pool, a data that is greater than or equal to the consecutive logical addresses, in a unit of a positive integer multiple of a minimum value of the reduced LUN allocation granularity defined by the predefined unit. The storage space of the length, the difference between the size of the storage space of the thin pool of the application and the length of the data to be written is less than a preset threshold.

FIG. 7 is another structural block diagram of a system for writing data according to an embodiment of the present invention. In conjunction with the systems shown in Figures 3 and 7, the system of Figure 7 further includes:

a mapping table module 700, configured to: write the logical address of the reduced LU to be in a thin pool The software module composition of the system for writing data based on the thin configuration of the present invention is shown above. It should be noted that the system for writing data of the present invention may also exist in hardware form, and several write data of the present invention will be listed below. An embodiment of the hardware form of the system.

FIG. 8 is a hardware architecture diagram of a system for writing data according to an embodiment of the present invention, with reference to FIG. 7 and FIG.

The interface module 100 can exist in the form of interface 01, and the received command to write data is stored in the first database 02;

The first database 02 stores the command to request to write data;

The first processor 03 is a processor that has the built-in function of the determining module 200 and the determining module 300. The first processor 03 extracts a command for receiving the request to write data stored in the first fetch database 02, and determines whether to write the to-be-written. The logical address of the thin LUN is completely allocated to the thin pool storage space. When the judgment result is no, the length of the data that can be written by the continuous logical address of the thin pool storage space is determined in the logical address, which involves When splitting the data, the first processor 03 may store the split data to be written into the first database 02;

The compact LUN 04 has a built-in function of the application module 400, which applies an integer multiple of the minimum storage unit that the memory can provide, to the thin pool, which is greater than or equal to the length of the data that can be written by the consecutive logical addresses. storage;

Thin pool 05 responds to the LUN 04 application, allocates the corresponding storage space, and sends information about the location and size of the allocated storage space;

The function of the storage information receiving module 500 can be built in the form of software in the input device 06, or in the LU-24;

The input device 06 has built-in software for writing the function of the module 600. When it also has software for storing the function of the information receiving module 500, the corresponding data to be written stored in the first database 02 can be directly extracted and written into the thin pool. In the allocated storage space; when the function of the storage information receiving module 500 is set in other hardware devices, such as streamlining LU 04, the allocation of other hardware devices can be obtained by transferring ^ i^ , , ^^- ^ - 0?. ό 4 eyes into the data, will fc into Thin storage space allocated by the pool;

The second database 07 has built-in software for mapping the function of the table module 700, and the second database 07 includes a mapping table composed of a plurality of mapping tags, which can allocate the storage space allocated by the thin pool to the corresponding physical address on the thin pool, and The corresponding logical address on the logical unit LUN is recorded in a mapping table in the form of a mapping mark;

It should be noted that the interface 01 and the first database 02 can be integrated, as in the form of a production volume of the prior art.

Figure 9 is another hardware architecture diagram of the system for writing data according to the present invention, with reference to Figures 7 and 9.

The production volume 012 receives a command sent by the host to write data;

The first processor 03 is a processor with built-in judgment module 200 and determination module 300 function software, and extracts a command for requesting write data from the generated volume 012, and performs corresponding processing;

The LU 04 has built-in software for applying the function of the module 400, software for storing the function of the information receiving module 500, and software for writing the function of the module 600;

Thin pool 05 responds to the LUN 04 application, allocates the corresponding storage space, and sends information about the allocation storage storage;

The second database 07 has a built-in function of the mapping table module 700, and the second database 07 includes a mapping table composed of a plurality of mapping tags.

It should be noted that the hardware architecture diagrams shown in FIG. 8 and FIG. 9 are only preferred manners of the hardware architecture of the present invention, and should not be a limitation on the hardware architecture system of the present invention. Those skilled in the art can fully modify and integrate the software and hardware of the present invention by the technical revelation given by the specific embodiments of the present invention, and the corresponding software principles and hardware components shown. Corresponding software and hardware, it should be noted that the modifications and integrations do not depart from the technical idea of the present invention and are also within the scope of the present invention.

The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments may be referred to each other. for

Simple, see the method section for details.

A person skilled in the art will further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate the hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented directly in hardware, a software module executed by a processor, or a combination of both. Software modules can be placed in random access memory

(RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage known in the art. In the medium.

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments are obvious 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 the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded to the broadest scope of the principles and novel features disclosed herein.

Claims

Rights request

A method for writing data, comprising:

Receiving a command to request to write data, where the command to write data includes a to-be-written data, a length of the data to be written, and a logical address to be written into the reduced logical unit number LUN;

Determining whether the thin pool storage space is completely allocated to the logical address to be written to the thin LU;

If yes, the data to be written is written into the allocated storage space of the thin pool; if not, the length of the data that can be written by the consecutive logical addresses of the reduced pool storage space in the logical address is determined. Applying, to the thin pool, a storage space that is greater than or equal to a length of data that can be written by the consecutive logical addresses, in an integer multiple of a minimum storage unit that the memory can provide;

The receiving thin pool responds to the information about the storage space allocated by the above application, and writes the data to be written into the corresponding storage space.

2. The method according to claim 1, further comprising:

The logical address to be written into the thin LUN is recorded in the mapping table in the form of a mapping mark corresponding to the physical address corresponding to the thin pool.

The method according to claim 2, wherein the determining whether to completely allocate the thin pool storage space to the logical address to be written into the thin LUN comprises:

Detecting a record of the logical address to be written into the reduced LU in the mapping table; if the logical address of the to-be-written thin LUN is completely recorded in the mapping table, determining that the to-be-written is simplified The logical address of the LUN is completely allocated to the thin pool storage space;

If the logical address portion of the to-be-written LU is not recorded in the mapping table, it is determined that the thin pool storage space is not completely allocated to the logical address of the LU to be written.

The method according to claim 1, 2 or 3, wherein the determining, in the logical address, that a continuous logical address of the thin pool storage space is not allocated can write data The length includes:

If the thin pool storage space is not allocated to the logical address to be written into the thin LUN, the length of the data that can be written by the consecutive logical addresses of the unallocated thin pool storage space is the length of the data to be written. ;

If the thin pool storage space is not completely allocated to the logical address to be written into the thin LU, the logical address corresponding to the allocated storage space is used as a split point, and the logical address to be written into the thin LUN is split. Then, the length of the data that can be written by the consecutive logical addresses of the unallocated pool storage space is the length of the data that can be written by the consecutive logical addresses of the split thin pool storage space.

The method according to claim 1, wherein the applying to the thin pool by the integer multiple of a minimum storage unit that can be provided by the memory is greater than or equal to the continuous logical address. The length of storage space includes:

Defining a minimum value of the reduced LU allocation granularity, the minimum of the allocated granularity being a minimum storage unit size that the memory can provide;

Applying, to the thin pool, a storage space that is greater than or equal to a length of data that can be written by the consecutive logical addresses, in units of integer multiples of the minimum value of the thin LUN allocation granularity, the thin pool storage of the application The difference between the size of the space and the length of the data to be written is less than a preset threshold.

6. A system for writing data, comprising:

a receiving module, configured to receive a command for requesting to write data, where the command for writing data includes a data to be written, a length of the data to be written, and a logical address to be written into the reduced logical unit number LU;

a judging module, configured to determine whether the thin pool storage space is completely allocated to the logical address to be written into the thin LU;

a determining module, configured to determine, in the case that the determining result of the determining module is negative, that the logical address that is not allocated the thin pool storage space can be written by the logical address Length

An application module, configured to apply, to the thin pool, a storage space that is greater than or equal to a length of data that can be written by the consecutive logical addresses, by an integer multiple of a minimum storage unit that can be provided by the storage;

a storage information receiving module, configured to receive information about a storage space allocated by the thin pool in response to the application of the application module;

7. The system according to claim 6, further comprising:

The mapping table module is configured to record the logical address to be written into the thin LUN and the corresponding physical address on the thin pool in a mapping form in the mapping table.

The system according to claim 7, wherein the determining module comprises: a detecting unit, configured to detect a record of the logical address of the to-be-written thin LUN in the mapping table;

a determining unit, configured to: when the detecting unit detects that the logical address of the to-be-written thin LUN is completely recorded in the mapping table, determine that the logical address of the to-be-written thin LU has been completely allocated to the thin pool storage Space, or, when the detecting unit detects that the logical address portion of the LU to be written is not recorded in the mapping table, determines that the thin pool of the logical address to be written into the thin LU is not completely allocated. storage.

9. The system of claim 6, 7 or 8, wherein the determining module comprises:

a first determining unit, configured to determine, when the thin pool storage space is not allocated to the logical address to be written into the thin LU, the length of the data to be written is, the continuous storage space of the unallocated thin pool The length of the data that can be written to the logical address; a splitting unit, configured to: when a thin pool storage space is not completely allocated to the logical address to be written into the thin LU, use a logical address corresponding to the allocated storage space as a split point, and the thin LUN to be written The logical address is split;

a second determining unit, configured to determine, by using a consecutive logical address of the split logical storage address that is not allocated the thin pool storage space, a continuous logical address that is not allocated the thin pool storage space The length of the data written.

The system according to claim 6, wherein the application module includes: a predefined unit, configured to pre-define a minimum value of the granularity of the thin LUN allocation, where a minimum value of the allocated granularity is the memory The size of the smallest memory unit that can be provided;

An application unit, configured to apply, to the thin pool, a data that is greater than or equal to the continuous logical address and can write data by using a positive integer multiple of a minimum value of the thin LUN allocation granularity defined by the predefined unit. The storage space of the length, the difference between the size of the storage space of the thin pool of the application and the length of the data to be written is less than a preset threshold.