WO2017084348A1 - Ip硬盘的管理方法和装置 - Google Patents

Ip硬盘的管理方法和装置 Download PDF

Info

Publication number
WO2017084348A1
WO2017084348A1 PCT/CN2016/087917 CN2016087917W WO2017084348A1 WO 2017084348 A1 WO2017084348 A1 WO 2017084348A1 CN 2016087917 W CN2016087917 W CN 2016087917W WO 2017084348 A1 WO2017084348 A1 WO 2017084348A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
target
written
identifier
hard disk
Prior art date
Application number
PCT/CN2016/087917
Other languages
English (en)
French (fr)
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 华为技术有限公司
Publication of WO2017084348A1 publication Critical patent/WO2017084348A1/zh

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
    • 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
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061—Improving I/O performance
    • 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
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G06F3/0688—Non-volatile semiconductor memory arrays

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a method and an apparatus for managing an IP hard disk.
  • IP hard disk is a hard disk that provides an Ethernet interface and uses a Transmission Control Protocol (TCP)/IP to communicate directly with an upper layer network and provides an object storage service.
  • TCP Transmission Control Protocol
  • the IP hard disk Different from the ordinary Serial Advanced Technology Attachment (SATA) disk or the Serial Attached Small Computer System Interface (SAS) disk, the IP hard disk only provides the key/value. Interface, the user only needs to provide the key/value value to the IP hard disk to access the data, without concern for the specific logical block address (LBA) of the data on the disk, which greatly simplifies the IP hard disk.
  • LBA logical block address
  • IP hard disks produced by different manufacturers are different.
  • an IP hard disk is implemented by placing an adapter board (Dongle) on the disk drive of each hard disk.
  • the board is equivalent to an ARM processor-based Mini Storage Controller with independent memory, through which a traditional block-shaped disk becomes an IP accessed in the form of an object. Disk.
  • each manufacturer builds an open storage and storage platform based on its own IP hard disk.
  • the storage platform is used to manage and adapt the IP hard disk produced by the home, and provides the corresponding interface form to the user, but the storage platform cannot be adapted.
  • IP hard drives produced by other manufacturers For example, Seagate's kinetic storage platform is a storage platform built on kinetic IP hard disks. It can only be adapted to kinetic IP hard disks and is not compatible with IP drives from other manufacturers.
  • the interfaces of the IP hard disks produced by different manufacturers are different. Moreover, there is no unified standard in the industry that can be adapted to different IP hard disks. Therefore, the interface format of the unified IP hard disk cannot be provided to the user, and IP cannot be implemented. The unified management of the hard disk has caused the application of the IP hard disk to be greatly limited.
  • the embodiment of the invention provides a method and a device for managing an IP hard disk, providing a unified interface form of the IP hard disk to the user, and implementing unified management of the IP hard disk, so that the IP hard disk is more widely used.
  • an embodiment of the present invention provides a method for managing an IP hard disk, where the storage system includes a plurality of IP hard disks and at least one IP hard disk controller, and the IP hard disk controller includes a processor and a memory, and the method includes The processor is configured to: receive a resource request sent by a client, where the resource request includes data to be written, and length and attribute information of the data to be written; according to the length and attribute of the data to be written Determining an identifier of the one or more target IP hard disks to be written; determining an interface type of the target IP hard disk according to the identifier of the target IP hard disk and the interface library, where the identifier of each IP hard disk is saved in the interface library Corresponding relationship between the interface types corresponding thereto; converting the data to be written into a data protocol corresponding to the interface type; and transmitting the data protocol to the target IP hard disk.
  • the interface library stores the mapping between the identifiers of the IP disks and the corresponding interface types. Therefore, the processor can query the interface library to obtain interface types of different types of IP disks, and IP addresses of different interface types.
  • the hard disk communicates to realize unified management of different types of IP hard disks.
  • users can store data in different types of IP hard disks by communicating with the processor through the client, which is equivalent to providing a unified interface form to the user, so that the IP hard disk
  • the application is more extensive.
  • the device in this embodiment may be used to perform the method and technical solution provided by the second possible implementation manner of the first aspect, and the implementation principle and the beneficial effects are similar, and details are not described herein again.
  • the resource request further includes a client identifier, and the determining the one to be written according to the length and attribute information of the data to be written Before the identification of the plurality of target IP hard disks, the method further includes: determining, according to the correspondence between the client identifier and the identifier of the client identifier and the user resource pool, the target user resource pool corresponding to the client identifier Identifying; the target user resource pool includes the one or more target IP hard disks; and determining, according to the length and attribute information of the data to be written, an identifier of one or more target IP hard disks to be written, including And determining, according to the length of the data to be written and attribute information, an identifier of the one or more target IP hard disks from the target user resource pool.
  • the processor selects the target IP hard disk from the user resource pool created in advance for the client, and narrows the check. The range of IP hard disks is inspected, which effectively increases
  • the method further includes: sending a reserve operation instruction to the one or more target IP hard disks, where the reserve operation instruction is used to indicate that the target IP hard disk is the client Reserve storage resources.
  • the processor sends a reserved operation instruction to the target IP hard disk before the data is written, so that the target IP hard disk reserves storage resources for the data to be written, thereby avoiding that the other data occupies the target IP hard disk. This phenomenon of writing data failed.
  • the determining, according to the length of the data to be written and attribute information, determining a plurality of target IP hard disks to be written The identifier includes: performing fragmentation processing on the to-be-written data according to the length and attribute information of the to-be-written data; performing hash calculation on each fragmentation data to generate a key of each of the fragmentation data a word; determining, according to the keyword of each piece of fragmentation data, an identifier of a corresponding target IP hard disk for each piece of slice data.
  • the data to be written is stored in a plurality of target IP hard disks, and the storage speed is fast and the storage efficiency is high.
  • a second aspect of the present invention provides an apparatus for managing an IP hard disk, including: a receiving module, receiving a resource request sent by a client, where the resource request includes data to be written, and a length of the data to be written and Attribute information; a processing module, configured to determine, according to the length of the data to be written and attribute information, an identifier of one or more target IP hard disks to be written; determining, according to the identifier of the target IP hard disk and the interface library, respectively An interface type of the target IP hard disk, where the interface library stores a correspondence between an identifier of each IP hard disk and a corresponding interface type; and the data to be written is converted into a data protocol corresponding to the interface type; And a module, configured to send the data protocol to the target IP hard disk.
  • the device of this embodiment may be used to implement the technical solution of the method provided by the first aspect, and the implementation principle and the beneficial effects are similar, and details are not described herein again.
  • the processing module is further configured to use the client identifier and the client identifier and the user resource And determining, by the identifier of the pool, the identifier of the target user resource pool corresponding to the client identifier; the target user resource pool includes the one or more target IP hard disks; The length of the write data and the attribute information determine the identifier of the one or more target IP hard disks to be written, including: the processing module according to the length of the data to be written and Attribute information, determining an identifier of the one or more target IP hard disks from the target user resource pool.
  • the device in this embodiment may be used to perform the method and technical solution provided by the first possible implementation manner of the first aspect, and the implementation principle and the beneficial effects are similar, and details are not described herein again.
  • the sending module is further configured to send a reserved operation instruction to the one or more target IP hard disks.
  • the reservation operation instruction is used to instruct the target IP hard disk to reserve storage resources for the client.
  • the device in this embodiment may be used to perform the method and technical solution provided by the second possible implementation manner of the first aspect, and the implementation principle and the beneficial effects are similar, and details are not described herein again.
  • the processing module determines, according to the length of the data to be written and attribute information, multiple target IPs to be written
  • the identifier of the hard disk includes: the processing module performs a fragmentation process on the data to be written according to the length and attribute information of the data to be written; and performs hash calculation on each fragment data to generate the foregoing a keyword of the fragmentation data; determining, according to the keyword of each fragmentation data, an identifier of the corresponding target IP hard disk for each of the fragmentation data.
  • the device of this embodiment may be used to perform the technical solution of the method provided by the third possible implementation manner of the first aspect, and the implementation principle and the beneficial effects are similar, and details are not described herein again.
  • FIG. 1 is a schematic diagram of an application scenario of a method for managing an IP hard disk according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for managing an IP hard disk according to Embodiment 1 of the present invention
  • FIG. 3 is a flowchart of a method for managing an IP hard disk according to Embodiment 2 of the present invention.
  • FIG. 4 is a schematic diagram of a form of a user resource pool provided by the present invention.
  • FIG. 5 is a schematic diagram of another user resource pool provided by the present invention.
  • FIG. 6 is a schematic diagram of another form of a user resource pool provided by the present invention.
  • FIG. 7 is a schematic structural diagram of an apparatus for managing an IP hard disk according to Embodiment 3 of the present invention.
  • the method of the embodiment of the present invention is to solve the problem that the IP hard disk management method in the prior art cannot provide a unified IP hard disk interface form to the user, and the unified management of the IP hard disk cannot be implemented, which causes the application of the IP hard disk to be greatly affected.
  • FIG. 1 is a schematic diagram of an application scenario of a method for managing an IP hard disk according to an embodiment of the present invention.
  • the scenario is a storage system.
  • the storage system includes at least an IP hard disk controller and a plurality of IP hard disks.
  • the IP hard disk controller can be a server, a computer, and the like, and the IP hard disk controller includes the processor 1 .
  • the memory 6, the memory 6 is used to store the interface library 2 and the interface library 3.
  • the IP hard disk 4 and the IP hard disk 5 are two types of IP hard disks having different interface types.
  • the processor 1 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. .
  • the processor 1 is configured to receive a resource request and a read data request sent by the client, process the resource request and the read data request, send the data request to the IP hard disk, and perform other operations.
  • the memory 6 is for storing program instructions and related data, and the memory 6 may include a high speed RAM memory, and may also include a non-volatile memory such as at least one disk memory. It can be understood that the memory 6 can be a random memory (RAM), a magnetic disk, a hard disk, an optical disk, a solid state disk (SSD), or a nonvolatile memory, and can store program codes. Non-transitory machine readable medium. In the embodiment of the present invention, the memory 6 can be used to store related program instructions, interface libraries, and the like.
  • the interface library is a storage file in the form of a folder, a database, a table, or the like, or a software program for querying data.
  • the interface library includes a correspondence between an identifier of the IP hard disk and its corresponding interface type, and each interface library corresponds to one interface.
  • Type IP hard disk the interface library can also record the number of IP hard disks corresponding to the interface type and add, delete and other information.
  • the interface type of the IP hard disk may be a Small Computer System Interface (SCSI) or a Serial Attached SCSI (SAS).
  • FIG. 2 is a flowchart of a method for managing an IP hard disk according to Embodiment 1 of the present invention. The method of this embodiment is applied to the scenario shown in FIG. 1, and the method is performed by the processor in FIG. 1, as shown in FIG. 2, the method includes the following steps:
  • Step 101 Receive a resource request sent by a client, where the resource request includes data to be written, and length and attribute information of the data to be written.
  • the length of the data to be written is used to determine the storage space required for storing the data to be written, and the data information of the data to be written includes text, pictures, audio, video, and the like.
  • Step 102 Determine an identifier of one or more target IP hard disks to be written according to the length of the data to be written and the attribute information.
  • the processor determines, according to the attribute information of the data to be written, the type of the IP hard disk required to store the data, and determines the number of the corresponding type of IP hard disks required to store the data according to the length of the data to be written. Thereby determining the identity of one or more target IP hard disks.
  • Step 103 Determine the interface type of the target IP hard disk according to the identifier of the target IP hard disk and the interface library, and the interface library stores the correspondence between the identifiers of the IP hard disks and the corresponding interface types.
  • the interface type of the IP hard disk is different. After determining the type of the IP hard disk, the processor needs to query the interface library to obtain the interface type corresponding to the identifier of the target IP hard disk.
  • the interface library can be in the form of a folder, a database, a table, and the like.
  • Step 104 Convert the data to be written into a data protocol corresponding to the interface type.
  • Step 105 Send the data protocol to the target IP hard disk.
  • the processor converts the data to be written into a data protocol corresponding to the interface type of the target IP, and then sends the data to the target IP hard disk to ensure that the IP hard disk can correctly parse the data protocol and store the data.
  • the processor receives the resource request sent by the client, and determines the identifier of the one or more target IP hard disks to be written according to the length of the data to be written in the resource request and the attribute information. Determine the interface type of the target IP hard disk according to the identifier of the target IP hard disk and the interface library, and convert the data to be written into a data protocol corresponding to the interface type, and send the data protocol to the target IP hard disk.
  • the interface library stores the mapping between the identifiers of the IP disks and their corresponding interface types. Therefore, the processor can query the interface library to obtain interface types of different types of IP disks, and communicate with IP disks of different interface types.
  • IP hard disks The unified management of the disk, and the user can communicate with the processor through the client to store the data in different types of IP hard disks, which is equivalent to providing a unified interface form for the user, so that the application of the IP hard disk is more extensive.
  • FIG. 3 is a flowchart of a method for managing an IP hard disk according to Embodiment 2 of the present invention. This embodiment is a detailed description of the method embodiment shown in FIG. 2, which is performed by the processor in FIG. 1, as shown in FIG. 3, the method includes the following steps:
  • Step 201 Receive a resource request sent by a client.
  • the resource request includes data to be written, and length and attribute information of the data to be written.
  • the step of “determining the identifier of the one or more target IP hard disks to be written according to the length of the data to be written and the attribute information” may further include the step 202, and step 203 can be used instead of step 102 in FIG.
  • Step 202 Determine, according to the correspondence between the client identifier and the identifier of the client identifier and the identifier of the user resource pool, the identifier of the target user resource pool corresponding to the client identifier; the target user resource pool includes one or more target IP hard disks.
  • the processor may further create a user resource pool for the client according to the resource request, and the user resource pool may include one type of IP hard disk, or may include different types of IP hard disks.
  • FIG. 4 is a schematic diagram of a form of a user resource pool provided by the present invention
  • FIG. 5 is a schematic diagram of another user resource pool provided by the present invention
  • FIG. 6 is a schematic diagram of another form of a user resource pool provided by the present invention.
  • the user resource pool includes one type of IP hard disk.
  • the user resource pool includes at least two child resource pools, and each of the child resource pools includes one type of IP hard disk.
  • the user resource pool includes at least two types of IP hard disks.
  • Step 203 Determine an identifier of one or more target IP hard disks from the target user resource pool according to the length of the data to be written and the attribute information.
  • step 203 may include the following steps:
  • Step 2031 Perform a fragmentation process on the data to be written according to the length of the data to be written and the attribute information.
  • Step 2032 Perform hash calculation on each fragment data to generate a keyword for each fragment data.
  • Step 2033 Determine, according to the keyword of each fragmentation data, an identifier of the corresponding target IP hard disk for each fragmentation data.
  • Step 204 Send a reserved operation instruction to one or more target IP hard disks, where the reserved operation instruction is used to indicate that the target IP hard disk reserves storage resources for the client.
  • step 204 is an optional step, and step 205 may also be directly performed after step 203.
  • Step 205 Determine an interface type of the target IP hard disk according to the identifier of the target IP hard disk and the interface library.
  • the interface library stores the correspondence between the identifiers of the IP disks and their corresponding interface types.
  • Step 206 Convert the data to be written into a data protocol corresponding to the interface type.
  • Step 207 and sending the data protocol to the target IP hard disk.
  • the data in the target IP hard disk may also be read, including the following steps:
  • Step 208 Receive a read data request sent by the client.
  • the read data request includes a keyword and a client identifier of the data to be read.
  • Step 209 Determine, according to the correspondence between the client identifier and the identifier of the client identifier and the identifier of the user resource pool, the identifier of the target user resource pool corresponding to the client identifier.
  • Step 210 Obtain a keyword of each fragment data according to a keyword of the data to be read, and determine each from the target user resource pool according to the correspondence between the keyword of the fragment data and the identifier of the IP hard disk. The identifier of the target IP hard disk corresponding to the keyword of the fragmentation data.
  • Step 211 Send a read command to each target IP hard disk.
  • Step 212 Receive fragment data sent by each target IP hard disk.
  • Step 213 Assemble all the fragment data into data to be read, and send the data to be read to the client.
  • the user sends a resource request to the IP hard disk controller through the client, and the processor queries the target user resource pool identifier according to the client identifier in the resource request, according to the length and attributes of the data to be written.
  • the information is used to determine the identifier of one or more target IP hard disks from the target user resource pool, and send a reservation operation instruction to one or more target IP hard disks, indicating that the target IP hard disk reserves storage resources for the client, and is to be written.
  • the data is converted into a data protocol corresponding to the interface type and then sent to the target IP hard disk, and the user can read the data through the IP hard disk controller to the target IP hard disk, so that the data can be stored in different types of IP hard disks, and
  • the storage process is simple and the storage efficiency is high.
  • FIG. 7 is a schematic structural diagram of an apparatus for managing an IP hard disk according to Embodiment 3 of the present invention.
  • the apparatus includes a receiving module 11, a processing module 12, and a transmitting module 13.
  • the receiving module 11 receives the resource request sent by the client, where the resource request includes the data to be written, and the length and attribute information of the data to be written.
  • the processing module 12 is configured to determine the to-be-written according to the length of the data to be written and the attribute information.
  • the identifier of one or more target IP hard disks; the interface type of the target IP hard disk is determined according to the identifier of the target IP hard disk and the interface library, and the correspondence between the identifiers of the IP hard disks and their corresponding interface types is saved in the interface library;
  • the data to be written is converted into a data protocol corresponding to the interface type;
  • the sending module 13 is configured to send the data protocol to the target IP hard disk.
  • the device in this embodiment can be used to implement the technical solution of the method embodiment shown in FIG. 2, and the implementation principle and the friendship effect are similar, and details are not described herein again.
  • the processing module 12 is further configured to determine, according to the client identifier and the correspondence between the client identifier and the identifier of the user resource pool, the target user resource pool corresponding to the client identifier.
  • the identifier of the target user resource pool includes one or more target IP hard disks; the processing module 12 determines the identifier of the one or more target IP hard disks to be written according to the length of the data to be written and the attribute information, including: the processing module 12
  • the identifiers of one or more target IP hard disks are determined from the target user resource pool according to the length of the data to be written and the attribute information.
  • the sending module 13 is further configured to send a reserved operation instruction to the one or more target IP hard disks, where the reserved operation instruction is used to indicate that the target IP hard disk reserves storage resources for the client.
  • the processing module 12 determines the identifiers of the plurality of target IP hard disks to be written according to the length of the data to be written and the attribute information, including: the processing module 12 processes the data according to the length of the data to be written and the attribute information. Performing fragmentation processing; performing hash calculation on each fragmentation data to generate keywords of each fragmentation data; determining, according to keywords of each fragmentation data, identifiers of corresponding target IP hard disks for each fragmentation data .
  • the device of this embodiment can be used to implement the technical solution of the method embodiment shown in FIG. 3, and the implementation principle and the beneficial effects are similar, and details are not described herein again.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the steps of the foregoing method embodiments are performed; and the foregoing storage medium includes: Read-Only Memory (ROM), random A medium that can store program code, such as a random access memory (RAM), a magnetic disk, or an optical disk.

