WO2010040255A1 - 对象存储***的管理方法 - Google Patents
对象存储***的管理方法 Download PDFInfo
- Publication number
- WO2010040255A1 WO2010040255A1 PCT/CN2008/072606 CN2008072606W WO2010040255A1 WO 2010040255 A1 WO2010040255 A1 WO 2010040255A1 CN 2008072606 W CN2008072606 W CN 2008072606W WO 2010040255 A1 WO2010040255 A1 WO 2010040255A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- function
- user
- command
- function object
- partition
- Prior art date
Links
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
- 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/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/062—Securing storage systems
-
- 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/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0643—Management of files
-
- 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/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F2213/0038—System on Chip
Definitions
- the present invention relates to the field of computer information storage, and in particular to access and management based on object storage devices.
- the technical problem to be solved by the present invention is to provide a method for managing an object storage system, which can support intelligent processing in a storage device, and provide an effective object storage access interface to support function decentralization and flexibility. Scheduling execution.
- the present invention provides a method for managing an object storage system, where the object storage system includes a client and a storage node, and an object-based storage device.
- An OBSD Object-Based Storage Device
- the OBSD stores a root object, a partition object, a collection object, and a user object
- the OBSD further stores a functional object
- the function object includes a user function object and a system function object; when the OBSD responds to the client's request for the user object, the OBSD calls the user function object to execute a client request command; the system function object reads the root object property page of the OBSD in real time; And system real-time status information of the object storage device, and determining whether the system is in a specific state according to the read status information, and if yes, executing a specific system management function set in the system function object.
- one of the functional objects is contained in only one of the partitioned objects, and one of the partitioned objects contains zero or more of the functional objects.
- the user function object may be associated with zero or more user objects, and the association method is: setting a function object in a user object information property page
- the functional object ID (identifier) field in which the functional object ID is stored in the functional object ID field, and the functional object ID points to a specific functional object.
- scheduling execution of the read/write command of the object storage system includes the following steps:
- the command description block CDB of the read/write user object command sets the function object flag bit, and the value of the function object flag bit is "0" or "1" ; 5-2.
- the client sends a read/write user object command to the OBSD.
- OBSD reads the function object flag bit value in the CDB of the command description block, and judges the function object flag bit value; if the function object flag bit value is "0", no function object is called; if the function object flag bit When the value is "1", the function object ID in the user object information attribute page of the user object indicated by the user object ID is read according to the user object ID in the command description block CDB, and then the function object pointed to by the function object ID is called. Perform a read/write operation.
- the method further includes creating a user/system function object command, and the scheduling of the user/system function object command includes the following steps:
- the command description block in the create user/system function object command CDB sets the function object length field, the requested function object ID field, and the function object length field specifies the number of bytes of the function object content to be uploaded;
- the client issues a create user/system function object command to the OBSD, and simultaneously uploads the user/system function object content; the command data or the parameter data segment in which the user/system function object content to be created is encapsulated in the data output buffer. ;
- the OBSD reads the command description block CDB sent by the client. If the command describes that the requested function object ID field value in the block CDB is "0", the OBSD will arbitrarily assign a function object ID to the uploaded function object; If the function object ID field value of the request in the command description block CDB is not "0", the OBSD attempts to assign the function object ID to the user/system to be created on the basis that at least the following functional object ID assignment conditions are satisfied.
- the functional object, functional object ID assignment condition is: Within the same partition, the following conditions are not allowed: a) At a certain moment, the same functional object ID points to multiple functional objects; or b) functional object ID and an existing collection object The ID or user object ID is the same; if the requested function object ID field value is not "0" and the OBSD cannot assign the requested function object ID to the function object to be created, the function object will not be created and an error will be returned.
- the client issues a list command to the OBSD.
- OBSD read list command description block CDB if the value of the function object ID field in the command description block CDB is "0", then return all functions under the partition object pointed to by the partition object ID in the CDB of the command description block.
- Object ID if the value of the function object ID field in the command description block CDB is not "0", return the user object associated with the function object ID under the partition object pointed to by the partition object ID in the command description block CDB.
- ID If the functional object indicated by the functional object ID field does not exist, the command should be terminated in an abnormal state.
- the method further includes deleting a user/system function object command, and the scheduling of the delete user/system function object command includes the following steps:
- the command description block CDB of the delete user/system function object command sets the forced delete function object flag bit, the function object ID field, the partition object ID field, and the content of the function object ID field specifies the function object to be deleted, the partition object.
- the content of the ID field specifies the partition object to which the function object to be deleted belongs;
- the client sends a delete user/system function object command to the OBSD;
- the OBSD read command describes the block CDB. If the value of the partition object ID field is “0”, the function object indicated by the function object ID is deleted in the partition object specified by the partition object ID;
- the function object has a user object association and the value of the forced delete function object flag is "1", then all users associated with the function object are set.
- the user object information property page of the object is related to the user object
- the associated function object ID attribute value is "0" to indicate that the user objects are no longer associated with the function object; and then the function object indicated by the function object ID is deleted in the partition object indicated by the partition object ID;
- the method for managing an object storage system further comprising: a first system function object, a second system function object, ..., an nth system function object, wherein the first The system function object reads the root object property page of the object storage device and the system real-time state information of the object storage device in real time, and determines whether the system state is in a specific state according to the read state information, and if so, schedules the second, ..., nth System function objects in the system perform specific system management functions.
- the object storage system management method provided by the invention expands the storage object (OSD object) in the OBSD on the T10 OSD standard, newly defines the system function object and the user function object, and expands the access of the object storage device.
- the command set which supports intelligent processing in storage devices, provides an effective object storage access interface to support functional decentralization and flexible scheduling execution.
- the user function object in the present invention responds to the client request, performs the operation requested by the client, and moves the data processing task undertaken by the existing client to the object storage device to save network storage bandwidth and improve the security of the stored data. purpose.
- the system function object performs system management functions, and the underlying disk management of the file system and the database system is completed by the object storage device, and the functions of automatic data backup, hotspot migration, load balancing, and the like can be easily implemented in the storage system.
- User functional objects and system functional objects can be customized by the user.
- the invention changes the data management and processing mode of the traditional storage system and improves the performance of the storage system.
- Figure 1 Schematic diagram of the object storage system architecture.
- Figure 2 Schematic diagram of object distribution on the object storage device.
- Figure 3 Schematic diagram of the client's read command in the object storage system.
- Figure 4 Flow diagram of the client issuing a write command in the object storage system.
- FIG. Schematic diagram of the scheduling of the system function object to implement the self-management function. detailed description
- the present invention is based on, but not limited to, the T10 OSD standard.
- the root object, the partition object, the collection object, and the user object are defined in the T10 OSD standard, and there is no reference to how to operate the object.
- the functional object is a piece of executable code, and the code language can be c, c++, JAVA, etc., which is identified by the functional object ID.
- Functional objects include user functional objects and system functional objects.
- the client sends a read/write command to the device
- the command contains the function object flag parameter
- the corresponding user function object can be called to execute.
- the user function object is called during the read operation, and the data can be processed before being returned to the application client.
- the file directory query operation is decentralized to the device side, so that the data is processed nearby, avoiding large network delays and making full use of the processing power of the device.
- the user function object execution is called during the write operation, and the data can be better saved. For example, compressing storage, or encrypting data, ensures that the data on the disk is not known to others even if the disk that holds the data is lost.
- the system function object is used for management purposes. After running, the OSD can be managed autonomously, such as automatic data backup, automatic load balancing, and mining rules from attributes.
- FIG. 1 is a schematic structural view of a storage system of the present invention.
- the figure includes a series of application clients Client l ... Clientn, a series of storage node devices 0BSD1, OBSD2, ..., OBSDn, a metadata server MDS (Metadata Server) cluster and a high-speed interconnection network, application customers There is a metadata channel connection between the end and the MDS cluster, wherein the metadata server cluster can be virtualized on the client or the storage device by using the software module.
- the client first sends an operation request command to the object to the metadata server, and the metadata server is negative. Responsibilities: 1. Mapping of file ID to object ID; 2. Device ID of the requested file; 3. Assigning a capability certificate to the requested operation command.
- the client After the metadata server feeds back the information to the client, the client directly uses the obtained object ID to directly initiate read and write access to the storage device OBSD. If the access needs to execute the corresponding functional object, the functional object flag will be included in the access parameter
- Each OSD (Object-Based Storage Device Commands) logical unit on the object storage device has a root object.
- the root object is the starting point for the positioning of an OSD logical unit structure, and the zero partition object represents the root object.
- the attributes of the root object contain the global characteristics of the system logic unit, such as the total capacity of the OSD logical unit and the number of partitions the system contains.
- the root object includes a list of all partition object identifiers and a list of all system function object identifiers.
- the system function object includes a first system function object, a second system function object, ..., an nth system function object, wherein the first system function object reads the root object attribute page in the object storage device and the system real-time status of the object storage device in real time.
- the information determines the system status based on the read status information, and schedules the system function objects in the second, ..., nth to perform system management functions.
- User function objects located under non-zero partition objects can be associated with zero or more user objects.
- the user function object under the non-zero partition object can be associated with a user object or with a user object. Disassociate.
- the attribute number of the function object ID attribute associated with the user object indicated by the user object ID is 3h, occupying 8
- a functional object belongs to only one partition object. Within a single partitioned object, the value of the functional object ID assigned to the functional object will be different from the value of any one of the collection object ID and the user object ID.
- FIG. 3 is a schematic flowchart of a client issuing a command in an object storage system.
- Figure 4 is a schematic flow chart of the client issuing a write command in the object storage system.
- Table 2 shows the CDB command format for the READ/WRITE command.
- the fifth bit in the 10th byte in Table 2, FUN indicates whether the corresponding functional object execution is to be called when the user object is read/written.
- the storage device checks the value of the FUN bit (ie, the functional object flag) in the command description block CDB defined in the T10 OSD standard. If the bit value is "1", it means that the user function object associated with the user object to be read/written is called.
- the ID of these user function objects can be queried by the user object information property page indicated by the user object ID, and the ID of the user object will be used as a parameter for the function object. If the value of the function object flag in the CDB is "0", it means that the corresponding function object execution is not called.
- step 101 is performed downward, and the client sends a user object command to the OBSD storage node.
- the OBSD determination command describes whether the FUN bit of the function object flag in the block CDB is "". 1"? If yes, step 103 is executed to read out the user function object ID associated with the user object in the user object information attribute page, and step 104, reading the user function object into the memory according to the ID of the user function object, step 105. Execute the user function object with the user object ID as a parameter, and step 106, return the result of execution or reading to the client, and then end. If the result of the OBSD judgment command description block CDB is "1", the process proceeds to step 107, and no function object is executed, and the user object is read. Data.
- the present invention also defines some functional pairs.
- the CREATE AND WRITE FUNCTION command is used to upload the executable code to the device side and create a functional object on the device.
- the LIST FUNCTION command lists the IDs of all functional objects in a partition object or the IDs of all user objects associated with the specified functional object.
- Create user/system function object command CREATE AND WRITE FUNCTION Scheduling includes the following specific steps:
- the FUNCTION command description block CDB sets the function object length field, the requested function object ID field, the function object length field specifies the number of bytes of the function object content to be uploaded, and the content of the requested function object ID field specifies that the content is to be created.
- the functional object ID of the functional object is as shown in Table 4 below: Table 4 CDB Command Format Bytes of the CREATE AND WRITE FUNCTION Command
- the client sends a command to create a user/system function object to the OBSD, and simultaneously uploads the content of the user/system function object; the command data or the parameter data segment in which the content of the user/system function object to be created is encapsulated in the data output buffer ;
- the OBSD reads the command description block CDB sent by the client. If the command describes that the requested function object ID field value in the block CDB is "0", the OBSD will arbitrarily assign a function object ID to the uploaded function object; If the function description ID field value of the request in the block description CDB is not "0", the OBSD attempts to assign the requested function object ID to the user to be created on the basis that at least the following functional object ID assignment conditions are satisfied.
- function object ID assignment condition is: Within the same partition, the following conditions are not allowed: a) At a certain moment, the same function object ID points to multiple function objects; or b) The function object ID and an existing one The collection object ID or the user object ID is the same; if the requested function object ID field value is not "0" and the OBSD cannot assign the requested function object ID to the function object to be created, the function object will not be created, The command terminates with the CHECK CONDITION state and sets the detection code to ILLEGAL
- the additional detection code is set to INVALID FIELD IN CDB.
- the scheduling of the list command LIST FUNCTION includes the following steps:
- the client issues a list command to the OBSD
- OBSD read list command description block CDB if the value of the function object ID field in the command description block CDB is "0", then return all functions under the partition object pointed to by the partition object ID in the CDB of the command description block Object ID; if the value of the function object ID field in the command description block CDB is not "0", return the user object associated with the function object ID under the partition object pointed to by the partition object ID in the command description block CDB. ID; If the function object indicated by the function object ID field does not exist, the command should be terminated in the CHECK CONDITION state, and the detection code is set to ILLEGAL REQUEST, and the additional detection code is set to INVALID FIELD IN CDB.
- the scheduling of deleting the user/system function object command includes the following steps: Cl, in the command description block CDB of the delete user/system function object command, the Force Function Removal (FFR) flag, the function object ID field, the partition object ID field, and the function object ID field specify the function to be deleted.
- FFR Force Function Removal
- Object the content of the partition object ID field specifies the partition object to which the function object to be deleted belongs, as shown in Table 6 below.
- the client sends a delete user/system function object command to the OBSD.
- C-3 The OBSD read command describes the block CDB. If the value of the partition object ID field is “0”, the function object indicated by the function object ID is deleted in the partition object specified by the partition object ID;
- a method of determining whether the function object ID is associated with the user object ID in addition to querying whether the user object information attribute page of the user object indicated by the user object ID exists
- an association mapping table of the functional object ID and the user object ID may also be established, and the user object ID associated with the functional object ID is found by querying the association mapping table.
- FIG. 5 is a schematic diagram of scheduling of a system function object implementing a self-management function.
- the first system function object under the zero partition object runs in real time in the OBSD, and reads the root object attribute page in the object storage device OBSD and the system real-time status information of the object storage device, and judges according to the read status information.
- System status when the system status meets the pre-set conditions of the system, the system function objects in the second, ..., nth are scheduled to perform system management functions.
- Table 7 The specific functions of each system function object are shown in Table 7 below: System function object list function
- the first system function object stores the system real-time status information of the device, and schedules the second system function object.
- the n system function object runs.
- the request for point data is transferred to the corresponding OBSD with lower access frequency.
- the nth system function object retains the object storage device OBSD in the root object property page to record the use of the entire system, including the root directory property page, the root information property page, the root quota property page, the root error recovery property page, etc., the root information property page content As shown in Table 8 below, the system information such as the total capacity and used capacity of the object storage system is recorded in Table 8.
- the real-time status information of the system records the real-time running status of the system, such as the usage of the CPU, the usage of the memory, etc. These real-time status information can be obtained directly from the system. For example, if you are running a Linux system on a storage device, you can get system information from /proc and /sysfs.
- the first system function object learns from the root object property page that the OBSD used capacity reaches 90% of the total OBSD capacity, and satisfies the system preset condition number 1, thereby scheduling the execution of the second system function object. Migrate the data on the OBSD to another OBSD.
- the first system function object Reading the real-time status information of the system, the length of the command request queue of the OBSD is greater than 10, and the condition number 2 preset by the system is satisfied, thereby scheduling the execution of the third system function object, and copying the hotspot data on the OBSD to another access.
- the request from the client for the hot data on the OBSD is transferred to the corresponding OBSD with lower access frequency.
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)
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2008/072606 WO2010040255A1 (zh) | 2008-10-07 | 2008-10-07 | 对象存储***的管理方法 |
CN200880014000XA CN101796514B (zh) | 2008-10-07 | 2008-10-07 | 对象存储***的管理方法 |
US13/063,934 US8645460B2 (en) | 2008-10-07 | 2008-10-07 | Method for managing object-based storage system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2008/072606 WO2010040255A1 (zh) | 2008-10-07 | 2008-10-07 | 对象存储***的管理方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010040255A1 true WO2010040255A1 (zh) | 2010-04-15 |
Family
ID=42100184
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2008/072606 WO2010040255A1 (zh) | 2008-10-07 | 2008-10-07 | 对象存储***的管理方法 |
Country Status (3)
Country | Link |
---|---|
US (1) | US8645460B2 (zh) |
CN (1) | CN101796514B (zh) |
WO (1) | WO2010040255A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9372854B2 (en) | 2010-11-08 | 2016-06-21 | Hewlett Packard Enterprise Development Lp | Load balancing backup jobs in a virtualized storage system having a plurality of physical nodes |
CN112241243A (zh) * | 2020-10-19 | 2021-01-19 | 北京计算机技术及应用研究所 | 一种主动对象存储***的实现方法 |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101453425B1 (ko) * | 2008-12-18 | 2014-10-23 | 한국전자통신연구원 | 메타데이터 서버 및 메타데이터 관리 방법 |
CN102202087B (zh) | 2011-04-25 | 2015-04-01 | 中兴通讯股份有限公司 | 一种标识存储设备的方法及*** |
US9424443B2 (en) * | 2013-08-20 | 2016-08-23 | Janus Technologies, Inc. | Method and apparatus for securing computer mass storage data |
CN103714022A (zh) * | 2014-01-13 | 2014-04-09 | 浪潮(北京)电子信息产业有限公司 | 一种基于数据块的混合存储*** |
US9639546B1 (en) | 2014-05-23 | 2017-05-02 | Amazon Technologies, Inc. | Object-backed block-based distributed storage |
CN106062717B (zh) * | 2014-11-06 | 2019-05-03 | 华为技术有限公司 | 一种分布式存储复制***和方法 |
CN105243112A (zh) * | 2015-09-25 | 2016-01-13 | 天脉聚源(北京)科技有限公司 | 对象索引化的控制方法和装置 |
US9870322B2 (en) | 2015-11-12 | 2018-01-16 | International Business Machines Corporation | Memory mapping for object-based storage devices |
US9740415B2 (en) | 2015-11-17 | 2017-08-22 | International Business Machines Corporation | Object-based storage management |
CN105573865A (zh) * | 2015-12-24 | 2016-05-11 | 创新科存储技术(深圳)有限公司 | 一种数据备份方法以及一种数据备份*** |
CN109491983B (zh) * | 2018-11-01 | 2021-08-31 | 郑州云海信息技术有限公司 | 一种数据信息的管理方法、装置和计算机可读存储介质 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006146904A (ja) * | 2004-11-17 | 2006-06-08 | Hitachi Ltd | ストレージシステムでオブジェクトレベルのスナップショットを生成するシステムと方法 |
US20060156059A1 (en) * | 2005-01-13 | 2006-07-13 | Manabu Kitamura | Method and apparatus for reconstructing data in object-based storage arrays |
CN1845093A (zh) * | 2006-04-30 | 2006-10-11 | 华中科技大学 | 一种属性可扩展的对象文件*** |
US20070118676A1 (en) * | 2005-11-23 | 2007-05-24 | Yoshiki Kano | System, method and apparatus for multiple-protocol-accessible OSD storage subsystem |
CN1331038C (zh) * | 2005-07-21 | 2007-08-08 | 华中科技大学 | 基于对象的存储控制器及其使用的调度方法 |
CN101040282A (zh) * | 2004-08-13 | 2007-09-19 | 潘纳萨斯公司 | 将虚拟映射存入对象属性中的分布式基于对象的存储*** |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7730213B2 (en) * | 2000-12-18 | 2010-06-01 | Oracle America, Inc. | Object-based storage device with improved reliability and fast crash recovery |
US20070288247A1 (en) * | 2006-06-11 | 2007-12-13 | Michael Mackay | Digital life server |
-
2008
- 2008-10-07 CN CN200880014000XA patent/CN101796514B/zh active Active
- 2008-10-07 WO PCT/CN2008/072606 patent/WO2010040255A1/zh active Application Filing
- 2008-10-07 US US13/063,934 patent/US8645460B2/en active Active - Reinstated
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101040282A (zh) * | 2004-08-13 | 2007-09-19 | 潘纳萨斯公司 | 将虚拟映射存入对象属性中的分布式基于对象的存储*** |
JP2006146904A (ja) * | 2004-11-17 | 2006-06-08 | Hitachi Ltd | ストレージシステムでオブジェクトレベルのスナップショットを生成するシステムと方法 |
US20060156059A1 (en) * | 2005-01-13 | 2006-07-13 | Manabu Kitamura | Method and apparatus for reconstructing data in object-based storage arrays |
CN1331038C (zh) * | 2005-07-21 | 2007-08-08 | 华中科技大学 | 基于对象的存储控制器及其使用的调度方法 |
US20070118676A1 (en) * | 2005-11-23 | 2007-05-24 | Yoshiki Kano | System, method and apparatus for multiple-protocol-accessible OSD storage subsystem |
CN1845093A (zh) * | 2006-04-30 | 2006-10-11 | 华中科技大学 | 一种属性可扩展的对象文件*** |
Non-Patent Citations (2)
Title |
---|
WANG, YAN.: "Research and Implementation of Software System for Object Storage Disk Controller.", THESIS FOR THE DEGREE OF MASTER OFHUAZHONG UNIVERSITY, February 2008 (2008-02-01) * |
ZHAO, SHUI QING ET AL.: "The Study of Quality of service in Object-based Storage Device", COMPUTER SCIENCE, vol. 33, no. 9, September 2006 (2006-09-01), pages 89 - 92 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9372854B2 (en) | 2010-11-08 | 2016-06-21 | Hewlett Packard Enterprise Development Lp | Load balancing backup jobs in a virtualized storage system having a plurality of physical nodes |
CN112241243A (zh) * | 2020-10-19 | 2021-01-19 | 北京计算机技术及应用研究所 | 一种主动对象存储***的实现方法 |
CN112241243B (zh) * | 2020-10-19 | 2024-01-26 | 北京计算机技术及应用研究所 | 一种主动对象存储***的实现方法 |
Also Published As
Publication number | Publication date |
---|---|
US20110167113A1 (en) | 2011-07-07 |
US8645460B2 (en) | 2014-02-04 |
CN101796514B (zh) | 2012-04-18 |
CN101796514A (zh) | 2010-08-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2010040255A1 (zh) | 对象存储***的管理方法 | |
US7765189B2 (en) | Data migration apparatus, method, and program for data stored in a distributed manner | |
EP2284725B1 (en) | Client, brokerage server and method for providing cloud storage | |
US9348842B2 (en) | Virtualized data storage system optimizations | |
JP4943081B2 (ja) | ファイル格納制御装置及び方法 | |
TWI232396B (en) | Partial migration of an object to another storage location in a computer system | |
KR100951107B1 (ko) | 최적의 성능을 위한 파일 관리 방법 | |
US8645645B2 (en) | File management method and hierarchy management file system | |
TWI465936B (zh) | 依據應用程式管理檔案之檔案系統及方法 | |
US20090063556A1 (en) | Root node for carrying out file level virtualization and migration | |
US8271559B2 (en) | Storage system and method of controlling same | |
US20090019223A1 (en) | Method and systems for providing remote strage via a removable memory device | |
WO2010078760A1 (zh) | 一种文件存储方法、装置及文件删除方法和装置 | |
JP2013506889A (ja) | ファイルレベル階層ストレージ管理システム、方法、及び装置 | |
WO2019149261A1 (zh) | 分布式文件***的文件存储方法及分布式文件*** | |
WO2018000300A1 (zh) | 一种电子设备的数据操作方法及电子设备 | |
US6594674B1 (en) | System and method for creating multiple files from a single source file | |
KR100936919B1 (ko) | 메타데이터의 일관성을 보장하기 위한 분산 파일 시스템 및방법 | |
CN101246534B (zh) | 一种使U盘具有autorun病毒免疫功能的方法 | |
US8725675B2 (en) | File server, file management system and file relocation method | |
US8489559B2 (en) | Methods and apparatus for conversion of content | |
WO2017172377A1 (en) | File system support for file-level ghosting | |
CN109478181A (zh) | 用于使得能够修改文件***卷内的多个数据对象的***和方法 | |
CN110209343B (zh) | 数据存储方法、装置、服务器及存储介质 | |
CN114356224B (zh) | 文件地址优化方法、终端、服务器及计算机可读存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200880014000.X Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08877224 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13063934 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 08877224 Country of ref document: EP Kind code of ref document: A1 |