WO2016103356A1 - Système de mémoire hiérarchique, contrôleur de mémoire et procédé d'initialisation de duplication - Google Patents

Système de mémoire hiérarchique, contrôleur de mémoire et procédé d'initialisation de duplication Download PDF

Info

Publication number
WO2016103356A1
WO2016103356A1 PCT/JP2014/084100 JP2014084100W WO2016103356A1 WO 2016103356 A1 WO2016103356 A1 WO 2016103356A1 JP 2014084100 W JP2014084100 W JP 2014084100W WO 2016103356 A1 WO2016103356 A1 WO 2016103356A1
Authority
WO
WIPO (PCT)
Prior art keywords
extent
logical
physical
controller
storage
Prior art date
Application number
PCT/JP2014/084100
Other languages
English (en)
Japanese (ja)
Inventor
高山　雅陽
Original Assignee
株式会社 東芝
東芝ソリューション株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社 東芝, 東芝ソリューション株式会社 filed Critical 株式会社 東芝
Priority to JP2016514207A priority Critical patent/JP6022116B1/ja
Priority to PCT/JP2014/084100 priority patent/WO2016103356A1/fr
Publication of WO2016103356A1 publication Critical patent/WO2016103356A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures

Definitions

  • Embodiments described herein relate generally to a hierarchical storage system, a storage controller, and a replication initialization method.
  • the storage system is realized by hierarchically combining a first storage device (hereinafter referred to as a high speed storage device) and a second storage device (hereinafter referred to as a low speed storage device). Therefore, such a storage system is also called a hierarchical storage system.
  • a high-speed storage device is generally used as a higher-level storage device
  • a low-speed storage device is generally used as a lower-level storage device.
  • a logical disk refers to a logical storage area that is recognized as a storage that can be accessed by a host computer (hereinafter referred to as a host) using a storage system (hierarchical storage system) without difference from a single storage apparatus.
  • the logical storage area of a logical disk and the physical storage areas of a high-speed storage device and a low-speed storage device are both divided into a plurality of partial regions having a certain size for management. Is done.
  • Such a partial area is called an extent.
  • the former is called a logical extent and the latter is called a physical extent.
  • tearing is known as one of the functions used in the storage system.
  • “tearing” will be described by taking as an example a case where the storage system is a hierarchical storage system.
  • the controller of the hierarchical storage system acquires an access statistical value such as the number of accesses for each logical extent in the logical disk.
  • the storage controller changes the physical extent allocated to the first logical extent from the first physical extent to the second physical extent in the high-speed storage device. That is, the storage controller changes the tier assigned to the first logical extent from the lower tier to the upper tier.
  • the replication function refers to a function that manages an arbitrary plurality of logical disks in an integrated manner to hold replicated data.
  • the logical disk provided by the hierarchical storage system is also subject to replication.
  • the storage controller of the hierarchical storage system can operate by synchronizing (matching) the data of two logical disks completely using the replication function.
  • One of the two logical disks is used as a master logical disk and the other is used as a sub logical disk.
  • Input / output (I / O) requests from the host are processed as I / O requests to the master logical disk.
  • I / O requests from the host are processed as I / O requests to the master logical disk.
  • the storage controller executes a replication initialization process as preparation for operation in such a state. In the replication initialization process, the storage controller copies data from the master logical disk to the sub logical disk in order to make the data of the master and sub logical disk consistent.
  • the system transitions to a synchronous state in which the contents of the master and sub logical disks are the same.
  • the master and sub logical disks are recognized as a single logical disk from the host.
  • the host requests the storage controller to write data to the logical disk (master logical disk).
  • the storage controller writes data to the first and second physical storage areas assigned to the same logical address of each of the master and sub logical disks based on the logical address designated by the host.
  • the data write requested by the host is not completed until the data write to the first and second physical storage areas is completed.
  • one of the first and second physical storage areas is a physical storage area in the high-speed storage apparatus (that is, a high-speed physical storage area), and the other of the first and second physical storage areas is in the low-speed storage apparatus. It is assumed that it is a physical storage area (that is, a low-speed physical storage area).
  • the time when the requested data writing is completed depends on the time required to write the data to the low-speed physical storage area. That is, the performance of writing data to the logical disk recognized by the host is reduced depending on the writing of data to the low-speed physical storage area.
  • the problem to be solved by the present invention is to provide a hierarchical storage system, a storage controller, and a replication initialization method that can prevent a decrease in performance of writing data to a logical disk recognized by a host.
  • the hierarchical storage system includes a first storage device, a second storage device, and a storage controller.
  • the first storage device is used as an upper tier storage device, and includes a storage area including a plurality of first type physical extents corresponding to the upper tier.
  • the second storage device is used as a lower-level storage device, and includes a storage area including a plurality of second-type physical extents corresponding to the lower level.
  • the storage controller controls the first and second storage devices and includes a system management unit and a replication controller.
  • the system management unit manages a plurality of logical disks. Each of the plurality of logical disks includes a plurality of logical extents having the same size as the physical extent.
  • At least a part of the storage area of the first and second storage devices is allocated to the plurality of logical disks in units of the physical extent.
  • the replication controller performs replication initialization processing for synchronizing the first and second logical disks included in the plurality of logical disks as a master and a sub logical disk, respectively, in the first logical disk.
  • the first logical extent and the second logical extent in the second logical disk corresponding to the first logical extent are synchronized as a master and a sub logical extent, respectively, they are allocated to the second logical extent.
  • the type of the physical extent is matched with the type of the first physical extent currently allocated to the first logical extent.
  • FIG. 1 is a block diagram illustrating a typical hardware configuration of a computer system according to one embodiment.
  • FIG. 2 is a diagram for explaining a typical configuration of two logical disks applied in the hierarchical storage system shown in FIG.
  • FIG. 3 is a block diagram mainly showing a typical functional configuration of the storage controller shown in FIG.
  • FIG. 4 is a diagram showing an example of the data structure of the address conversion table shown in FIG.
  • FIG. 5 is a diagram showing an example of the data structure of the access counter table shown in FIG.
  • FIG. 6 is a flowchart for explaining a typical procedure of the replication initialization process according to the embodiment.
  • FIG. 7 is a flowchart for explaining a typical procedure of the hierarchy changing process according to the embodiment.
  • FIG. 1 is a block diagram illustrating a typical hardware configuration of a computer system according to one embodiment.
  • FIG. 2 is a diagram for explaining a typical configuration of two logical disks applied in the hierarchical storage system shown in FIG.
  • FIG. 3
  • FIG. 8 is a flowchart for explaining a typical procedure of replication initialization processing according to the modification of the embodiment.
  • FIG. 9 is a flowchart for explaining a typical procedure of the second copy process included in the replication initialization process.
  • FIG. 10 is a diagram for explaining a typical procedure of the hierarchy changing process according to the modification.
  • FIG. 11 is a flowchart for explaining a typical procedure of the second rearrangement process included in the hierarchy change process.
  • FIG. 1 is a block diagram illustrating a typical hardware configuration of a computer system according to one embodiment.
  • the computer system shown in FIG. 1 includes a hierarchical storage system 10 and a host computer (hereinafter referred to as a host) 20. That is, the computer system has a single host. However, the computer system may include a plurality of hosts.
  • the host 20 uses the logical disk provided by the hierarchical storage system 10 as its external storage device.
  • the host 20 is connected to the hierarchical storage system 10 (more specifically, the storage controller 13 of the hierarchical storage system 10) via the host interface bus 21, for example.
  • the host interface bus 21 is a fiber channel (FC).
  • the host interface bus 21 is an interface other than FC, such as a small computer system interface (SCSI), serial attached SCSI (SAS), Internet SCSI (iSCSI), Ethernet (registered trademark), or serial AT attachment (SATA). It can be a bus.
  • the host 20 may be connected to the hierarchical storage system 10 via a network.
  • the host 20 is a physical computer such as a server or a client personal computer (client PC).
  • client PC client personal computer
  • an application program for accessing data in the logical disk provided by the hierarchical storage system 10 operates.
  • the host 20 uses the hierarchical storage system 10 via the host interface bus 21.
  • the hierarchical storage system 10 includes a high-speed storage device (first storage device) 11, a low-speed storage device (second storage device) 12, and a storage controller 13.
  • the high speed storage device 11 and the low speed storage device 12 are connected to the storage controller 13 via the storage interface bus 22.
  • the storage interface bus 22 is FC (Fibre Channel).
  • the storage interface bus 22 may be an interface bus other than FC.
  • the high-speed storage device 11 is composed of, for example, a single solid state drive (SSD) having compatibility with a hard disk drive (HDD).
  • the low-speed storage device 12 is composed of a storage device that satisfies a certain condition (first condition) with respect to access response performance and storage capacity.
  • the storage device that satisfies the first condition refers to a storage device that has lower access response performance than the high-speed storage device 11 (that is, the access speed is low), but has a large storage capacity.
  • the low-speed storage device 12 is composed of a single HDD.
  • the high speed storage device 11 and the low speed storage device 12 are referred to as SSD 11 and HDD 12, respectively.
  • a high-speed storage device called a flash array storage equipped with a flash memory or an all-flash array may be used.
  • a low-speed storage device having an array configuration including a plurality of HDDs may be used.
  • a high-speed HDD such as an FC HDD may be used instead of the SSD 11
  • a low-speed HDD such as a SATA HDD may be used instead of the HDD 12.
  • an optical disk drive such as a Blu-ray Disc (registered trademark) drive or a DVD (registered trademark) drive, or a tape device may be used.
  • an optical disk drive may be used instead of the SSD 11.
  • the high-speed storage device As described above, as the high-speed storage device and the low-speed storage device, a storage device selected from a plurality of storage devices having various access speeds and storage capacities can be used. However, the low-speed storage device needs to satisfy the first condition regarding the access response performance and the storage capacity as described above.
  • the high-speed storage apparatus may be composed of a storage apparatus that satisfies the second condition regarding access response performance and storage capacity.
  • the storage device that satisfies the second condition refers to a storage device that has a small storage capacity but a high access response performance (that is, a high access speed) compared to a low-speed storage device.
  • the SSD 11 and the HDD 12 exist as two storage devices having different access speeds (that is, a high-speed storage device and a low-speed storage device).
  • the SSD 11 is used as an upper hierarchy (high speed hierarchy, first hierarchy)
  • the HDD 12 is used as a lower hierarchy (low speed hierarchy, second hierarchy).
  • the tiered storage system 10 may include a storage device (third tier storage device) having a lower speed (lower tier) and a larger capacity than the HDD 12.
  • the storage controller 13 receives an access (read access or write access) request (input / output request) using a logical address given from the host 20, and executes the requested input / output (I / O). In executing this I / O, the storage controller 13 converts a logical address into a physical address using a known address conversion function.
  • the logical address indicates an address in the logical disk recognized by the host 20.
  • the physical address indicates the physical position of the physical storage area included in the SSD 11 or HDD 12 and associated with the logical address.
  • the storage controller 13 accesses the SSD 11 or the HDD 12 based on the physical address.
  • the HIFC 131 controls data transfer (data transfer protocol) between the HIFC 131 and the host 20.
  • the HIFC 131 receives an I / O (input / output) request (read request or write request) from the host and returns a response to the I / O request.
  • This I / O request specifies reading data from a logical disk or writing data to the logical disk.
  • the HIFC 131 transmits the I / O request to the CPU 135.
  • the CPU 135 that has received the I / O request processes the I / O request.
  • the SIFC 132 receives from the CPU 135 an access request (more specifically, a read request or a write request for the SSD 11 or the HDD 12) corresponding to the I / O request from the host 20 received by the CPU 135.
  • the physical storage areas of the SSD 11 and the HDD 12 are also called physical disks (or physical volumes).
  • the entire physical storage area of each of the SSD 11 and the HDD 12 is defined as a physical disk.
  • a part of the physical storage area of each of the SSD 11 and the HDD 12 may be defined as a physical disk.
  • a plurality of physical disks may be defined using the SSD 11 and the HDD 12 respectively.
  • the above access request specifies reading data from a physical disk or writing data to the physical disk.
  • the SIFC 132 executes access to the SSD 11 or the HDD 12 in response to the received access request.
  • the local HDD 134 stores a control program 321 (FIG. 3).
  • the CPU 135 loads at least a part of the control program 321 stored in the local HDD 134 into the memory 133 by executing an initial program loader (IPL) when the storage controller 13 is activated.
  • IPL is stored in a non-volatile memory such as a read only memory (ROM) or a flash ROM (FROM).
  • the CPU 135 functions as a system management unit 301, an access controller 302, a replication controller 303, and a hierarchization controller 304 (FIG. 3) in accordance with a control program 321 loaded into the memory 133. That is, the CPU 135 executes the control program 321 stored in the memory 133 to control the entire hierarchical storage system 10 (particularly, each unit in the storage controller 13).
  • the storage controller 13 is provided independently of the host 20 as shown in FIG.
  • the storage controller 13 may be built in the host 20.
  • the storage controller 13 (more specifically, the function of the storage controller 13) may be realized by using a part of the operating system (OS) function of the host 20.
  • OS operating system
  • FIG. 2 is a diagram for explaining a typical configuration of two logical disks applied in the hierarchical storage system 10 shown in FIG.
  • the hierarchical storage system 10 uses logical disks (LDs) 211 and 212 as a master LD and a sub LD, respectively.
  • the LDs 211 and 212 may be referred to as a master LD 211 and a sub LD 212 depending on the usage state.
  • a physical extent in the SSD 11 (upper tier storage device) is referred to as a high speed physical extent (or first type physical extent), and a physical extent in the HDD 12 (lower tier storage device) is a low speed physical extent.
  • an extent (or a second type of physical extent).
  • the first type and the second type correspond to the above-described upper layer and lower layer, respectively.
  • the high-speed physical extent and the low-speed physical extent can be regarded as an upper-layer physical extent and a lower-layer physical extent, respectively.
  • the M1 physical extents included in the group of physical extents in the SSD 11 are allocated to the M1 logical extents in the master LD 211.
  • the M2 physical extents included in the group of physical extents in the SSD 11 are allocated to the M2 logical extents in the sub LD 212.
  • N1 physical extents included in the group of physical extents in the HDD 12 are allocated to N1 logical extents in the master LD 211.
  • N2 physical extents included in the group of physical extents in the HDD 12 are allocated to N2 logical extents in the sub LD 212.
  • Each logical extent and physical extent is divided into small areas having a second size for management.
  • This small area is called a block or a sector.
  • Both the SSD 11 and the HDD 12 can be accessed in units of blocks (or sectors).
  • the first size is 4 kilobytes (KB) and the second size is 512B. That is, the first size is eight times the second size.
  • the first size may be other than 4 KB, for example, 4 megabytes (MB).
  • FIG. 3 is a block diagram mainly showing a typical functional configuration of the storage controller 13 shown in FIG.
  • the storage controller 13 includes a system management unit 301, an access controller 302, a replication controller 303, and a hierarchical controller 304.
  • These functional elements 301 to 304 are software modules realized when the CPU 134 of the storage controller 13 shown in FIG. 1 executes the control program 321. However, at least one of the functional elements 301 to 304 may be realized by a hardware module.
  • the system management unit 301 constructs (defines) and manages a logical disk provided to the host 20 (that is, recognizable by the host 20). Further, the system management unit 301 uses the address conversion table 322 for the mapping state for each logical extent in all the logical disks provided to the host 20 (that is, the correspondence between the logical address of the logical extent and the physical address of the physical extent). Manage. The system management unit 301 converts the logical address into a physical address based on the address conversion table 322.
  • the hierarchization controller 304 controls hierarchization of the respective logical extents in the master LD 211 and the sub LD 212.
  • the hierarchization controller 304 dynamically changes the hierarchies allocated to the respective logical extents in the master LD 211 and the sub LD 212 in order to optimize the performance of the master LD 211 and the sub LD 212.
  • the hierarchization controller 304 determines a set of logical extents in the master LD 211 and the sub LD 212 whose hierarchy to be changed is to be changed based on the access counter table 323.
  • the layering controller 304 rearranges the data in the determined set of logical extents. That is, the hierarchization controller 304 rearranges the data in the physical extent allocated to the determined logical extent in the master LD 211 in two physical extents in a hierarchy different from the hierarchy to which the physical extent belongs.
  • the respective logical extents in the master LD 211 and the sub LD 212 may be referred to as a master logical extent and a sub logical extent.
  • physical extents respectively allocated to the master logical extent and the sub logical extent may be referred to as a master physical extent and a sub physical extent.
  • the memory 132 includes a control program area 311 and a table area 312.
  • the control program area 311 is used to store at least a part of the control program 321 executed by the CPU 134.
  • the table area 312 is used to store an address conversion table 322 and an access counter table 323.
  • the HDD 133 is used to store the control program 321 in advance.
  • the HDD 133 is used to store an address conversion table 322 and an access counter table 323. At least a part of the control program 321, the address conversion table 322, and the access counter table 323 are loaded and used from the HDD 133 to the control program area 310 and the table area 312 of the memory 132 when the storage controller 13 is activated, for example.
  • the address conversion table 322 and the access counter table 323 loaded in the memory 132 are stored in the HDD 133 as appropriate. That is, the information update in the table area 312 of the memory 132 is appropriately reflected in the address conversion table 322 and the access counter table 323 stored in the HDD 133.
  • FIG. 4 shows an example of the data structure of the address conversion table 322 shown in FIG.
  • the address conversion table 322 includes a master LD address conversion table 322a and a sub LD address conversion table 322b.
  • the master LD address conversion table 322a holds address conversion information used to convert the logical address of the master LD 211 into a physical address
  • the sub LD address conversion table 322b converts the logical address of the sub LD 212 into a physical address. Holds the address translation information used for.
  • Each of the master LD address conversion table 322a and the sub LD address conversion table 322b includes n entries 0 to n ⁇ associated with n logical extents 0 to n ⁇ 1 having logical extent numbers 0 to n ⁇ 1. 1 is provided.
  • Each entry of the master LD address conversion table 322a and the sub LD address conversion table 322b includes a logical disk identifier (LDID) field, a logical address field, a physical disk identifier (PDID) field, a physical address field, and a first flag (F1) field. , And a second flag (F2) field.
  • LDID logical disk identifier
  • PDID physical disk identifier
  • F1 first flag
  • F2 second flag
  • the logical address field of the entry i indicates the logical address of the logical extent i associated with the entry i (more specifically, the logical address of the first block of the logical extent i).
  • the logical address of the same logical extent i is set in the logical address field of both entries i of the master LD address conversion table 322a and the sub LD address conversion table 322b.
  • the PDID field of entry i indicates the ID of the PD (physical disk) including the physical extent assigned to the logical extent i.
  • the physical address field of the entry i indicates the physical address of the physical extent allocated to the logical extent i (more specifically, the physical address of the first block of the physical extent allocated to the logical extent i).
  • the F1 field of entry i is used to hold a flag F1 indicating whether the master and the sub logical extent i are synchronized.
  • the F2 field of entry i is used to hold a flag F2 indicating whether the logical extent i is included in the read-only area.
  • the F2 field of entry i is used in a later-described modification, it is not always necessary in the present embodiment.
  • the F1 and F2 fields may be prepared in at least one of the master LD address conversion table 322a and the sub LD address conversion table 322b (for example, the master LD address conversion table 322a). Further, the master LD address conversion table 322 a and the sub LD address conversion table 322 b may be merged into a single address conversion table, and this single address conversion table may be used as the address conversion table 322. In this case, the address conversion table 322 has 2n entries, and a logical extent number field indicating the logical extent number of the logical extent may be added to each of the 2n entries. Also, as in the example of FIG.
  • FIG. 5 shows an example of the data structure of the access counter table 323 shown in FIG.
  • the access counter table 323 is associated with the LDID of the master LD 211 and is used as access counter information indicating the number of accesses to each logical extent of the master LD 211.
  • the access counter table 323 includes n entries 0 to n ⁇ 1 associated with n logical extents 0 to n ⁇ 1 having logical extent numbers 0 to n ⁇ 1.
  • write count WCNTi since the write count WCNTi is used in the modification, it is not always necessary in the present embodiment.
  • two access counter tables similar to the access counter table 323 are prepared in association with the LDIDs of the LDs 211 and 212, respectively.
  • the state transition of replication will be explained.
  • the host 20 can recognize the LDs 211 and 212 individually and access the LDs 211 and 212 separately.
  • Such a state is called a split state. That is, the LDs 211 and 212 are in a split state.
  • the physical extents assigned to the logical extents i having the same logical extent number i in the LDs 211 and 212 are not necessarily present in the storage device of the same tier.
  • the host 20 accesses only the master LD 211 of the master LD 211 and the sub LD 212.
  • the access controller 302 writes data to both the master LD 211 and the sub LD 212 when the host 20 requests write access to the master LD 211 in the copy state or the synchronization state.
  • FIG. 6 is a flowchart for explaining a typical procedure of the replication initialization process.
  • the system management unit 301 selects, from the master LD 211 and the sub LD 212, a master and sub logical extent pair that is a target of replication initialization (step S1).
  • a sub logical extent i first and second logical extents
  • the system management unit 301 passes control to the replication controller 303 after executing step S2. Then, the replication controller 303 newly allocates the data in the specified master physical extent to the sub physical extent currently allocated to the sub logical extent i (that is, the specified sub physical extent) or the sub logical extent i.
  • the first copy process (step S3) for copying to the physical extent to be performed is executed as follows in cooperation with the system management unit 301.
  • the replication controller 303 determines whether the identified master physical extent exists in the SSD 11 based on the PDID in the acquired master physical extent address information (step S301). If the specified master physical extent exists in the SSD 11 (Yes in step S301), that is, if the specified master physical extent is a high-speed physical extent (first type physical extent), the replication controller. In step 303, the process proceeds to step S302. On the other hand, if the specified master physical extent does not exist in the SSD 11 (No in step S301), that is, if the specified master physical extent is a low-speed physical extent (second type physical extent). The replication controller 303 proceeds to step S303. In both steps S302 and S303, the replication controller 303 determines whether the specified sub physical extent exists in the SSD 11 based on the PDID in the address information of the acquired sub physical extent.
  • the replication controller 303 returns control to the system management unit 301 after executing step S306. Then, the system management unit 301 updates the sub LD address conversion table 322b (step S307). That is, the system management unit 301 sets the PDID and physical address set in the entry i associated with the logical extent number i in the sub LD address conversion table 322b to the physical extent secured in step S304 or S305, respectively. Change to PDID and physical address. As a result, the reserved physical extent is registered in the sub LD address conversion table 322b as a new sub physical extent corresponding to the identified master physical extent.
  • the system management unit 301 adds the physical extent number (and PDID) of the sub physical extent identified in step S2 to the free physical extent list. That is, the identified sub physical extent is registered in the free physical extent list as a free physical extent. Thereby, the first copy process (step S3) is completed. Then, the system management unit 301 proceeds to step S4.
  • step S303 determines that the specified master and sub-physical extents exist in the same tier (lower tier) storage device (that is, the HDD 12). That is, the replication controller 303 determines that the identified master and sub physical extent types are the same (second type). Also in this case, the replication controller 303 proceeds to step S308.
  • step S308 the replication controller 303 copies the data in the specified master physical extent (first physical extent) to the specified sub physical extent (second physical extent).
  • the sub logical extent i to which the identified sub physical extent is currently allocated is synchronized with the master logical extent i to which the identified master physical extent is currently allocated.
  • the first copy process (step S3) ends, and the replication controller 303 returns control to the system management unit 301.
  • the system management unit 301 proceeds to step S4.
  • the host 20 requests the storage controller 13 to write data to the master LD 211.
  • the replication controller 303 controls the access controller 302 so that data is written to the set of logical extents x of the master LD 211 and the sub LD 212.
  • the data writing operation in the copy state differs depending on whether the synchronization of the logical extent x of each of the master LD 211 and the sub LD 212 (that is, master and sub logical extent x) has been completed.
  • the access controller 302 writes data only to the master sub physical extent allocated to the master logical extent x.
  • the replication controller 303 executes the first copy process (step S3) described above.
  • the master and the sub logical extent x are synchronized simultaneously with the writing of the write data to the master and the sub logical extent x.
  • the system management unit 301 synchronizes the flag F1 set in the F1 field in the entry associated with the master and sub logical extent x in the master LD address conversion table 322a and the sub LD address conversion table 322b. Update to show status.
  • step S306 the access controller 302 (or the replication controller 303) may write the data designated by the host 20 in the reserved physical extent.
  • step S308 the access controller 302 (or the replication controller 303) may write the data designated by the host 20 in the specified sub physical extent.
  • the host 20 may request to write data to a part of the logical extent x.
  • the access controller 302 (or the replication controller 303) merges the data (write data) specified by the host 20 and the data in the specified master physical extent, and secures the merged data. It is sufficient to write to the specified master physical extent or the specified sub physical extent.
  • the hierarchization controller 304 selects a master logical extent that is a candidate for hierarchy change based on the access counter table 323 (step S11). That is, the hierarchization controller 304 searches the access counter table 323 for an entry z including the maximum access count ACNT, is associated with the entry z, and is included in the master LD 211 (the master logical extent z (first number)). 3) is selected as a candidate for hierarchy change.
  • the hierarchical controller 304 transfers control to the system management unit 301 when step S11 is executed. Then, the system management unit 301 refers to the address conversion table 322a on the basis of the logical extent number z of the selected master logical extent z, so that the master physical extent (third physical extent) allocated to the master logical extent z is referred to. An extent is specified (step S12). That is, the system management unit 301 acquires the address information of the master physical extent allocated to the master logical extent z.
  • step S12 the system management unit 301 returns control to the hierarchical controller 304. Then, the hierarchization controller 304 determines whether it is necessary to change the hierarchy allocated to the selected master logical extent z based on whether the specified master physical extent exists in the HDD 12 (step S13).
  • the hierarchical controller 304 determines that the hierarchy assigned to the selected master logical extent z is an upper hierarchy, and therefore the hierarchy change is It is determined that it is not necessary (No in step S13). In this case, this is equivalent to the fact that the logical extent whose hierarchy is to be changed has not been selected, and the hierarchization controller 304 skips the next step S14 (first relocation process) and proceeds to step S15.
  • the first relocation process in order to change the hierarchy assigned to the master logical extent z, data in the master physical extent (low-speed physical extent) currently assigned to the master logical extent z is changed to the master and the master logical extent z. It includes a process of rearranging (copying) two high-speed physical extents (fourth and fifth physical extents) to be newly allocated to the sub logical extent z (third and fourth logical extents).
  • the hierarchical controller 304 determines that the hierarchy assigned to the selected master logical extent z is a lower hierarchy, and therefore the hierarchy It is determined that a change is necessary (Yes in step S13). In this case, it is equivalent to the master logical extent z being selected as the logical extent whose hierarchy is to be changed, and the hierarchical controller 304 performs the first relocation process (step S14) with the system management unit 301. Work together as follows:
  • the hierarchical controller 304 converts the two physical extents in the SSD 11 to be newly changed to free physical extents into a master LD address conversion table 322a and sub LD address conversion. Based on the table 322b and the access counter table 323, the following determination is made. First, the hierarchical controller 304 searches for a master logical extent y having the smallest access count ACNT among the master logical extents to which the high-speed physical extent is allocated based on the master LD address conversion table 322a and the access counter table 323.
  • the hierarchization controller 304 determines the master physical extent (high-speed physical extent) assigned to the master logical extent y and the sub physical extent assigned to the sub logical extent y having the same logical extent number y as the master logical extent y. Specify an extent (high-speed physical extent).
  • the hierarchical controller 304 copies the data in the specified master physical extent to two free physical extents (that is, low-speed physical extents) in the HDD 12.
  • the system management unit 301 uses the master LD address conversion table 322a and the sub LD.
  • the address conversion table 322b is updated. Thereby, the hierarchization controller 304 can secure two free physical extents in the SSD 11.
  • the hierarchical controller 304 returns control to the system management unit 301 after executing step S142. Then, the system management unit 301 updates the master LD address conversion table 322a (step S143). That is, the system management unit 301 sets the PDID and physical address set in the entry z associated with the logical extent number z in the master LD address conversion table 322a, for example, the fourth physical address secured in step S141. Change to the PDID and physical address of the extent. As a result, the secured fourth physical extent is registered in the master LD address conversion table 322a as a new master physical extent that replaces the master physical extent (third physical extent) specified in step S12.
  • step S144 the system management unit 301 updates the sub LD address conversion table 322b (step S144). That is, the system management unit 301 sets the PDID and the physical address set in the entry z associated with the logical extent number z in the sub LD address conversion table 322b, for example, the fifth physical allocated in step S141. Change to the PDID and physical address of the extent. As a result, the reserved fifth physical extent becomes a sub-LD address conversion table 322b as a new sub-physical extent that replaces the sub-physical extent allocated to the sub-logical extent z before the first relocation processing this time. Registered in Note that step S144 may be executed prior to step S143.
  • the system management unit 301 returns control to the hierarchical controller 304 when executing steps S143 and S144, that is, executing step S14. Then, the hierarchization controller 304 proceeds to step S15.
  • step S15 the hierarchical controller 304 determines whether the currently selected master logical extent z is the last hierarchical change candidate, for example, as follows. First, the hierarchization controller 304 compares the number of hierarchy change candidates selected so far in the hierarchy change process with a reference value. If the number of selected hierarchy change candidates is less than the reference value, the hierarchization controller 304 determines that the master logical extent z is not the last hierarchy change candidate (No in step S15). On the other hand, if the number of selected hierarchy change candidates matches the reference value, it is determined that the master logical extent z is the last hierarchy change candidate (Yes in step S15).
  • step S15 the hierarchization controller 304 returns to step S11.
  • step S11 the hierarchical controller 304 searches the access counter table 323 for an entry z including the next largest access count ACNT, and associates with the new entry z that is associated with the entry z and included in the master LD 211.
  • the logical extent z is selected as the next hierarchy change candidate. That is, the hierarchization controller 304 selects a new master logical extent z having the largest access count ACNT among the master logical extents not yet selected as a hierarchy change candidate as the next hierarchy change candidate.
  • the subsequent operations are the same as when the first hierarchy change candidate is selected.
  • step S15 the hierarchization controller 304 ends the hierarchy change process.
  • the physical extent allocated to the master logical extent is changed from the low speed physical extent to the high speed physical extent
  • the physical extent allocated to the sub logical extent is also changed from the low speed physical extent to the high speed physical extent. Be changed. Thereby, there is no possibility that the performance of data writing to the master LD 211 and the sub LD 212 will be lowered depending on the performance of data writing to the sub physical extent.
  • each of the master LD 211 and the sub LD 212 is used as a read-only area. Further, it is assumed that the logical extents in the read-only areas of the master LD 211 and the sub LD 212 are the logical extent i (that is, the master and the sub logical extent i).
  • data is not written to the master and sub physical extents assigned to the master and sub logical extent i. That is, regarding the read-only areas of the master LD 211 and the sub-LD 212, there is no need to consider data writing for synchronization, and therefore there is no need to consider performance degradation due to data writing for synchronization. Therefore, for example, even if a physical extent (that is, a high-speed physical extent) in the SSD 11 has already been allocated (or newly allocated) to the master logical extent i, another physical extent in the SSD 11 is replaced with a sub logical extent. It is not always necessary to assign i.
  • the feature of this modification is that when the master and sub logical extents are included in the read-only areas of the master LD 211 and the sub LD 212, the physical extent in the HDD 12 (that is, the low speed extent) is always assigned to the sub logical extent. There is.
  • FIG. 8 is a flowchart for explaining a typical procedure of the replication initialization process according to this modification.
  • the system management unit 301 selects a set of a master and a sub logical extent i (first and second logical extents) as in step S1 in the embodiment (step S21).
  • the system management unit 301 identifies the master and sub physical extents (first and second physical extents) allocated to the master and sub logical extent i, similarly to step S2 in the embodiment (step S22). ).
  • the system management unit 301 passes control to the replication controller 303.
  • the system management unit 301 sets the flag F2 set in the F2 field of the entry i associated with the master and the sub logical extent i. Passed to the replication controller 303.
  • step S24 the replication controller 303 determines whether the write count WCNTi associated with the logical extent number i is less than the threshold value WCNTTH.
  • the write count WCNTi is set in the entry i associated with the logical extent number i in the access counter table 323.
  • the replication controller 303 determines that the frequency of data writing to the master and sub logical extent i is high. In this case, the replication controller 303 executes the first copy process in cooperation with the system management unit 301 in the same manner as S3 in the embodiment (step S25).
  • the replication controller 303 returns control to the system management unit 301 after executing step S263. Then, the system management unit 301 updates the sub LD address conversion table 322b (step S264). That is, the system management unit 301 uses the PDID and physical address set in the entry i associated with the logical extent number i in the sub LD address conversion table 322b, respectively, for the physical extent PDID and the physical extent secured in step S262. Change to a physical address. As a result, the second copy process (step S26) ends, and the replication controller 303 returns control to the system management unit 301. Then, the system management unit 301 proceeds to step S27.
  • step S261 the replication controller 303 proceeds to step S265.
  • step S265 the replication controller 303 copies the data in the specified master physical extent (first physical extent) to the specified sub physical extent (second physical extent).
  • the sub logical extent i to which the specified sub physical extent is currently allocated is synchronized with the master logical extent i to which the specified master physical extent is currently allocated.
  • step S26 ends, and the replication controller 303 returns control to the system management unit 301. Then, the system management unit 301 proceeds to step S27.
  • the master logical extent is included in the read-only area, or the master logical extent If the frequency of data writing to is low, the high-speed physical extent is prevented from being assigned to the sub logical extent. As a result, it is possible to save expensive and small-capacity SSD 11 resources.
  • FIG. 10 is a flowchart for explaining a typical procedure of the hierarchy changing process.
  • the hierarchy change process is started in a state where the master LD 211 and the sub LD 212 are synchronized, as in the above embodiment.
  • the master and the sub physical extent allocated to the master and the sub logical extent z do not necessarily exist in the storage device of the same tier.
  • the master physical extent is a physical extent in the HDD 12 (that is, a low-speed physical extent)
  • the sub physical extent is also a low-speed physical extent.
  • the hierarchization controller 304 selects a master logical extent z (third logical extent) that is a candidate for hierarchy change based on the access counter table 323, similarly to step S11 in the embodiment (step S31).
  • the hierarchization controller 304 passes control to the system management unit 301.
  • the system management unit 301 specifies the master physical extent (third physical extent) allocated to the selected master logical extent z, similarly to step S12 in the embodiment (step S32).
  • the layering controller 304 determines that a layer change is necessary (Yes in step S33). In this case, the hierarchical controller 304 determines whether the selected master logical extent z and the sub logical extent z associated with the master logical extent z exist in the read-only areas of the master LD 211 and the sub LD 212, respectively. Determination is made (step S34).
  • the sub logical extent z is specified by the system management unit 301 referring to the entry z in the sub LD address conversion table 322b based on the logical extent number z of the master logical extent z, for example.
  • the sub physical extent to which the sub logical extent z is allocated is also specified based on the entry z in the sub LD address conversion table 322b.
  • the determination in step S34 is executed based on the flag F2 set in the F2 field of the entry z associated with the master and the sub logical extent z, as in step S23 (FIG. 8) in the present modification.
  • step S34 the hierarchical controller 304 proceeds to step S35.
  • step S35 the hierarchization controller 304 determines whether or not the write count WCNTz associated with the logical extent number z is less than the threshold value WCNTTH.
  • step S35 the hierarchization controller 304 executes the first rearrangement process in cooperation with the system management unit 301 in the same manner as in S14 in the embodiment.
  • step S36 the hierarchization controller 304 executes the first rearrangement process in cooperation with the system management unit 301 in the same manner as in S14 in the embodiment.
  • the data of the specified master physical extent third physical extent
  • two free physical extents fourth and fifth physical extents
  • the hierarchization controller 304 proceeds to step S38.
  • step S34 if the selected master and sub logical extent z are present in the read-only area (Yes in step S34), the hierarchical controller 304 proceeds to step S37. Also, when the write count WCNTz is less than the threshold value WCNTTH (Yes in step S35), the hierarchization controller 304 proceeds to step S37.
  • step S37 the hierarchical controller 304 executes the second rearrangement process in cooperation with the system management unit 301.
  • the feature of the second relocation process is that, unlike the first relocation process, the data in the specified master physical extent is one new high-speed physical extent (in the SSD 11) to be newly allocated to the master logical extent z. Relocation (copying) to only one free physical extent).
  • the second rearrangement process (step S37) will be described with reference to FIG.
  • FIG. 11 is a flowchart for explaining a typical procedure of the second rearrangement process.
  • the hierarchization controller 304 secures one free physical extent in the SSD 11 (step S371).
  • the hierarchical controller 304 copies (rearranges) the data in the identified master physical extent (third physical extent) to the secured physical extent (sixth physical extent) (step S372).
  • the hierarchical controller 304 transfers control to the system management unit 301 after executing step S372. Then, the system management unit 301 updates the master LD address conversion table 322a (step S373). That is, the system management unit 301 uses the PDID and physical address set in the entry z associated with the logical extent number z in the master LD address conversion table 322a as the PDID of the physical extent secured in step S371, respectively. Change to a physical address. As a result, the second arrangement process (step S37) ends, and the system management unit 301 returns control to the hierarchical controller 304. Then, the hierarchization controller 304 proceeds to step S38.
  • step S37 the physical extent (sixth physical extent) secured in step S371 is replaced with the master physical extent (third physical extent) specified in step S32.
  • the master physical extent is registered in the master LD address conversion table 322a as a master physical extent newly allocated to the master logical extent z. That is, the master physical extent is changed from the low speed physical extent to the high speed physical extent.
  • the sub physical extent is maintained as a low speed physical extent.
  • step S38 the hierarchization controller 304 determines whether the currently selected master logical extent z is the last hierarchy change candidate, as in step S15 in the above embodiment. If the determination in step S38 is No, the hierarchical controller 304 returns to step S31. On the other hand, if the determination in step S38 is Yes, the hierarchization controller 304 ends the hierarchy change process.
  • the master logical extent is included in the read-only area, or the master If the frequency of data writing to the logical extent is low, the high-speed physical extent is prevented from being assigned to the sub logical extent. As a result, it is possible to save expensive and small-capacity SSD 11 resources.
  • the replication initialization process and the hierarchy change process applied in the modified example are predetermined by the control program 321. However, it is designated by the user whether to execute the replication initialization process and the hierarchy change process as applied in the embodiment, or the replication initialization process and the hierarchy change process as applied in the modification. It may be determined in response to a request from the host 20 based on it.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Selon un mode de réalisation, l'invention porte sur un système de mémoire hiérarchique qui comprend un premier dispositif de mémoire servant de dispositif de mémoire de niveau supérieur, un second dispositif de mémoire servant de dispositif de mémoire de niveau inférieur, et un contrôleur de mémoire. Au cours d'un processus d'initialisation de duplication pour faire respectivement d'un premier disque logique et d'un second disque logique un disque logique primaire et un disque logique secondaire, et synchroniser ces disques l'un sur l'autre, le contrôleur de duplication dans le contrôleur de mémoire amène le type d'une étendue physique qui doit être attribuée à une seconde étendue logique dans le second disque logique, correspondant à une première étendue logique dans le premier disque logique, à coïncider avec le type d'une première étendue physique attribuée à ce moment à la première étendue logique.