Landscapes

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

Abstract

一种IP硬盘的管理方法和装置，该方法包括：接收客户端发送的资源请求，所述资源请求包括待写入数据，以及所述待写入数据的长度和属性信息（S101）；根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识（S102）；分别根据所述目标IP硬盘的标识以及接口库确定所述目标IP硬盘的接口类型，所述接口库中保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系（S103）；将所述待写入数据转化为与所述接口类型对应的数据协议（S104）；将所述数据协议发送给所述目标IP硬盘（S105）。所述IP硬盘管理方法，向用户提供统一的IP硬盘的接口形式，并实现了IP硬盘的统一管理，使得IP硬盘得到更加广泛的应用。

Description

IP硬盘的管理方法和装置 技术领域
本发明实施例涉及通信技术，尤其涉及一种IP硬盘的管理方法和装置。
背景技术
互联网协议(Internet Protocol，简称IP)硬盘是一种提供以太网接口、采用传输控制协议(Transmission Control Protocol，简称TCP)/IP直接与上层网络进行通信、并提供对象存储服务的硬盘。
与普通的串行高级技术附件(Serial Advanced Technology Attachment，简称SATA)盘或者串行连接小型计算机系统接口(Serial Attached Small Computer System Interface，简称SAS)盘不同的是，IP硬盘对外只提供key/value接口，用户只需要向IP硬盘提供key/value健值即可实现数据的存取，而不需要关心数据在磁盘中具体的逻辑区块地址(Logical Block Address，简称LBA)，使得IP硬盘大大简化了存储系统的架构。
目前，不同厂家生产的IP硬盘的具体实现方式均有所不同，例如，一种IP硬盘的具体实现方式是，在每个硬盘的磁盘驱动器上前置一个转接板(Dongle)，该转接板相当于一个基于ARM处理器的小型存储控制器(Mini Storage Controller)，具有独立的内存，通过该转接板将一块传统的Block形式的磁盘变成了一块以对象(Object)形式访问的IP磁盘。为了面向用户，各厂家基于自家生产的IP硬盘搭建一个开放式存存储平台，该存储平台用于管理和适配自家生产的IP硬盘，并向用户提供对应的接口形式，但该存储平台不能适配其它厂家生产的IP硬盘。例如，希捷的kinetic存储平台就是基于kinetic IP硬盘搭建起来的存储平台，只能适配kinetic IP硬盘，不兼容其它厂家的IP硬盘。
由于不同厂家生产的IP硬盘的接口形式各有差异，而且，目前业界内也没有统一的标准可以适配不同的IP硬盘，因此，不能向用户提供统一的IP硬盘的接口形式，也无法实现IP硬盘的统一管理，导致IP硬盘的应用受到了很大的局限性。
发明内容
本发明实施例提供一种IP硬盘的管理方法和装置，向用户提供统一的IP硬盘的接口形式，并实现了IP硬盘的统一管理，使得IP硬盘得到更加广泛的应用。
第一方面，本发明实施例提供一种IP硬盘的管理方法，所述存储系统包括多个IP硬盘和至少一个IP硬盘控制器，所述IP硬盘控制器包括处理器和存储器，所述方法由所述处理器执行，包括：接收客户端发送的资源请求，所述资源请求包括待写入数据，以及所述待写入数据的长度和属性信息；根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识；分别根据所述目标IP硬盘的标识以及接口库确定所述目标IP硬盘的接口类型，所述接口库中保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系；将所述待写入数据转化为与所述接口类型对应的数据协议；将所述数据协议发送给所述目标IP硬盘。本实施例中，由于接口库保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系，因此，处理器可以查询接口库获取不同类型的IP硬盘的接口类型，与不同接口类型的IP硬盘进行通信，从而实现不同类型IP硬盘的统一管理，而且，用户通过客户端与处理器通信即可将数据存储在不同类型的IP硬盘中，相当于向用户提供统一的接口形式，使得IP硬盘的应用更加的广泛。本实施例的装置，可用于执行第一方面的第二种可能实现方式提供的方法技术方案，其实现原理和有益效果类似，此处不再赘述。
结合第一方面，在第一方面的第一种可能实现方式中，所述资源请求还包括客户端标识，则所述根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识之前，所述方法还包括：根据所述客户端标识以及客户端标识与用户资源池的标识之间的对应关系，确定所述客户端标识对应的目标用户资源池的标识；所述目标用户资源池包括所述一个或多个目标IP硬盘；则所述根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识，包括：根据所述待写入数据的长度和属性信息，从所述目标用户资源池中确定所述一个或多个目标IP硬盘的标识。本实施例中，处理器从预先为客户端创建的用户资源池中选择目标IP硬盘，缩小了查 询IP硬盘的范围，有效提高了写数据的速率。
结合第一方面或第一方面的第一种可能实现方式，在第一方面的第二种可能实现方式中，所述根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识之后，所述方法还包括：向所述一个或多个目标IP硬盘发送预留操作指令，所述预留操作指令用于指示所述目标IP硬盘为所述客户端预留存储资源。本实施例中，处理器在写入数据之前，先向目标IP硬盘发送预留操作指令，使得目标IP硬盘为待写入数据预留存储资源，避免了由于其它的数据占用目标IP硬盘而导致本次写数据失败的现象。
结合第一方面的任一种可能实现方式，在第一方面的第三种可能实现方式中，所述根据所述待写入数据的长度和属性信息确定待写入的多个目标IP硬盘的标识，包括：根据所述待写入数据的长度和属性信息，对所述待写入数据进行分片处理；分别对每个分片数据进行哈希计算生成所述每个分片数据的关键字；根据所述每个分片数据的关键字，为所述每个分片数据确定对应的目标IP硬盘的标识。本实施例中，将待写入数据分片存储在多个目标IP硬盘中，存储速度快，存储效率高。
第二方面，本发明实施例提供一种IP硬盘的管理装置，包括：接收模块，接收客户端发送的资源请求，所述资源请求包括待写入数据，以及所述待写入数据的长度和属性信息；处理模块，用于根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识；分别根据所述目标IP硬盘的标识以及接口库确定所述目标IP硬盘的接口类型，所述接口库中保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系；将所述待写入数据转化为与所述接口类型对应的数据协议；发送模块，用于将所述数据协议发送给所述目标IP硬盘。本实施例的装置，可用于执行第一方面提供的方法技术方案，其实现原理和有益效果类似，此处不再赘述。
结合第二方面，在第二方面的第一种可能实现方式中，若所述资源请求还包括客户端标识，则所述处理模块还用于根据所述客户端标识以及客户端标识与用户资源池的标识之间的对应关系，确定所述客户端标识对应的目标用户资源池的标识；所述目标用户资源池包括所述一个或多个目标IP硬盘；则所述处理模块根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识，包括：所述处理模块根据所述待写入数据的长度和 属性信息，从所述目标用户资源池中确定所述一个或多个目标IP硬盘的标识。本实施例的装置，可用于执行第一方面的第一种可能实现方式提供的方法技术方案，其实现原理和有益效果类似，此处不再赘述。
结合第二方面或第二方面的第一种可能实现方式，在第二方面的第二种可能实现方式中所述发送模块还用于向所述一个或多个目标IP硬盘发送预留操作指令，所述预留操作指令用于指示所述目标IP硬盘为所述客户端预留存储资源。本实施例的装置，可用于执行第一方面的第二种可能实现方式提供的方法技术方案，其实现原理和有益效果类似，此处不再赘述。
结合第二方面的任一种可能实现方式，在第二方面的第三种可能实现方式中，所述处理模块根据所述待写入数据的长度和属性信息确定待写入的多个目标IP硬盘的标识，包括：所述处理模块根据所述待写入数据的长度和属性信息，对所述待写入数据进行分片处理；分别对每个分片数据进行哈希计算生成所述每个分片数据的关键字；根据所述每个分片数据的关键字，为所述每个分片数据确定对应的目标IP硬盘的标识。本实施例的装置，可用于执行第一方面的第三种可能实现方式提供的方法技术方案，其实现原理和有益效果类似，此处不再赘述。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的IP硬盘的管理方法的应用场景示意图；
图2为本发明实施例一提供的IP硬盘的管理方法的流程图；
图3为本发明实施例二提供的IP硬盘的管理方法的流程图；
图4为本发明提供的一种用户资源池的形态示意图；
图5为本发明提供的另一种用户资源池的形态示意图；
图6为本发明提供的再一种用户资源池的形态示意图；
图7为本发明实施例三提供的IP硬盘的管理装置的结构示意图。
具体实施方式
本发明实施例涉及的方法，旨在解决现有技术中的IP硬盘管理方法不能向用户提供统一的IP硬盘的接口形式，也无法实现IP硬盘的统一管理，导致IP硬盘的应用受到了很大的局限性这一技术问题。
下面以具体地实施例对本发明的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例不再赘述。
图1为本发明实施例提供的IP硬盘的管理方法的应用场景示意图。该场景为一个存储系统，如图1所示，该存储系统包括至少IP硬盘控制器和多个IP硬盘，其中，IP硬盘控制器可以为服务器、计算机等设备，IP硬盘控制器包括处理器1和存储器6，存储器6用于存储接口库2和接口库3，IP硬盘4和IP硬盘5是两种接口类型不相同的IP硬盘。
处理器1可能是一个中央处理器(Central Processing Unit，简称CPU)，或者是专用集成电路(Application Specific Integrated Circuit，简称ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路。在本发明实施例中，处理器1可用于接收来自客户端发送的资源请求和读数据请求，并对所述资源请求和读数据请求进行处理后发送给IP硬盘以及执行其它操作。
存储器6，用于存放程序指令以及相关数据，存储器6可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。可以理解的是，存储器6可以为随机存储器(Random-Access Memory，RAM)、磁碟、硬盘、光盘、固态硬盘(Solid State Disk，SSD)或者非易失性存储器等各种可以存储程序代码的非短暂性的(non-transitory)机器可读介质。在本发明实施例中，存储器6可用于存储相关的程序指令、接口库等。
接口库为文件夹、数据库、表格等形式的存储文件或者是用于查询数据的软件程序，接口库包括IP硬盘的标识与其对应的接口类型之间的对应关系，每个接口库对应一种接口类型的IP硬盘，接口库还可以记录对应接口类型的IP硬盘的数目以及增加、删减等信息。IP硬盘的接口类型可以为小型计算机系统接口(Small Computer System Interface，简称SCSI)、串行连接SCSI接口(Serial Attached SCSI，简称SAS)等。
图2为本发明实施例一提供的IP硬盘的管理方法的流程图。本实施例的方法应用于图1所示的场景中，并且，该方法由图1中的处理器执行，如图2所示，该方法包括以下步骤：
步骤101、接收客户端发送的资源请求，资源请求包括待写入数据，以及待写入数据的长度和属性信息。
在本实施例中，待写入数据的长度用于判断存储待写入数据需要多大容量的存储空间，待写入数据的数据信息包括文字、图片、音频、视频等。
步骤102、根据待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识。
在本实施例中，处理器根据待写入数据的属性信息判断存储该数据所需的IP硬盘的类型，根据待写入数据的长度判断存储该数据所需的相应类型的IP硬盘的数量，从而确定出一个或多个目标IP硬盘的标识。
步骤103、分别根据目标IP硬盘的标识以及接口库确定目标IP硬盘的接口类型，接口库中保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系。
在本实施例中，由于不同类型的IP硬盘的接口形式不相同，在确定IP硬盘的类型之后，处理器需要查询接口库，获取与目标IP硬盘的标识对应的接口类型。其中，接口库可以为文件夹、数据库、表格等形式。
步骤104、将待写入数据转化为与接口类型对应的数据协议。
步骤105、将数据协议发送给目标IP硬盘。
在本实施例中，处理器将待写入数据转化为与目标IP的接口类型对应的数据协议之后，发送给目标IP硬盘，保证IP硬盘可以对数据协议正确解析，存储数据。
本实施例提供的IP硬盘的管理方法，处理器接收客户端发送的资源请求，根据资源请求中的待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识，分别根据目标IP硬盘的标识以及接口库确定目标IP硬盘的接口类型，将待写入数据转化为与接口类型对应的数据协议，将数据协议发送给目标IP硬盘。由于接口库保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系，因此，处理器可以查询接口库获取不同类型的IP硬盘的接口类型，与不同接口类型的IP硬盘进行通信，从而实现不同类型IP硬 盘的统一管理，而且，用户通过客户端与处理器通信即可将数据存储在不同类型的IP硬盘中，相当于向用户提供统一的接口形式，使得IP硬盘的应用更加的广泛。
图3为本发明实施例二提供的IP硬盘的管理方法的流程图。本实施例的是对图2所示方法实施例的详细说明，该方法由图1中的处理器执行，如图3所示，该方法包括以下步骤：
步骤201、接收客户端发送的资源请求。
其中，资源请求包括待写入数据，以及待写入数据的长度和属性信息。
可选地，若资源请求中还包括客户端标识，则步骤“根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识”之前，还可以包括步骤202，并且，可以用步骤203代替图1中的步骤102。
步骤202、根据客户端标识以及客户端标识与用户资源池的标识之间的对应关系，确定客户端标识对应的目标用户资源池的标识；目标用户资源池包括一个或多个目标IP硬盘。
在本实施例中，处理器还可以根据资源请求为客户端创建用户资源池，该用户资源池可以包括一种类型的IP硬盘，也可以包括不同类型的IP硬盘。图4为本发明提供的一种用户资源池的形态示意图，图5为本发明提供的另一种用户资源池的形态示意图，图6为本发明提供的再一种用户资源池的形态示意图。如图4所示，该用户资源池包括一种类型的IP硬盘。如图5所示，该用户资源池包括至少两个子资源池，每个子资源池包括一种类型的IP硬盘。如图6所示，该用户资源池包括至少两种类型的IP硬盘。
步骤203、根据待写入数据的长度和属性信息，从目标用户资源池中确定一个或多个目标IP硬盘的标识。
可选地，步骤203的实现方式可以包括以下步骤：
步骤2031、根据待写入数据的长度和属性信息，对待写入数据进行分片处理；
步骤2032、分别对每个分片数据进行哈希计算生成每个分片数据的关键字；
步骤2033、根据每个分片数据的关键字，为每个分片数据确定对应的目标IP硬盘的标识。
步骤204、向一个或多个目标IP硬盘发送预留操作指令，预留操作指令用于指示目标IP硬盘为客户端预留存储资源。
需要说明的是，步骤204为一个可选的步骤，在步骤203之后也可以直接执行步骤205。
步骤205、分别根据目标IP硬盘的标识以及接口库确定目标IP硬盘的接口类型。
其中，接口库中保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系。
步骤206、将待写入数据转化为与接口类型对应的数据协议。
步骤207、并将数据协议发送给目标IP硬盘。
可选地，将数据写入目标IP硬盘之后，还可以读取目标IP硬盘中的数据，具体包括如下步骤：
步骤208、接收客户端发送的读数据请求。
其中，读数据请求中包括待读取数据的关键字和客户端标识。
步骤209、根据客户端标识以及客户端标识与用户资源池的标识之间的对应关系，确定客户端标识对应的目标用户资源池的标识。
步骤210、根据待读取数据的关键字获取每个分片数据的关键字，并根据分片数据的关键字与IP硬盘的标识之间的对应关系，从目标用户资源池中分别确定每个分片数据的关键字对应的目标IP硬盘的标识。
步骤211、向每个目标IP硬盘发送读取指令。
步骤212、接收每个目标IP硬盘发送的分片数据。
步骤213、将所有的分片数据组装为待读取数据，并将待读取数据发送给客户端。
本实施例提供的IP硬盘的管理方法，用户通过客户端向IP硬盘控制器发送资源请求，处理器根据资源请求中的客户端标识查询目标用户资源池标识，根据待写入数据的长度和属性信息，从目标用户资源池中确定一个或多个目标IP硬盘的标识，并向一个或多个目标IP硬盘发送预留操作指令，指示目标IP硬盘为客户端预留存储资源，将待写入数据转化为与接口类型对应的数据协议后发送给目标IP硬盘，并且，用户可以通过IP硬盘控制器才目标IP硬盘中读取数据，可以实现将数据存储在不同类型的IP硬盘中，而且， 存储过程简单，存储效率高。
图7为本发明实施例三提供的IP硬盘的管理装置的结构示意图。如图7所示，该装置包括接收模块11、处理模块12和发送模块13。接收模块11接收客户端发送的资源请求，资源请求包括待写入数据，以及待写入数据的长度和属性信息；处理模块12用于根据待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识；分别根据目标IP硬盘的标识以及接口库确定目标IP硬盘的接口类型，接口库中保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系；将待写入数据转化为与接口类型对应的数据协议；发送模块13用于将数据协议发送给目标IP硬盘。
本实施例的装置，可用于执行图2所示方法实施例的技术方案，其实现原理和友谊效果类似，此处不再赘述。
可选地，若资源请求还包括客户端标识，则处理模块12还用于根据客户端标识以及客户端标识与用户资源池的标识之间的对应关系，确定客户端标识对应的目标用户资源池的标识；目标用户资源池包括一个或多个目标IP硬盘；则处理模块12根据待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识，包括：处理模块12根据待写入数据的长度和属性信息，从目标用户资源池中确定一个或多个目标IP硬盘的标识。
可选地，发送模块13还用于向一个或多个目标IP硬盘发送预留操作指令，预留操作指令用于指示目标IP硬盘为客户端预留存储资源。
可选地，处理模块12根据待写入数据的长度和属性信息确定待写入的多个目标IP硬盘的标识，包括：处理模块12根据待写入数据的长度和属性信息，对待写入数据进行分片处理；分别对每个分片数据进行哈希计算生成每个分片数据的关键字；根据每个分片数据的关键字，为每个分片数据确定对应的目标IP硬盘的标识。
本实施例的装置，可用于执行图3所示方法实施例的技术方案，其实现原理和有益效果类似，此处不再赘述。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：只读存储器(Read-Only Memory，简称ROM)、随机 存取存储器(random access memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (8)

  1. 一种管理存储系统中的IP硬盘的方法，其特征在于，所述存储系统包括多个IP硬盘和至少一个IP硬盘控制器，所述IP硬盘控制器包括处理器和存储器，所述方法由所述处理器执行，包括：
    接收客户端发送的资源请求，所述资源请求包括待写入数据，以及所述待写入数据的长度和属性信息；
    根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识；
    分别根据所述目标IP硬盘的标识以及接口库确定所述目标IP硬盘的接口类型，所述接口库中保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系；
    将所述待写入数据转化为与所述接口类型对应的数据协议；
    将所述数据协议发送给所述目标IP硬盘。
  2. 根据权利要求1所述的方法，其特征在于，所述资源请求还包括客户端标识，则所述根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识之前，所述方法还包括：
    根据所述客户端标识以及客户端标识与用户资源池的标识之间的对应关系，确定所述客户端标识对应的目标用户资源池的标识；所述目标用户资源池包括所述一个或多个目标IP硬盘；
    则所述根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识，包括：
    根据所述待写入数据的长度和属性信息，从所述目标用户资源池中确定所述一个或多个目标IP硬盘的标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识之后，所述方法还包括：
    向所述一个或多个目标IP硬盘发送预留操作指令，所述预留操作指令用于指示所述目标IP硬盘为所述客户端预留存储资源。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述根据所述待写入数据的长度和属性信息确定待写入的多个目标IP硬盘的标识，包括：
    根据所述待写入数据的长度和属性信息，对所述待写入数据进行分片处理；
    分别对每个分片数据进行哈希计算生成所述每个分片数据的关键字；
    根据所述每个分片数据的关键字，为所述每个分片数据确定对应的目标IP硬盘的标识。
  5. 一种互联网协议IP硬盘的管理装置，其特征在于，包括：
    接收模块，接收客户端发送的资源请求，所述资源请求包括待写入数据，以及所述待写入数据的长度和属性信息；
    处理模块，用于根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识；分别根据所述目标IP硬盘的标识以及接口库确定所述目标IP硬盘的接口类型，所述接口库中保存有各个IP硬盘的标识与其对应的接口类型之间的对应关系；将所述待写入数据转化为与所述接口类型对应的数据协议；
    发送模块，用于将所述数据协议发送给所述目标IP硬盘。
  6. 根据权利要求5所述的装置，其特征在于，若所述资源请求还包括客户端标识，则所述处理模块还用于根据所述客户端标识以及客户端标识与用户资源池的标识之间的对应关系，确定所述客户端标识对应的目标用户资源池的标识；所述目标用户资源池包括所述一个或多个目标IP硬盘；
    则所述处理模块根据所述待写入数据的长度和属性信息确定待写入的一个或多个目标IP硬盘的标识，包括：
    所述处理模块根据所述待写入数据的长度和属性信息，从所述目标用户资源池中确定所述一个或多个目标IP硬盘的标识。
  7. 根据权利要求5或6所述的装置，其特征在于，所述发送模块还用于向所述一个或多个目标IP硬盘发送预留操作指令，所述预留操作指令用于指示所述目标IP硬盘为所述客户端预留存储资源。
  8. 根据权利要求5-7任一项所述的装置，其特征在于，所述处理模块根据所述待写入数据的长度和属性信息确定待写入的多个目标IP硬盘的标识，包括：
    所述处理模块根据所述待写入数据的长度和属性信息，对所述待写入数据进行分片处理；分别对每个分片数据进行哈希计算生成所述每个分片数据的关键字；根据所述每个分片数据的关键字，为所述每个分片数据确定对应的目标IP硬盘的标识。
PCT/CN2016/087917 2015-11-20 2016-06-30 Ip硬盘的管理方法和装置 WO2017084348A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510808475.8 2015-11-20
CN201510808475.8A CN105468300B (zh) 2015-11-20 2015-11-20 Ip硬盘的管理方法和装置

Publications (1)

Publication Number Publication Date
WO2017084348A1 true WO2017084348A1 (zh) 2017-05-26

Family

ID=55606053

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/087917 WO2017084348A1 (zh) 2015-11-20 2016-06-30 Ip硬盘的管理方法和装置

Country Status (2)

Country Link
CN (1) CN105468300B (zh)
WO (1) WO2017084348A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112256204A (zh) * 2020-10-28 2021-01-22 重庆紫光华山智安科技有限公司 存储资源分配方法、装置、存储节点及存储介质
CN113821467A (zh) * 2021-09-29 2021-12-21 广联达科技股份有限公司 数据传输方法、装置及电子设备

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107436725B (zh) 2016-05-25 2019-12-20 杭州海康威视数字技术股份有限公司 一种数据写、读方法、装置及分布式对象存储集群
CN109101186A (zh) * 2017-06-20 2018-12-28 上海宝存信息科技有限公司 数据储存装置与数据储存方法
CN108646981B (zh) * 2018-04-28 2021-09-03 深圳市茁壮网络股份有限公司 一种数据缓存节点管理方法、数据缓存方法和缓存管理节点
CN109669633B (zh) * 2018-12-17 2021-11-09 郑州云海信息技术有限公司 一种分布式存储系统的磁盘控制方法、装置、设备及介质
CN114116560A (zh) * 2020-08-31 2022-03-01 华为技术有限公司 一种信息交互方法及装置
CN115061958A (zh) * 2022-07-05 2022-09-16 中国长城科技集团股份有限公司 一种硬盘识别方法、识别系统、存储介质和计算机设备
CN115495398B (zh) * 2022-09-28 2023-06-30 北京亚控科技发展有限公司 接口资源操作方法、装置、电子设备、存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070197100A1 (en) * 2006-02-17 2007-08-23 Robert Tsao Type of hard disk interface device
US8146027B1 (en) * 2009-05-07 2012-03-27 Xilinx, Inc. Creating interfaces for importation of modules into a circuit design
CN104007938A (zh) * 2014-05-29 2014-08-27 华为技术有限公司 在存储网络中的键值生成方法及装置
CN104077374A (zh) * 2014-06-24 2014-10-01 华为技术有限公司 一种实现ip盘文件存储的方法及装置
CN105068948A (zh) * 2015-07-02 2015-11-18 华为技术有限公司 存储盘及存储盘的设置方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7369570B2 (en) * 2003-03-03 2008-05-06 Nec Corporation iSCSI apparatus and communication control method for the same
CN103973810B (zh) * 2014-05-22 2018-01-16 华为技术有限公司 基于互联网协议ip盘的数据处理方法和装置
CN104238963B (zh) * 2014-09-30 2017-08-11 华为技术有限公司 一种数据存储方法、存储装置及存储系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070197100A1 (en) * 2006-02-17 2007-08-23 Robert Tsao Type of hard disk interface device
US8146027B1 (en) * 2009-05-07 2012-03-27 Xilinx, Inc. Creating interfaces for importation of modules into a circuit design
CN104007938A (zh) * 2014-05-29 2014-08-27 华为技术有限公司 在存储网络中的键值生成方法及装置
CN104077374A (zh) * 2014-06-24 2014-10-01 华为技术有限公司 一种实现ip盘文件存储的方法及装置
CN105068948A (zh) * 2015-07-02 2015-11-18 华为技术有限公司 存储盘及存储盘的设置方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112256204A (zh) * 2020-10-28 2021-01-22 重庆紫光华山智安科技有限公司 存储资源分配方法、装置、存储节点及存储介质
CN112256204B (zh) * 2020-10-28 2022-06-03 重庆紫光华山智安科技有限公司 存储资源分配方法、装置、存储节点及存储介质
CN113821467A (zh) * 2021-09-29 2021-12-21 广联达科技股份有限公司 数据传输方法、装置及电子设备

Also Published As

Publication number Publication date
CN105468300B (zh) 2018-08-14
CN105468300A (zh) 2016-04-06

Similar Documents

Publication Publication Date Title
WO2017084348A1 (zh) Ip硬盘的管理方法和装置
US9692823B2 (en) Inter-protocol copy offload
EP2932692B1 (en) Compatibly extending offload token size
CN104020961A (zh) 分布式数据存储方法、装置及系统
US10812599B2 (en) Method and system for creating virtual non-volatile storage medium, and management system
WO2018233630A1 (zh) 故障发现
WO2016066108A1 (zh) 路由访问方法、路由访问系统及用户终端
KR102263357B1 (ko) 분산 파일시스템 환경에서 사용자 수준 dma i/o를 지원하는 시스템 및 그 방법
US10126969B1 (en) Mechanism for non-disruptive virtual tape libraries removal and reconfiguration
US10901621B2 (en) Dual-level storage device reservation
WO2015180650A1 (zh) 在存储网络中的键值生成方法及装置
US9432329B2 (en) Network address assignment with duplication detection
WO2016188373A1 (zh) 存储系统中融合san及nas存储架构的方法及装置
WO2016101662A1 (zh) 一种数据处理方法及相关服务器
US10437849B2 (en) Method and apparatus for implementing storage of file in IP disk
CN105162833B (zh) 应用于无盘工作站的客户机管理系统及方法
US11194771B2 (en) Methods for transferring reserves when moving virtual machines across systems
WO2016095644A1 (zh) 数据库的高可用解决方法和装置
US9648103B2 (en) Non-uniform file access in a distributed file system
US20150261524A1 (en) Management pack service model for managed code framework
KR20150139546A (ko) 탈착가능형 저장 디바이스 아이덴티티 및 구성 정보
JP2018536247A (ja) クラウドベースのセッション管理システム
WO2023273803A1 (zh) 一种认证方法、装置和存储系统
WO2014077451A1 (ko) Iscsi 스토리지 시스템을 이용한 네트워크 분산 파일 시스템 및 방법
US10769172B2 (en) Globalized object names in a global namespace

Legal Events

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

Ref document number: 16865528

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: 16865528

Country of ref document: EP

Kind code of ref document: A1