WO2021196957A1 - 一种存储管理方法、装置及存储*** - Google Patents
一种存储管理方法、装置及存储*** Download PDFInfo
- Publication number
- WO2021196957A1 WO2021196957A1 PCT/CN2021/078781 CN2021078781W WO2021196957A1 WO 2021196957 A1 WO2021196957 A1 WO 2021196957A1 CN 2021078781 W CN2021078781 W CN 2021078781W WO 2021196957 A1 WO2021196957 A1 WO 2021196957A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- directory
- file
- name
- storage
- parent directory
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
- G06F16/134—Distributed indices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/164—File meta data generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file 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
-
- 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/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
Definitions
- This application relates to the field of storage technology, and in particular to a storage management method, device and storage system.
- the existing storage architecture usually separates the storage and processing of the metadata and data of the storage object, which not only simplifies the complexity of the overall system design, but also enables data index structure and data access mode according to the access characteristics of the metadata and the data itself.
- Targeted design in order to achieve better performance.
- the operation of object storage does not have rename semantics, and the rename operation can only be realized by first copying the source object to obtain the renamed target object, and then deleting the source object.
- the existing storage architecture needs to read the metadata and data of all source objects in the file directory for the file name renaming operation, then copy and generate a renamed target object metadata and data, and then rename the source object. All metadata and data of the object are deleted.
- the present application provides a storage management method, device, and storage system, which solves the problems of the prior art storage management that wastes network bandwidth resources and the poor IO access performance of the storage system.
- a storage management method includes: obtaining inode information of a parent directory of an object in a file system; and generating an object name of the object according to the inode information.
- the object naming method in the prior art is based on the name of the parent node of the object, and the name of the parent node of the parent node up to the root node of the storage system.
- the object name of the object is generated by the index node information of the parent directory of the object in the file system, where the index node information is unique in the storage system, and the naming of the object does not depend on the parent node.
- the object is a file or a directory.
- files or directories can be named based on the naming method provided in this application, and the files or directories can be further renamed, simplifying the naming method for objects, and improving the performance of storage management.
- the object name of the object also contains the object's identity.
- the object name is generated based on the index node information of the parent directory of the file or directory in the file system and the identification of the file or directory.
- the naming method provided in this application is simple and does not depend on the name of the parent node, which improves Performance of storage management.
- a storage management method includes: obtaining the object name of a first object; wherein the object name of the first object includes the index node information of the parent directory of the first object in the file system; The inode information of the first parent directory of the object in the file system is modified to the inode information of the second parent directory in the file system.
- the inode information of the parent directory of the first object in the file system can be modified to the inode information of the target directory, thereby avoiding all the inode information included in the first object.
- Object replication and deletion operations avoid the waste of network bandwidth resources, and avoid the problem of affecting the IO access performance of the storage system due to a large number of replication and deletion operations, and improve the user's IO access experience.
- the first object is a file or a directory.
- the object name of the first object also includes the identification of the first object.
- the object name of the first object also contains the identifier of the first object.
- an electronic device in a third aspect, includes an interface and a processor, the interface communicates with the processor; the processor is used to: obtain the index node information of the parent directory of the object in the file system; Object name.
- the object is a file or a directory.
- the object name of the object also includes the identifier of the object.
- an electronic device in a fourth aspect, includes an interface and a processor, the interface communicates with the processor; the processor is used for:
- the object name of the first object contains the index node information of the parent directory of the first object in the file system; and the first parent of the first object in the file system
- the inode information of the directory is modified to the inode information of the second parent directory in the file system.
- the first object is a file or a directory.
- the object name of the first object also includes the identifier of the first object.
- a storage system configured to: obtain the inode information of the parent directory of an object in the file system; and generate the object name of the object according to the inode information.
- the object is a file or a directory.
- the object name of the object also includes the identifier of the object.
- a storage system configured to: obtain the object name of a first object; wherein the object name of the first object includes the index node information of the parent directory of the first object in the file system; The inode information of the first parent directory of an object in the file system is modified to the inode information of the second parent directory in the file system.
- the first object is a file or a directory.
- the object name of the first object also includes the identifier of the first object.
- a storage management device includes: an acquisition module for acquiring inode information of a parent directory of an object in a file system; and a processing module for generating an object name of the object based on the inode information.
- the object is a file or a directory.
- the object name of the object also includes the identifier of the object.
- a storage management device comprising: an obtaining module for obtaining the object name of a first object; wherein the object name of the first object includes the index node of the parent directory of the first object in the file system Information; a processing module for modifying the index node information of the first parent directory of the first object in the file system to the index node information of the second parent directory in the file system.
- the first object is a file or a directory.
- the object name of the first object also includes the identifier of the first object.
- a computer-readable storage medium is provided.
- the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can execute the same as described in any one of the above-mentioned first aspects.
- a computer-readable storage medium is provided.
- the electronic device can execute any of the above-mentioned second aspects. The storage management method described.
- a computer program product which when the computer program product runs on a computer, causes the computer to execute the storage management method according to any one of the above-mentioned first aspects.
- a computer program product which when the computer program product runs on a computer, causes the computer to execute the storage management method according to any one of the above-mentioned second aspects.
- any storage management apparatus, storage device, storage system, computer-readable storage medium, or computer program product provided above can be used to execute the corresponding method provided above, and therefore, it can achieve
- any storage management apparatus, storage device, storage system, computer-readable storage medium, or computer program product provided above can be used to execute the corresponding method provided above, and therefore, it can achieve
- FIG. 1 is an architecture diagram of a storage system provided by an embodiment of the application
- FIG. 2 is a schematic diagram of a prior art object renaming process provided by an embodiment of the application.
- FIG. 3 is a schematic flowchart of a storage management method provided by an embodiment of the application.
- FIG. 4 is a schematic flowchart of another storage management method provided by an embodiment of the application.
- FIG. 5 is a sequence diagram of a software processing flow for performing a renaming operation provided by an embodiment of the application
- FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
- FIG. 7 is a schematic diagram of a storage management apparatus provided by an embodiment of the application.
- first and second are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined with “first” and “second” may explicitly or implicitly include one or more of these features. In the description of the present embodiment, unless otherwise specified, “plurality” means two or more.
- the embodiments of this application can be applied to the storage system shown in FIG. Form a cluster to enhance computing and storage capabilities.
- the computing node can run a client program, and communicate with the metadata node and the storage node through a network interface card (NIC).
- NIC network interface card
- Metadata nodes can be used to maintain the data layout and organization level of the storage system, and provide metadata management and access services for computing nodes and storage nodes through the NIC.
- a storage node may include an NIC, a processor, and multiple storage devices, etc., and the storage node provides external data access services.
- a storage device refers to a device used to store information, usually after the information is digitized, and then stored using electric, magnetic, or optical media.
- the storage device can be a Disk Disk, a Solid State Drive (SSD), or a Storage Class Memory (SCM) device, etc.
- SCM Storage Class Memory
- the processor may be a central processing unit (Central Processing Unit, CPU), a Field Programmable Gate Array (Field Programmable Gate Array, FPGA), or an application-specific integrated circuit (ASIC), etc.
- a storage node may be composed of NIC, CPU, and disk.
- the object In the field of storage technology, objects are usually used as the basic unit of storage management.
- the object may represent multiple types of basic storage management units such as a file, a narrow object, a block, and a stream.
- Metadata refers to data about data. It is data used to describe the information or attributes of the data. It can be used to describe or indicate the attributes of certain/certain data. Metadata can be elements or attributes of data, such as name, size, or data type; metadata can also be the structure of data, such as length, fields, or data columns.
- the naming method of the object name is based on the naming method composed of the parent directory and the subdirectory of the object. Taking the object in Figure 2 as an example, the parent directory of file1 is dir1 and the subdirectory is dir2, then the file The object name of file1 is: dir1/dir2/file1.
- the directory renaming operation can be as shown in Figure 2.
- the renaming operation specifically includes: First, traverse all the directories under the entire directory dir1 Objects, as shown in Figure 2, objects include files file1, file2, file3, and file4. Each object under the directory dir1 needs to be copied first to generate the target directory dir3. All objects under the directory dir3 also include files file1, file2, file3, and file4. Finally, the source objects file1, file2, file3, and file4 in the directory dir1 are deleted, and the renaming operation of the directory dir1 is completed.
- the renaming operation is complicated, and the copy and delete operations require a large amount of network bandwidth resources.
- the copy and delete operations require a large amount of network bandwidth resources.
- Delete operations are used for copying and deleting operations that waste the use of network bandwidth resources, and the performance of renaming operations is poor, and it also affects the IO access performance of the storage system, causing IO access delays or failures, and affecting user experience .
- the embodiment of the present application provides a storage management method, based on the foregoing storage system architecture, provides a method for naming objects; and based on the object naming method provided by the present application, the embodiments of the present application provide a method for renaming objects. ⁇ This solves the problems of waste of network bandwidth resources caused by storage management in the prior art and poor IO access performance of the storage system.
- the storage management method provided by the embodiment of the present application includes:
- S301 The storage system obtains inode information of the parent directory of the object in the file system.
- the parent directory of the object represents the upper-level directory of the object in the file system.
- index node refers to a data structure in many Unix-like file systems. Each index node stores the metadata of a file system object in the file system, but does not include the data content or file name.
- the index node information is used to indicate the corresponding index node. Specifically, the index node information may be an index node number, that is, inodeNo.
- the index node number inodeNo is used to indicate the unique index node of the object in the storage system.
- Any storage resource in the Unix operating system can be managed as a file, such as directories, CD-ROM drives, terminal devices, etc., are all treated as a kind of file. Therefore, the directories and hardware devices in the Unix operating system, like ordinary files, can have common attributes, namely metadata. Therefore, all inode nodes in the file system can be saved in the inode block, and metadata of the object can be saved in the inode node, which can be some attributes of the file, such as creation and modification time. For example, when the system creates a file file1, the system allocates an inode node from the inode block to the file file1, and stores the attributes of the file file1 in this node.
- the inodeNo of the directory dir1 is 10000, and the inodeNo of the directory dir2 is 10001.
- S302 The storage system generates the object name of the object according to the index node information.
- the storage system can generate the object name of the object according to the above-mentioned index node information.
- the object name of the object may also include the identifier of the object. Then the storage system can generate the object name according to the index node information and the identifier of the object. Among them, the object can be a file or a directory.
- the object name of the aforementioned directory dir2 may be: 10000/dir2, and the object name of the file file1 may be: 10001/file1.
- the above-mentioned embodiments of the present application can generate the naming method of the object name according to the index node information, or generate the naming method of the object name according to the index node information and the identifier of the object, which simplifies the naming method of files or objects in the storage system. Further, based on the above-mentioned object naming method, only the metadata of the object (such as the index node number inodeNo) needs to be modified to perform the renaming operation of the object, and there is no need to copy and delete the object. Next, we will introduce in detail the operation process of object renaming based on the above-mentioned object naming method.
- the present application also provides a storage management method, which is applied to the object renaming operation in the storage system, that is, in the scenario where the object name of the object needs to be modified.
- the method may include:
- S401 The storage system obtains the object name of the first object, where the object name of the first object includes inode information of the parent directory of the first object in the file system.
- the first object can be a file or a directory.
- the parent directory of the first object in the file system is the upper level directory of the first object in the file system.
- the index node information may specifically be the index node number, that is, inodeNo.
- the first object is the file file1, the parent directory of file1 is dir2, and the inodeNo of the parent directory dir2 is 10001.
- the first object is the directory dir2, the parent directory of dir2 is dir1, and the inodeNo of the parent directory dir1 is 10000.
- S402 The storage system modifies the inode information of the first parent directory of the first object in the file system to the inode information of the second parent directory in the file system.
- the storage system can modify the index node information of the first parent directory of the first object in the file system to the index node of the second parent directory in the file system information.
- the second parent directory represents the target directory to be renamed.
- the inode information of the second parent directory is the inodeNo assigned by the storage system to the second parent directory (target directory).
- the object name of the first object also includes the identification of the first object.
- the first object is file1
- the parent directory of the first object is dir2
- the inodeNo of the parent directory dir2 is 10001
- the identifier of the first object is file1
- the original object name of the first object can be: 10001/ file1.
- the storage system can insert a new directory, for example, the target directory is dir3, and the metadata of the target directory dir3 is inserted.
- the new target is the second parent directory, and the inode No assigned by the storage system to the second parent directory is, for example, 10003, and the target object name of the new second object is 10003/file1.
- delete the metadata of the parent directory of the first object to complete the renaming operation.
- the first object is the directory dir2, the parent directory of the first object is dir1, and the inodeNo of the parent directory dir1 of the first object is 10000, then the original object name of the first object may be: 10000/dir2.
- the storage system can insert a new target directory and metadata of the target directory. For example, if the target directory is the second parent directory, and the inode No assigned by the storage system to the second parent directory is, for example, 10004, the target object name of the new second object is 10004/dir2. Finally, delete the metadata of the parent directory of the first object to complete the renaming operation.
- processing sequence diagram of the software program for the storage system to perform the object renaming operation may be as shown in FIG. 5, including:
- the application initiates a rename request to the access layer.
- the application refers to a client application that needs to be renamed and initiates a rename request.
- the access layer represents the process of executing the rename request.
- the access layer records the transaction and sends a transaction request to the metadata layer.
- the metadata layer represents metadata nodes that store metadata.
- the access layer instructs the metadata layer to write the metadata of the target directory.
- the access layer instructs the metadata layer to delete the metadata of the original directory.
- the access layer returns a response that the rename is completed to the application.
- the storage system when performing a renaming operation, the storage system only needs to modify the metadata of the directory or file. Specifically, the storage system inserts the metadata of a new target directory and deletes the metadata of the original directory. That is, the renaming operation of dir1 can be realized without copying and deleting each file in the directory, and without occupying the IO access resources of the storage system, which effectively improves the performance of the storage system's object renaming operation.
- an embodiment of the present application also provides an electronic device.
- the electronic device 600 includes an interface 601 and a processor 602, and the interface 601 can communicate with the processor 602. Specifically, communication can be carried out via a bus.
- the processor 602 may be configured to: obtain the index node information of the parent directory of the object in the file system; and generate the object name of the object according to the index node information.
- the object may be a file or a directory.
- the object name of the object also includes the identifier of the object.
- an embodiment of the present application further provides an electronic device.
- the processor 602 may be further configured to: obtain the object name of the first object; wherein, the object name of the first object includes the first object in the file The index node information of the parent directory in the system; the index node information of the first parent directory of the first object in the file system is modified to the index node information of the second parent directory in the file system.
- the first object may be a file or a directory.
- the object name of the first object also includes the identification of the first object.
- the processor 602 may further include instructions, and the instructions may be executed on the processor 602 so that the electronic device 600 executes the method described in the foregoing method embodiments.
- the electronic device in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
- the volatile memory may be random access memory (RAM), which is used as an external cache.
- RAM random access memory
- static random access memory static random access memory
- DRAM dynamic random access memory
- DRAM synchronous dynamic random access memory
- Access memory synchronous DRAM, SDRAM
- double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
- enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
- synchronous connection dynamic random access memory Take memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).
- an embodiment of the present application also provides a storage system, which can be used to execute the steps that can be implemented by the storage system in the above embodiments, and the storage system can be based on the storage architecture shown in FIG. 1.
- the embodiment of the present application also provides a storage management device. As shown in FIG. 7, the device 700 includes an acquisition module 701 and a processing module 702.
- the obtaining module 701 may be used to obtain the index node information of the parent directory of the object in the file system.
- the processing module 702 may be used to generate the object name of the object according to the index node information.
- the object may be a file or a directory.
- the object name of the object also includes the identifier of the object.
- an embodiment of the present application further provides a storage management device.
- the obtaining module 701 may also be used to obtain the object name of the first object; wherein, the object name of the first object includes the first object in the file The inode information of the parent directory in the system.
- the processing module 702 may be used to modify the inode information of the first parent directory of the first object in the file system to the inode information of the second parent directory in the file system.
- the first object may be a file or a directory.
- the object name of the first object also includes the identification of the first object.
- the steps executed by the storage management apparatus in the foregoing embodiments may be executed by corresponding modules or units.
- the effects achieved by the foregoing storage management apparatus may also refer to the content described in the foregoing embodiment, which will not be repeated here.
- the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
- the implementation process constitutes any limitation.
- the disclosed storage system, storage device, and method may be implemented in other ways.
- the above-described embodiments are merely illustrative, for example, the division of nodes, systems, or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined. Or it can be integrated into another system, or some features can be ignored or not implemented.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
- the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
- the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
- the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
一种存储管理方法、装置及存储***,涉及存储技术领域,用于解决现有技术中存储管理对网络带宽资源浪费,以及存储***的IO访问性能较差的问题。该方法包括:存储***获取对象的父目录在文件***中的索引节点信息(S301);存储***根据索引节点信息生成对象的对象名(S302)。
Description
本申请要求于2020年06月23日提交国家知识产权局、申请号为202010580922.X、申请名称为“一种存储管理方法、装置及存储***”,以及2020年03月28日提交国家知识产权局、申请号为202010232677.3申请名称为“一种对象管理方法及设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及存储技术领域,尤其涉及一种存储管理方法、装置及存储***。
现有的存储架构,通常将存储对象的元数据与数据分离存储和处理,既能简化整体***设计的复杂度,而且能够根据元数据和数据本身的访问特性进行数据索引结构、数据访问模式等针对性设计,以便达到更好的性能表现。其中,对象存储的操作没有重命名(rename)语义,要进行rename操作只能通过先对源对象进行复制得到重命名的目标对象,再将源对象删除来实现。
例如,现有的存储架构对于文件名的重命名操作,需要读取该文件目录下的所有源对象的元数据和数据,然后复制生成一份重命名的目标对象元数据和数据,再将源对象的元数据和数据全部删除。
当需要重命名的文件目录下存储对象数量较多、数据量较大时,复制和删除操作需要占用大量的网络带宽资源,且对于存储***的输入输出(InputOutput,IO)访问性能的影响会很大。
发明内容
本申请提供一种存储管理方法、装置及存储***,解决了现有技术的存储管理对网络带宽资源浪费,以及存储***的IO访问性能较差的问题。
为达到上述目的,本申请采用如下技术方案:
第一方面,提供一种存储管理方法,该方法包括:获取对象的父目录在文件***中的索引节点信息;根据索引节点信息生成对象的对象名。
现有技术的对象命名方式,是基于对象的父节点名称,以及父节点上一级的父节点名称直至存储***根节点的命名方式。而本申请的上述技术方案中,通过对象的父目录在文件***中的索引节点信息生成对象的对象名,其中,索引节点信息在存储***中是唯一的,对象的命名不依赖于父节点的名称,从而简化了现有技术对于对象的命名方式,进一步还可以简化对于对象进行重命名的操作,提高存储管理的性能。
在一种可能的设计方式中,对象为文件或目录。上述可能的实现方式中,可以基于本申请提供的命名方式对文件或目录进行命名,进一步的对文件或目录进行重命名,简化对于对象的命名方式,提高存储管理的性能。
在一种可能的设计方式中,对象的对象名还包含对象的标识。上述可能的实现方式中,根据文件或目录的父目录在文件***中的索引节点信息和文件或目录的标识生 成对象名,本申请提供的命名方式简单,且不依赖于父节点的名称,提高存储管理的性能。
第二方面,提供一种存储管理方法,该方法包括:获取第一对象的对象名;其中,第一对象的对象名包含第一对象在文件***中的父目录的索引节点信息;将第一对象在文件***中的第一父目录的索引节点信息修改为文件***中的第二父目录的索引节点信息。
上述技术方案中,当对于第一对象进行重命名操作时,可以将第一对象在文件***中的父目录的索引节点信息修改为目标目录的索引节点信息,从而避免了第一对象包括的所有对象的复制和删除操作,避免了对网络带宽资源的浪费,并且避免了由于大量的复制和删除操作对存储***的IO访问性能造成影响的问题,改善用户的IO访问体验。
在一种可能的设计方式中,第一对象为文件或目录。
在一种可能的设计方式中,第一对象的对象名还包含第一对象的标识。
上述可能的实现方式中,第一对象的对象名还包含第一对象的标识,当对于第一对象进行重命名操作时,仅仅需要添加一个目标目录为第二父目录,并且添加第二父目录的元数据,修改第一对象在文件***中的父目录的索引节点信息为第二父目录的索引节点信息,即可完成重命名操作,简化了重命名操作的流程,并且避免了对带宽资源的浪费,提高重命名操作的性能。
第三方面,提供一种电子设备,该电子设备包含接口和处理器,接口与处理器通信;处理器用于:获取对象的父目录在文件***中的索引节点信息;根据索引节点信息生成对象的对象名。
在一种可能的设计方式中,对象为文件或目录。
在一种可能的设计方式中,对象的对象名还包含所述对象的标识。
第四方面,提供一种电子设备,该电子设备包含接口和处理器,接口与处理器通信;所述处理器用于:
获取所述第一对象的对象名;其中,所述第一对象的对象名包含所述第一对象在文件***中的父目录的索引节点信息;将第一对象在文件***中的第一父目录的索引节点信息修改为文件***中的第二父目录的索引节点信息。
在一种可能的设计方式中,第一对象为文件或目录。
在一种可能的设计方式中,第一对象的对象名还包含所述第一对象的标识。
第五方面,提供一种存储***,该存储***用于:获取对象的父目录在文件***中的索引节点信息;根据索引节点信息生成所述对象的对象名。
在一种可能的设计方式中,对象为文件或目录。
在一种可能的设计方式中,对象的对象名还包含所述对象的标识。
第六方面,提供一种存储***,该存储***用于:获取第一对象的对象名;其中,第一对象的对象名包含第一对象在文件***中的父目录的索引节点信息;将第一对象在文件***中的第一父目录的索引节点信息修改为文件***中的第二父目录的索引节点信息。
在一种可能的设计方式中,第一对象为文件或目录。
在一种可能的设计方式中,第一对象的对象名还包含所述第一对象的标识。
第七方面,提供一种存储管理装置,该装置包括:获取模块,用于获取对象的父目录在文件***中的索引节点信息;处理模块,用于根据索引节点信息生成对象的对象名。
在一种可能的设计方式中,对象为文件或目录。
在一种可能的设计方式中,对象的对象名还包含所述对象的标识。
第八方面,提供一种存储管理装置,该装置包括:获取模块,用于获取第一对象的对象名;其中,第一对象的对象名包含第一对象在文件***中的父目录的索引节点信息;处理模块,用于将第一对象在文件***中的第一父目录的索引节点信息修改为文件***中的第二父目录的索引节点信息。
在一种可能的设计方式中,第一对象为文件或目录。
在一种可能的设计方式中,第一对象的对象名还包含所述第一对象的标识。
第九方面,提供一种计算机可读存储介质,当所述计算机可读存储介质中的指令由电子设备的处理器执行时,使得所述电子设备能够执行如上述第一方面中任一项所述的存储管理方法。
第十方面,提供一种计算机可读存储介质,当所述计算机可读存储介质中的指令由电子设备的处理器执行时,使得所述电子设备能够执行如上述第二方面中任一项所述的存储管理方法。
第十一方面,提供一种计算机程序产品,当所述计算机程序产品在计算机上运行时,使得所述计算机执行如上述第一方面中任一项所述的存储管理方法。
第十二方面,提供一种计算机程序产品,当所述计算机程序产品在计算机上运行时,使得所述计算机执行如上述第二方面中任一项所述的存储管理方法。
可以理解地,上述提供的任一种存储管理装置、存储设备、存储***、计算机可读存储介质或者计算机程序产品,均可以用于执行上文所提供的对应的方法,因此,其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果,此处不再赘述。
图1为本申请实施例提供的一种存储***的架构图;
图2为本申请实施例提供的一种现有技术的对象重命名流程示意图;
图3为本申请实施例提供的一种存储管理方法的流程示意图;
图4为本申请实施例提供的另一种存储管理方法的流程示意图;
图5为本申请实施例提供的一种进行重命名操作的软件处理流程时序图;
图6为本申请实施例提供的一种电子设备的结构示意图;
图7为本申请实施例提供的一种存储管理装置的示意图。
以下,术语“第一”、“第二”仅用于描述目的,而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此,限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本实施例的描述中,除非另有说明,“多个”的含义是两个或两个以上。
需要说明的是,本申请中,“示例性的”或者“例如”等词用于表示作例子、例证或 说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
首先,对本申请实施例的实施环境和应用场景进行简单介绍。
本申请实施例可以应用于如图1所示的存储***,该存储***主要有计算节点、存储节点和元数据节点(可选)组成,其中各种类型的节点均可以通过网络互连的方式构成集群,用于增强计算和存储能力。
计算节点可以运行客户端程序,通过网络接口卡(Network Interface Card,NIC)与元数据节点和存储节点进行通信。
元数据节点可以用于维护存储***的数据布局形式和组织层级,并通过NIC为计算节点和存储节点提供元数据管理和访问服务。
存储节点可以包含NIC、处理器以及多个存储设备等,存储节点对外提供数据存取服务。其中,存储设备是指用于储存信息的设备,通常是将信息进行数字化后,再利用电、磁或光学等方式的媒体加以存储。存储设备可以是磁盘Disk、固态硬盘(Solid State Drive,SSD)或者存储级内存(Storage Class Memory,SCM)设备等,本申请实施例的图1中仅以Disk作为示例,本申请对此不作限定。处理器可以为中央处理器(Central Processing Unit,CPU)、现场可编程门阵列(Field Programmable Gate Array,FPGA)或者专用集成电路(Application-specific integrated circuit,ASIC)等。示例性的,如图1所示,一个存储节点可以由NIC、CPU以及磁盘Disk组成。
在存储技术领域,通常将对象作为存储管理的基本单元。在本申请的实施例中,根据存储***提供的接口不同,对象可以表示文件File、狭义的对象object、块Block、流Stream等多种类型的基本存储管理单元。
对象的存储管理中,通常可以将对象的元数据和数据本身分开进行存储和处理。其中,数据是对客观事物的逻辑归纳,在本申请实施例中是指能输入到计算机并被计算机程序处理的符号的总称,可以是用于输入计算机进行处理、具有一定意义的数字、字母、符号和模拟量等的通称。在计算机***中,数据可以二进制信息单元0和1的形式表示。元数据是指关于数据的数据,是用来描述数据的信息或者属性的数据,可以用于描述或者指示某个/某些数据的属性。元数据可以为数据的元素或属性,例如,名称、大小或数据类型等;元数据还可以为数据的结构,例如长度、字段或数据列等。
基于现有的存储架构,对象名的命名方式是基于对象的父目录-子目录构成的命名方式,以图2中的对象为例,文件file1的父目录为dir1,子目录为dir2,则文件file1的对象名为:dir1/dir2/file1。
基于上述的现有技术的命名方式,对于目录的重命名操作可以如图2所示,例如,需要对目录dir1重命名为dir3,则重命名操作具体包括:首先,遍历整个目录dir1下的所有对象,如图2所示,对象包括文件file1、file2、file3和file4。对于该目录dir1 下的每一个对象都需要先复制一份,生成目标目录dir3,目录dir3下的所有对象也包括以及文件file1、file2、file3和file4。最后将目录dir1下的源对象file1、file2、file3和file4删除,对目录dir1的重命名操作完成。
上述本申请的实施方式,重命名操作复杂,复制和删除操作需要占用大量的网络带宽资源。对于文件目录下存储对象数量较多、数据量较大的目录进行重命名操作时,例如,某目录下有一千万个文件,则重命名该目录需要对上述一千万个文件进行复制和删除操作,用于复制和删除操作对网络带宽资源的占用造成浪费,且重命名的操作性能较差,还会对存储***的IO访问性能造成影响,造成IO访问延时或者故障,影响用户体验。
基于此,本申请实施例提供一种存储管理方法,基于上述的存储***架构,提供一种对象命名的方式;以及基于本申请提供的对象命名方式,本申请实施例提供一种进行重命名对象的实施方式。从而解决现有技术中存储管理对网络带宽资源浪费,以及存储***的IO访问性能较差的问题。
如图3所示,本申请实施例提供的存储管理方法包括:
S301:存储***获取对象的父目录在文件***中的索引节点信息。
其中,对象的父目录表示所述对象在文件***中的上一级目录。
索引节点(inode)是指在许多类Unix文件***中的一种数据结构,每个索引节点保存了文件***中的一个文件***对象的元信息数据,但不包括数据内容或者文件名。索引节点信息用于指示对应的索引节点,具体的,索引节点信息可以为索引节点号,即inodeNo。
需要说明的是,索引节点号inodeNo用于指示对象在存储***中唯一的索引节点。在Unix操作***中的任何存储资源都可以被当作文件来管理,如目录、光驱、终端设备等,都被当作是一种文件。因此,Unix操作***中的目录、硬件设备跟普通文件一样,可以具有共同的属性即元数据。因此,inode块中可以保存文件***中的全部inode节点,inode节点中保存对象的元信息数据,具体可以为文件的部分属性,如创建、修改时间等。例如,当***创建了一个文件file1时,***就会从inode块中给该文件file1分配一个inode结点,在这个结点中存储文件file1的属性。
示例性的,目录dir1的inodeNo为10000,目录dir2的inodeNo为10001。
S302:存储***根据索引节点信息生成对象的对象名。
则存储***可以根据上述的索引节点信息生成对象的对象名。
在一种实施方式中,对象的对象名还可以包含对象的标识。则存储***可以根据索引节点信息和对象的标识生成对象名。其中,对象可以为文件或者目录。
示例性的,上述的目录dir2的对象名可以为:10000/dir2,文件file1的对象名可以为:10001/file1。
上述本申请的实施方式,可以根据索引节点信息生成对象名的命名方式,或者根据索引节点信息和对象的标识生成对象名的命名方式,简化了存储***中对于文件或者对象的命名方式。进一步的,基于上述的对象命名方式,进行对象的重命名操作就只需要修改对象的元数据(如索引节点号inodeNo),不需要再进行对象的复制和删除操作。接下来将详细介绍基于上述对象命名方式的对象重命名操作流程。
基于上述本申请提供的对象名的命名方式,本申请还提供一种存储管理方法,应用于存储***中的对象重命名操作,即需要修改对象的对象名的场景下。如图4所示,该方法可以包括:
S401:存储***获取第一对象的对象名,其中,第一对象的对象名包含第一对象在文件***中的父目录的索引节点信息。
其中,第一对象可以为文件或目录。第一对象在文件***中的父目录即为第一对象在文件***中的上一级目录。索引节点信息具体可以为索引节点号,即inodeNo。
示例性的,第一对象为文件file1,file1的父目录为dir2,父目录dir2的inodeNo为10001。
第一对象为目录dir2,dir2的父目录为dir1,父目录dir1的inodeNo为10000。
S402:存储***将第一对象在文件***中的第一父目录的索引节点信息修改为文件***中的第二父目录的索引节点信息。
当需要对第一对象的对象名进行修改或者重新命名的时候,存储***可以将第一对象在文件***中的第一父目录的索引节点信息修改为文件***中的第二父目录的索引节点信息。
其中,第二父目录表示重命名的目标目录。第二父目录的索引节点信息即为存储***为第二父目录(目标目录)分配的索引节点号inodeNo。
在一种实施方式中,第一对象的对象名还包含第一对象的标识。
基于上述的示例,第一对象为文件file1,第一对象的父目录为dir2,父目录dir2的inodeNo为10001,第一对象的标识为file1,则第一对象的原始对象名可以为:10001/file1。若需要对第一对象进行重命名,则存储***可以***一个新的目录,例如,目标目录为dir3,并且***目标目录dir3的元数据。该新的目标为第二父目录,存储***为第二父目录分配的索引节点号inodeNo,例如为10003,则新的第二对象的目标对象名为:10003/file1。最后删除第一对象的父目录的元数据即完成重命名操作。
示例性的,第一对象为目录dir2,第一对象的父目录为dir1,第一对象的父目录dir1的inodeNo为10000,则第一对象的原始对象名可以为:10000/dir2。对第一对象进行重命名,则存储***可以***一个新的目标目录,以及目标目录的元数据。例如,目标目录为第二父目录,存储***为第二父目录分配的索引节点号inodeNo例如为10004,则新的第二对象的目标对象名为:10004/dir2。最后删除第一对象的父目录的元数据即完成重命名操作。
综上所述,存储***进行对象的重命名操作的软件程序的处理时序图可以为如图5所示的,包括:
1、应用程序向接入层发起重命名请求。
其中,应用程序是指有重命名需要并且发起重命名请求的客户端应用。接入层表示执行重命名请求的处理进程。
2、接入层记录事务并向元数据层发送事务请求。
元数据层表示存储元数据的元数据节点。
3、接入层指示元数据层写入目标目录的元数据。
4、接入层指示元数据层删除原始目录的元数据。
5、接入层向应用程序返回重命名完成的响应。
通过本申请的上述实施方式,进行重命名操作时,存储***只需要修改目录或者文件的元数据,具体可以为,存储******一个新的目标目录的元数据,并删除原目录的元数据,即可以实现对dir1的重命名操作,不需要对目录下的每个文件进行复制和删除操作,也不需要占用存储***IO访问资源,有效提高了存储***对于对象的重命名操作性能。
本申请实施例还提供一种电子设备,如图6所示,该电子设备600包括接口601和处理器602,接口601能够与处理器602进行通信。具体的,可以通过总线进行通信。
处理器602可以用于:获取对象的父目录在文件***中的索引节点信息;根据索引节点信息生成对象的对象名。
在一种实施方式中,对象可以为文件或目录。
在一种实施方式中,对象的对象名还包含所述对象的标识。
基于此,本申请实施例还提供一种电子设备,如图6所示,处理器602还可以用于:获取第一对象的对象名;其中,第一对象的对象名包含第一对象在文件***中的父目录的索引节点信息;将第一对象在文件***中的第一父目录的索引节点信息修改为文件***中的第二父目录的索引节点信息。
在一种实施方式中,第一对象可以为文件或目录。
在一种实施方式中,第一对象的对象名还包含第一对象的标识。
处理器602还可以包括指令,所述指令可以在所述处理器602上被运行,使得所述电子设备600执行上述方法实施例中描述的方法。
还应理解,本申请实施例中的电子设备可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的随机存取存储器(random access memory,RAM)可用,例如静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。
另外,本申请实施例还提供一种存储***,所述存储***可以用于执行上述实施例中存储***能够实现的步骤,所述存储***可以为基于图1所示的存储架构。
本申请实施例还提供一种存储管理装置,如图7所示,该装置700包括获取模块701和处理模块702。
其中,获取模块701可以用于获取对象的父目录在文件***中的索引节点信息。
处理模块702可以用于根据索引节点信息生成对象的对象名。
在一种实施方式中,对象可以为文件或目录。
在一种实施方式中,对象的对象名还包含所述对象的标识。
基于此,本申请实施例还提供一种存储管理装置,如图7所示,获取模块701还可以用于获取第一对象的对象名;其中,第一对象的对象名包含第一对象在文件***中的父目录的索引节点信息。
处理模块702可以用于将第一对象在文件***中的第一父目录的索引节点信息修改为文件***中的第二父目录的索引节点信息。
在一种实施方式中,第一对象可以为文件或目录。
在一种实施方式中,第一对象的对象名还包含第一对象的标识。
上述各实施例中存储管理装置执行的步骤可以由相应的模块或者单元执行相应的步骤。并且,上述的存储管理装置实现的效果也可以参照上述实施例中描述的内容,此处不再赘述。应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
在本申请所提供的几个实施例中,应该理解到,所揭露的存储***、存储设备和方法,可以通过其它的方式实现。例如,以上所描述的实施例仅仅是示意性的,例如,节点、***或者单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘 等各种可以存储程序代码的介质。
最后应说明的是:以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何在本申请揭露的技术范围内的变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。
Claims (26)
- 一种存储管理方法,其特征在于,所述方法包括:获取对象的父目录在文件***中的索引节点信息;根据所述索引节点信息生成所述对象的对象名。
- 根据权利要求1所述的方法,其特征在于,所述对象为文件或目录。
- 根据权利要求1或2所述的方法,其特征在于,所述对象的对象名还包含所述对象的标识。
- 一种存储管理方法,其特征在于,所述方法包括:获取第一对象的对象名;其中,所述第一对象的对象名包含所述第一对象在文件***中的父目录的索引节点信息;将所述第一对象在文件***中的第一父目录的索引节点信息修改为所述文件***中的第二父目录的索引节点信息。
- 根据权利要求4所述的方法,其特征在于,所述第一对象为文件或目录。
- 根据权利要求4或5所述的方法,其特征在于,所述第一对象的对象名还包含所述第一对象的标识。
- 一种电子设备,其特征在于,所述电子设备包含接口和处理器,所述接口与处理器通信;所述处理器用于:获取对象的父目录在文件***中的索引节点信息;根据所述索引节点信息生成所述对象的对象名。
- 根据权利要求7所述的电子设备,其特征在于,所述对象为文件或目录。
- 根据权利要求7或8所述的电子设备,其特征在于,所述对象的对象名还包含所述对象的标识。
- 一种电子设备,其特征在于,所述电子设备包含接口和处理器,所述接口与处理器通信;所述处理器用于:获取第一对象的对象名;其中,所述第一对象的对象名包含所述第一对象在文件***中的父目录的索引节点信息;将所述第一对象在文件***中的第一父目录的索引节点信息修改为所述文件***中的第二父目录的索引节点信息。
- 根据权利要求10所述的电子设备,其特征在于,所述第一对象为文件或目录。
- 根据权利要求10或11所述的电子设备,其特征在于,所述第一对象的对象名还包含所述第一对象的标识。
- 一种存储***,其特征在于,所述存储***用于:获取对象的父目录在文件***中的索引节点信息;根据所述索引节点信息生成所述对象的对象名。
- 根据权利要求13所述的存储***,其特征在于,所述对象为文件或目录。
- 根据权利要求13或14所述的存储***,其特征在于,所述对象的对象名还包含所述对象的标识。
- 一种存储***,其特征在于,所述存储***用于:获取第一对象的对象名;其中,所述第一对象的对象名包含所述第一对象在文件 ***中的父目录的索引节点信息;将所述第一对象在文件***中的第一父目录的索引节点信息修改为所述文件***中的第二父目录的索引节点信息。
- 根据权利要求16所述的存储***,其特征在于,所述第一对象为文件或目录。
- 根据权利要求16或17所述的存储***,其特征在于,所述第一对象的对象名还包含所述第一对象的标识。
- 一种存储管理装置,其特征在于,所述装置包括:获取模块,用于获取对象的父目录在文件***中的索引节点信息;处理模块,用于根据所述索引节点信息生成所述对象的对象名。
- 根据权利要求19所述的装置,其特征在于,所述对象为文件或目录。
- 根据权利要求19或20所述的装置,其特征在于,所述对象的对象名还包含所述对象的标识。
- 一种存储管理装置,其特征在于,所述装置包括:获取模块,用于获取第一对象的对象名;其中,所述第一对象的对象名包含所述第一对象在文件***中的父目录的索引节点信息;处理模块,用于将所述第一对象在文件***中的第一父目录的索引节点信息修改为所述文件***中的第二父目录的索引节点信息。
- 根据权利要求22所述的装置,其特征在于,所述第一对象为文件或目录。
- 根据权利要求22或23所述的装置,其特征在于,所述第一对象的对象名还包含所述第一对象的标识。
- 一种计算机可读存储介质,其特征在于,当所述计算机可读存储介质中的指令由电子设备的处理器执行时,使得所述电子设备能够执行如权利要求1至3中任一项所述的存储管理方法。
- 一种计算机可读存储介质,其特征在于,当所述计算机可读存储介质中的指令由电子设备的处理器执行时,使得所述电子设备能够执行如权利要求4至6中任一项所述的存储管理方法。
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010232677.3 | 2020-03-28 | ||
CN202010232677 | 2020-03-28 | ||
CN202010580922.X | 2020-06-23 | ||
CN202010580922.XA CN113448921A (zh) | 2020-03-28 | 2020-06-23 | 一种存储管理方法、装置及存储*** |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021196957A1 true WO2021196957A1 (zh) | 2021-10-07 |
Family
ID=77808352
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/078781 WO2021196957A1 (zh) | 2020-03-28 | 2021-03-02 | 一种存储管理方法、装置及存储*** |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN113448921A (zh) |
WO (1) | WO2021196957A1 (zh) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116028312A (zh) * | 2023-02-27 | 2023-04-28 | 浪潮电子信息产业股份有限公司 | 一种固态硬盘寿命到期处理方法、装置及介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102713901A (zh) * | 2009-10-02 | 2012-10-03 | 赛门铁克公司 | 存储复制***和方法 |
CN103150394A (zh) * | 2013-03-25 | 2013-06-12 | 中国人民解放军国防科学技术大学 | 面向高性能计算的分布式文件***元数据管理方法 |
CN103229173A (zh) * | 2012-12-26 | 2013-07-31 | 华为技术有限公司 | 元数据管理方法及*** |
US20130339406A1 (en) * | 2012-06-19 | 2013-12-19 | Infinidat Ltd. | System and method for managing filesystem objects |
CN105550371A (zh) * | 2016-01-27 | 2016-05-04 | 华中科技大学 | 一种面向大数据环境的元数据组织方法和*** |
-
2020
- 2020-06-23 CN CN202010580922.XA patent/CN113448921A/zh active Pending
-
2021
- 2021-03-02 WO PCT/CN2021/078781 patent/WO2021196957A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102713901A (zh) * | 2009-10-02 | 2012-10-03 | 赛门铁克公司 | 存储复制***和方法 |
US20130339406A1 (en) * | 2012-06-19 | 2013-12-19 | Infinidat Ltd. | System and method for managing filesystem objects |
CN103229173A (zh) * | 2012-12-26 | 2013-07-31 | 华为技术有限公司 | 元数据管理方法及*** |
CN103150394A (zh) * | 2013-03-25 | 2013-06-12 | 中国人民解放军国防科学技术大学 | 面向高性能计算的分布式文件***元数据管理方法 |
CN105550371A (zh) * | 2016-01-27 | 2016-05-04 | 华中科技大学 | 一种面向大数据环境的元数据组织方法和*** |
Also Published As
Publication number | Publication date |
---|---|
CN113448921A (zh) | 2021-09-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7393334B2 (ja) | コンテンツアイテム同期のための一意の識別子の割り振り及び再割り当て | |
US11741046B2 (en) | Method and apparatus for creating system disk snapshot of virtual machine | |
Fairbanks | An analysis of Ext4 for digital forensics | |
US7007024B2 (en) | Hashing objects into multiple directories for better concurrency and manageability | |
US7555620B1 (en) | Method and system of using a backup image for multiple purposes | |
US8433863B1 (en) | Hybrid method for incremental backup of structured and unstructured files | |
US20160350326A1 (en) | Concurrency control in virtual file system | |
US11176165B2 (en) | Search and analytics for storage systems | |
US8977662B1 (en) | Storing data objects from a flat namespace in a hierarchical directory structured file system | |
CN113568566B (zh) | 利用索引物件来进行简易存储服务无缝迁移的方法、主装置以及存储服务器 | |
Liu et al. | Cfs: A distributed file system for large scale container platforms | |
Henry | Howard chu on lightning memory-mapped database | |
US20180101539A1 (en) | Reducing read operations and branches in file system policy checks | |
WO2021196957A1 (zh) | 一种存储管理方法、装置及存储*** | |
US8850126B2 (en) | Exclusive access during a critical sub-operation to enable simultaneous operations | |
Nelson et al. | Syndicate: Virtual cloud storage through provider composition | |
US20230006814A1 (en) | Method and apparatus for implementing changes to a file system that is emulated with an object storage system | |
AU2021268828B2 (en) | Secure data replication in distributed data storage environments | |
Orzechowski et al. | Indexing legacy data-sets for global access and processing in multi-cloud environments | |
Agrawal et al. | SD-HDFS: Secure deletion in hadoop distributed file system | |
US20230401174A1 (en) | Extending metadata-driven capabilities in a metadata-centric filesystem | |
US11853319B1 (en) | Caching updates appended to an immutable log for handling reads to the immutable log | |
US12007946B2 (en) | Systems and methods for managing path and file names using a universal connector | |
CN113568567B (zh) | 利用索引物件来进行简易存储服务无缝迁移的方法、主装置以及存储服务器 | |
US11914483B1 (en) | Metadata-based recovery classification management |
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: 21779613 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: 21779613 Country of ref document: EP Kind code of ref document: A1 |