PCT/JP2014/084100 2014-12-24 2014-12-24 Système de mémoire hiérarchique, contrôleur de mémoire et procédé d'initialisation de duplication WO2016103356A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2016514207A JP6022116B1 (ja) 2014-12-24 2014-12-24 階層化ストレージシステム、ストレージコントローラ及びレプリケーション初期化方法
PCT/JP2014/084100 WO2016103356A1 (fr) 2014-12-24 2014-12-24 Système de mémoire hiérarchique, contrôleur de mémoire et procédé d'initialisation de duplication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2014/084100 WO2016103356A1 (fr) 2014-12-24 2014-12-24 Système de mémoire hiérarchique, contrôleur de mémoire et procédé d'initialisation de duplication

Publications (1)

Publication Number Publication Date
WO2016103356A1 true WO2016103356A1 (fr) 2016-06-30

Family

ID=56149455

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/084100 WO2016103356A1 (fr) 2014-12-24 2014-12-24 Système de mémoire hiérarchique, contrôleur de mémoire et procédé d'initialisation de duplication

Country Status (2)

Country Link
JP (1) JP6022116B1 (fr)
WO (1) WO2016103356A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107656748A (zh) * 2017-09-08 2018-02-02 北京京东尚科信息技术有限公司 应用发布的方法和装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101947504B1 (ko) 2017-07-06 2019-02-13 주식회사 티맥스데이터 데이터 파일의 익스텐트 할당 방법

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008084253A (ja) * 2006-09-29 2008-04-10 Hitachi Ltd ボリューム選択方法及び情報処理システム
JP2013168162A (ja) * 2013-04-01 2013-08-29 Hitachi Ltd 記憶装置のデータ移行制御方法
JP2013196290A (ja) * 2012-03-19 2013-09-30 Fujitsu Ltd バックアップ装置，バックアップ方法，およびバックアッププログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008084253A (ja) * 2006-09-29 2008-04-10 Hitachi Ltd ボリューム選択方法及び情報処理システム
JP2013196290A (ja) * 2012-03-19 2013-09-30 Fujitsu Ltd バックアップ装置，バックアップ方法，およびバックアッププログラム
JP2013168162A (ja) * 2013-04-01 2013-08-29 Hitachi Ltd 記憶装置のデータ移行制御方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107656748A (zh) * 2017-09-08 2018-02-02 北京京东尚科信息技术有限公司 应用发布的方法和装置

Also Published As

Publication number Publication date
JPWO2016103356A1 (ja) 2017-04-27
JP6022116B1 (ja) 2016-11-09

Similar Documents

Publication Publication Date Title
US20200210082A1 (en) Compound storage system and storage control method to configure change associated with an owner right to set the configuration change
US7415573B2 (en) Storage system and storage control method
US9063877B2 (en) Storage system, storage controller, and method for managing mapping between local address and physical address
JP5583227B1 (ja) 物理ブロック間でデータをコピーするディスクアレイ装置、ディスクアレイコントローラ及び方法
JP5314772B2 (ja) 性能の異なる実領域群で構成されたプールを有するストレージシステムの管理システム及び方法
JP6067819B1 (ja) 階層化ストレージシステム、ストレージコントローラ、並びに重複排除及びストレージ階層化のための方法
US8055723B2 (en) Virtual array site configuration
US7933938B2 (en) File storage system, file storing method and file searching method therein
WO2015114809A1 (fr) Système de stockage hiérarchique, dispositif de commande de stockage et procédé pour remplacer un transfert de données entre des niveaux
WO2013018132A1 (fr) Système informatique avec allocation dynamique et procédé de gestion de données associé pour échelonnement dynamique
US8539142B2 (en) Storage system comprising nonvolatile semiconductor storage media
WO2017149592A1 (fr) Dispositif de stockage
US10649891B2 (en) Storage device that maintains mapping data therein
CN113918087B (zh) 存储装置以及用于管理存储装置中的命名空间的方法
US10089125B2 (en) Virtual machines accessing file data, object data, and block data
JP6022116B1 (ja) 階層化ストレージシステム、ストレージコントローラ及びレプリケーション初期化方法
WO2015140931A1 (fr) Système d'enregistrement hiérarchique comportant une zone d'essai, contrôleur d'enregistrement, et programme
JP6165909B1 (ja) 階層化ストレージシステム、ストレージコントローラ、及び階層化制御方法
US11875051B2 (en) Contiguous data storage using group identifiers
US10853257B1 (en) Zero detection within sub-track compression domains
US11144445B1 (en) Use of compression domains that are more granular than storage allocation units
JP5355603B2 (ja) ディスクアレイ装置及び論理ボリュームアクセス方法
JP5215434B2 (ja) 複数の不揮発性メモリを備えたストレージ装置、ストレージコントローラ及び論理ディスク生成方法
WO2018051446A1 (fr) Système informatique comprenant un système de stockage avec fonction optionnelle de traitement de données, et procédé de commande de stockage
JP2020102237A (ja) 情報処理システム

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2016514207

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14908963

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14908963

Country of ref document: EP

Kind code of ref document: A1