CN101079053A - ContextFS based file management method - Google Patents
ContextFS based file management method Download PDFInfo
- Publication number
- CN101079053A CN101079053A CN 200710069838 CN200710069838A CN101079053A CN 101079053 A CN101079053 A CN 101079053A CN 200710069838 CN200710069838 CN 200710069838 CN 200710069838 A CN200710069838 A CN 200710069838A CN 101079053 A CN101079053 A CN 101079053A
- Authority
- CN
- China
- Prior art keywords
- file
- user
- storage
- context
- files
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims description 14
- 238000000034 method Methods 0.000 claims abstract description 25
- 230000007774 longterm Effects 0.000 abstract description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
技术领域technical field
本发明涉及文件管理领域，主要是一种基于ContextFS上下文文件系统的文件管理方法。The invention relates to the field of file management, and mainly relates to a file management method based on a ContextFS context file system.
背景技术Background technique
在上下文文件系统的某些场景中，会无法避免的产生多个用户对同一个文件进行读写的情况，本发明需要解决这些冲突，同时又维持命名空间的一致性；此外由于基于ContextFS上下文文件系统只提供虚拟目录与虚拟文件，最终的用户文件会分散存储于整个空间中的后台文件服务器中，本发明还需要解决如何通过文件存放方法确定一个最优的存储位置，以保证文件的快速获取的问题；最后考虑到系统中设备存储容量的有限性，还需要对长期不使用的文件，即对长期处于未使用状态的文件进行归档存储处理。In some scenarios of the context file system, it is unavoidable that multiple users read and write the same file. The present invention needs to resolve these conflicts while maintaining the consistency of the namespace; in addition, because the context file based on ContextFS The system only provides virtual directories and virtual files, and the final user files will be scattered and stored in the background file server in the entire space. The present invention also needs to solve how to determine an optimal storage location through the file storage method to ensure the rapid acquisition of files Finally, considering the limited storage capacity of the equipment in the system, it is also necessary to archive and store files that have not been used for a long time, that is, files that have not been used for a long time.
发明内容Contents of the invention
本发明要解决上述技术所存在的缺陷，提供一种基于ContextFS上下文文件系统的文件管理方法，利用上下文驱动来提供主动服务的特性，对ContextFS系统中的文件管理采用不同的存储与管理策略，以提高性能，降低储存代价，并维护命名空间的一致性。The present invention aims to solve the defects of the above-mentioned technologies, and provides a file management method based on the ContextFS context file system, which utilizes the characteristics of active services provided by the context driver, and adopts different storage and management strategies for file management in the ContextFS system, so as to Improve performance, reduce storage costs, and maintain namespace consistency.
本发明解决其技术问题所采用的技术方案：这种基于ContextFS上下文文件系统的文件管理方法，包括下述步骤：The technical solution adopted by the present invention to solve its technical problems: this file management method based on the ContextFS context file system comprises the following steps:
1.1)、用户副本：在上下文文件系统中，如果产生多个用户对同一个文件进行读写的情况，采用用户副本的方法来解决这些冲突，同时又维持命名空间的一致性；1.1) User copy: In the context file system, if multiple users read and write the same file, the user copy method is used to resolve these conflicts while maintaining the consistency of the namespace;
1.2)、文件存放：根据用户自定义、当前上下文、用户偏好多个因素，来决定新创建的用户文件及副本的最终存放位置；1.2), file storage: according to user-defined, current context, and user preferences, the final storage location of newly created user files and copies is determined;
1.3)、文件归档：对长期不使用的文件，即对长期处于未使用状态的文件进行归档存储。1.3) File archiving: archive and store files that have not been used for a long time, that is, files that have not been used for a long time.
本发明中所述用户副本的方法，包括下述步骤：The user replica method described in the present invention includes the following steps:
2.1)、用户A对本文件系统中文件F发出读取请求，系统检查其权限，如果没有读权限则返回读失败；如果有读权限，则读请求会立即将请求的数据返回给用户A；2.1), user A sends a read request to file F in the file system, the system checks its permission, if there is no read permission, it will return read failure; if there is read permission, the read request will immediately return the requested data to user A;
2.2.1)、用户A对本文件系统中文件F发出写入请求，系统检查其权限，如果没有写权限则返回写失败；如果有写权限，则判断文件F的所有者是否是用户A，如果是用户A的文件则返回写成功；2.2.1), user A sends a write request to file F in this file system, the system checks its permission, if there is no write permission, it returns write failure; if there is write permission, then judge whether the owner of file F is user A, if If it is the file of user A, it will return the write success;
2.2.2)、如果不是用户A的文件，则创建用户副本，文件F被复制成文件F.A，文件F.A的元数据被写入文件元数据库，这个副本除了所有者、存储的物理位置和原文件不同外，其它文件元数据都和原文件一致，文件系统设定优先显示用户自身创建的文件F.A，对文件F的操作映射到文件F.A中，在文件F.A中写入数据并返回写成功到用户A。2.2.2), if it is not the file of user A, create a user copy, file F is copied into file F.A, and the metadata of file F.A is written into the file metadata database. This copy is in addition to the owner, the physical location of the storage and the original file Except for the difference, other file metadata are consistent with the original file. The file system setting gives priority to displaying the file F.A created by the user himself. The operation on the file F is mapped to the file F.A, writes data in the file F.A and returns the write success to the user a.
本发明中所述文件存放方法，包括下述步骤：The file storage method described in the present invention comprises the following steps:
3.1)、用户自定义拥有最高优先级，如果用户自定义了文件的存储位置，则根据自定义的位置存放生成的文件；3.1), user-defined has the highest priority, if the user defines the storage location of the file, the generated file will be stored according to the customized location;
3.2)、如果用户没有自定义文件的存放位置，或由于其他原因3.1无法满足，采用该用户的当前上下文信息来决定文件的存放位置，即系统根据当前上下文中的位置信息，选择空间中接近用户的后台设备存放用户文件；3.2), if the user does not customize the storage location of the file, or 3.1 cannot be satisfied due to other reasons, the user's current context information is used to determine the storage location of the file, that is, the system selects the space closest to the user according to the location information in the current context The background device stores user files;
3.3.1)、如果空间中出现多个可供选择的后台文件服务器时，系统将进一步根据当前环境中的上下文信息选择最优设备，存储方法根据用户的文件类型决定，如果是临时文件按照性能优先的原则存放，大文件按照网络带宽优先的原则存放，小文件则根据存储容量平衡的原则存放；3.3.1), if there are multiple optional background file servers in the space, the system will further select the optimal device according to the context information in the current environment, and the storage method is determined according to the user's file type. If it is a temporary file, it will be based on performance The principle of priority is stored, large files are stored according to the principle of network bandwidth priority, and small files are stored according to the principle of storage capacity balance;
3.3.2)、如果空间中没有可选择的后台文件服务器时，根据历史上下文中的用户偏好，选择用户所在组或用户当前角色来选择一个符合用户偏好的远程服务器进行存储。3.3.2), if there is no selectable background file server in the space, according to the user's preference in the historical context, select the user's group or the user's current role to select a remote server that meets the user's preference for storage.
本发明中所述文件归档方法，包括下述步骤：The file archiving method described in the present invention comprises the following steps:
4.1)、系统根据安装了ContextFS的后台文件服务器端存储设备的容量和价格，把它们分为从低到高的多个等级，每个等级对应一个归档时间T；4.1) According to the capacity and price of the background file server-side storage devices installed with ContextFS, the system divides them into multiple levels from low to high, and each level corresponds to an archiving time T;
4.2)、当该处于某个等级的文件A处于未使用状态的时间超过归档时间T，则系统自动对其进行降级归档，即自动将A移动到属于下个等级的存储设备上；4.2), when the unused time of the file A at a certain level exceeds the archiving time T, the system automatically downgrades it for archiving, that is, automatically moves A to a storage device belonging to the next level;
4.3)、被归档的文件只读，一旦进行写操作则产生新的用户副本，归档文件自动删除。4.3), the archived files are read-only, once a write operation is performed, a new user copy will be generated, and the archived files will be automatically deleted.
本发明有益的效果是：1、采用副本和相应管理措施解决多个用户对同一个文件进行读写产生的冲突，同时又维持命名空间的一致性。2、根据用户自定义、当前上下文、用户偏好等因素，确定一个最优的存储位置，以保证文件的快速获取。3、对长期处于未使用状态的文件进行归档存储，降低储存代价。The beneficial effects of the present invention are as follows: 1. Using copies and corresponding management measures to resolve conflicts caused by multiple users reading and writing the same file, while maintaining the consistency of the namespace. 2. According to user-defined, current context, user preference and other factors, determine an optimal storage location to ensure fast access to files. 3. Archive and store long-term unused files to reduce storage costs.
附图说明Description of drawings
图1是本发明副本管理读取过程数据流程图；Fig. 1 is a data flow chart of copy management reading process of the present invention;
图2是本发明副本管理写入过程数据流程图；Fig. 2 is a data flow chart of the copy management writing process of the present invention;
图3是本发明上下文文件系统体系结构示意图；Fig. 3 is a schematic structural diagram of the context file system of the present invention;
具体实施方式Detailed ways
下面结合附图和实施例对本发明作进一步介绍：The present invention will be further described below in conjunction with accompanying drawing and embodiment:
本发明所述的这种基于ContextFS上下文文件系统的副本管理方法，主要包括文件读写方法、文件存放方法和文件归档方法。The copy management method based on the ContextFS context file system described in the present invention mainly includes a file reading and writing method, a file storage method and a file filing method.
一、文件读写方法1. File reading and writing methods
在上下文文件系统的某些场景中，会无法避免的产生多个用户对同一个文件进行读写的情况，本系统采用用户副本的方法来解决这些冲突，同时又维持命名空间的一致性。In some scenarios of the context file system, it is unavoidable that multiple users read and write the same file. This system adopts the method of user copy to resolve these conflicts while maintaining the consistency of the namespace.
1.1)、用户A对本文件系统中文件F发出读取请求(读取请求是从偏移X开始读取Y字节)，系统检查其权限，如果没有读权限则返回读失败；如果有读权限，则读请求会立即将请求的数据返回给用户A；1.1), user A sends a read request to file F in this file system (the read request is to read Y bytes from offset X), the system checks its permissions, and returns read failure if there is no read permission; if there is read permission , the read request will immediately return the requested data to user A;
1.2.1)、用户A对本文件系统中文件F发出写入请求(写入请求是从偏移X开始读取Y字节)，系统检查其权限，如果没有写权限则返回写失败；如果有写权限，则判断文件F的所有者是否是用户A，如果是用户A的文件则返回写成功；1.2.1), user A sends a write request to file F in this file system (the write request is to read Y bytes from offset X), the system checks its permissions, and returns a write failure if there is no write permission; if there is Write permission, then judge whether the owner of file F is user A, if it is user A's file, return write success;
1.2.2)、如果不是用户A的文件，则创建用户副本，文件F被复制成文件F.A，文件F.A的元数据被写入文件元数据库，这个副本除了所有者、存储的物理位置和原文件不同外，其它文件元数据都和原文件一致，文件系统设定优先显示用户自身创建的文件F.A，对文件F的操作映射到文件F.A中，在文件F.A中写入数据并返回写成功到用户A。1.2.2), if it is not the file of user A, create a user copy, file F is copied into file F.A, and the metadata of file F.A is written into the file metadata database. This copy is in addition to the owner, the physical location of the storage and the original file Except for the difference, other file metadata are consistent with the original file. The file system setting gives priority to displaying the file F.A created by the user himself. The operation on the file F is mapped to the file F.A, writes data in the file F.A and returns the write success to the user a.
如图1和图2所示，当用户A对本文件系统中文件F进行读操作时，由于不存在冲突问题，读请求会被立即返回；然而当用户A向文件F写入数据时，由于文件F的所有者和A的用户名不相符(假设F的所有者是public)，这时上下文文件系统会创建一个新的文件副本，除了这个副本的所有者、存储的物理位置和原文件不同外，其它文件元数据都和原文件一致，由于两个文件同名，文件系统将会优先显示用户自身创建的文件，所以在用户A的虚拟目录中文件F被屏蔽，用户A将只能看到副本F.A，这时所有对文件F的操作自然被上下文文件系统映射到文件F.A中。每个用户只要对非自身的文件进行修改就会创建新的属于自己的副本文件，这个副本文件会被存放于用户指定的位置中保存，只改变文件F.A内容，而不改变F.A的元数据，F都不会再现，这就解决了多用户写冲突的问题，同时又维持命名空间的一致性。As shown in Figure 1 and Figure 2, when user A reads file F in this file system, the read request will be returned immediately because there is no conflict problem; however, when user A writes data to file F, due to file The owner of F does not match the user name of A (assuming that the owner of F is public), then the context file system will create a new copy of the file, except that the owner of the copy and the physical location of the storage are different from the original file , other file metadata are consistent with the original file, because the two files have the same name, the file system will display the file created by the user first, so file F is blocked in the virtual directory of user A, and user A will only see the copy F.A, at this time, all operations on file F are naturally mapped to file F.A by the context file system. Each user will create a new copy file that belongs to him as long as he modifies the file that is not his own. This copy file will be stored in the location specified by the user. Only the content of the file F.A will be changed, and the metadata of the F.A will not be changed. F will not be reproduced, which solves the problem of multi-user write conflicts while maintaining the consistency of the namespace.
二、文件存放方法2. File storage method
由于文件系统只提供虚拟目录与虚拟文件，最终的用户文件会分散存储于整个空间中的后台文件服务器中(如图3)，本系统的文件存放方法将确定一个最优的存储位置，以保证文件的快速获取。Because the file system only provides virtual directories and virtual files, the final user files will be scattered and stored in the background file server in the entire space (as shown in Figure 3). The file storage method of this system will determine an optimal storage location to ensure Quick access to files.
新创建的用户文件及副本的存放位置，由多种因素决定。基于ContextFS上下文文件系统的文件存放策略主要根据用户自定义、当前上下文、用户偏好等因素，来决定文件的最终存放位置。文件存放方法具体如下：The storage location of newly created user files and copies is determined by various factors. The file storage strategy based on the ContextFS context file system mainly determines the final storage location of the file based on factors such as user-defined, current context, and user preferences. The file storage method is as follows:
2.1)、用户自定义拥有最高优先级，如果用户自定义了文件的存储位置，则根据自定义的位置存放生成的文件。如：用户A自定义了他的文件存储位置为后台文件服务器中的某台文件服务器(IP地址)，那么A生成的所有文件及副本会被优先保存到这台服务器上。2.1), user-defined has the highest priority, if the user defines the storage location of the file, the generated file will be stored according to the customized location. For example: user A has customized his file storage location as a certain file server (IP address) in the background file server, then all files and copies generated by A will be preferentially saved on this server.
2.2)、如果用户没有自定义文件的存放位置，或由于其他原因2.1无法满足(服务器空间不足等)，那么本系统采用该用户的当前上下文信息来决定文件的存放位置。系统根据当前上下文中的位置信息，选择空间中接近用户的后台设备存放用户文件。如；用户A使用一无线笔记本N，该笔记本N既安装了ContextFS的客户端，又安装了ContextFS的后台文件服务器端，所以该设备既是用户接入层中的前端设备，也是后台文件服务器。如果用户A在使用N的过程中产生了新的用户文件，则在没有提供自定义偏好的情况下，优先存放于最接近用户的服务器N上。如果用户携带的设备没有文件存储能力，则文件会被存放到空间中接近用户并具有存储能力的文件服务器上。2.2), if the user does not customize the storage location of the file, or 2.1 cannot be satisfied due to other reasons (insufficient server space, etc.), then the system uses the user's current context information to determine the storage location of the file. According to the location information in the current context, the system selects a background device close to the user in the space to store user files. For example, user A uses a wireless notebook N, which is installed with both the ContextFS client and the background file server of ContextFS, so this device is not only the front-end device in the user access layer, but also the background file server. If user A generates a new user file in the process of using N, it will be stored on the server N closest to the user first if no custom preference is provided. If the device carried by the user does not have file storage capabilities, the files will be stored on a file server that is close to the user and has storage capabilities.
2.3.1)、如果空间中出现多个可供选择的后台文件服务器时，系统将进一步根据当前环境中的上下文信息选择最优设备，这时考虑的上下文包括服务器的性能，网络带宽，存储容量等多方面。存储策略根据用户的文件类型决定，如果是临时文件按照性能优先的原则存放，大文件按照网络带宽优先的原则存放，小文件则根据存储容量平衡的原则存放。2.3.1), if there are multiple alternative background file servers in the space, the system will further select the optimal device according to the context information in the current environment. The context considered at this time includes server performance, network bandwidth, and storage capacity And many other aspects. The storage policy is determined according to the user's file type. If it is a temporary file, it is stored according to the principle of performance priority, large files are stored according to the principle of network bandwidth priority, and small files are stored according to the principle of storage capacity balance.
2.3.2)、如果空间中没有可选择的后台文件服务器时，根据历史上下文中的用户偏好，选择用户所在组或用户当前角色来选择一个符合用户偏好的远程服务器进行存储。如医生A在公共汽车上，利用自己的手持式设备创建了文件F，车上没有可供存储F的其他设备，且A也没有自定义文件的存储位置，那么系统会根据A的角色医生及其平时文件存放习惯(2.3.1中成功存放的例子)，在他的工作场所(医院)的电脑上创建F。2.3.2), if there is no selectable background file server in the space, according to the user's preference in the historical context, select the user's group or the user's current role to select a remote server that meets the user's preference for storage. For example, if doctor A creates file F with his handheld device on the bus, and there is no other device on the bus that can store F, and A does not customize the storage location of the file, then the system will use A's role as doctor and His usual file storage habits (the example of successful storage in 2.3.1), create F on his workplace (hospital) computer.
三、文件归档3. Document archiving
考虑到系统中设备存储容量的有限性，需要对长期不使用的文件，即对长期处于未使用状态的文件进行归档存储，文件归档策略具体如下：Considering the limited storage capacity of devices in the system, it is necessary to archive and store files that have not been used for a long time, that is, files that have not been used for a long time. The file archiving strategy is as follows:
3.1)、系统根据安装了ContextFS的后台文件服务器端存储设备的容量和价格，把它们分为从低到高的多个等级，每个等级对应一个归档时间T。3.1) According to the capacity and price of the background file server-side storage devices installed with ContextFS, the system divides them into multiple grades from low to high, and each grade corresponds to an archiving time T.
3.2)、当该处于某个等级的文件A处于未使用状态(没有被对应的虚拟文件选中)的时间超过归档时间T，则系统自动对其进行降级归档。即自动将A移动到属于下个等级的存储设备上。3.2), when the file A at a certain level is in the unused state (not selected by the corresponding virtual file) for more than the archiving time T, the system automatically downgrades it for archiving. That is, A is automatically moved to the storage device belonging to the next level.
3.3)、被归档的文件只读，一旦进行写操作则产生新的用户副本，归档文件自动删除。3.3), the archived files are read-only, once a write operation is performed, a new user copy will be generated, and the archived files will be automatically deleted.
Claims (4)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200710069838 CN101079053A (en) | 2007-07-02 | 2007-07-02 | ContextFS based file management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200710069838 CN101079053A (en) | 2007-07-02 | 2007-07-02 | ContextFS based file management method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101079053A true CN101079053A (en) | 2007-11-28 |
Family
ID=38906532
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200710069838 Pending CN101079053A (en) | 2007-07-02 | 2007-07-02 | ContextFS based file management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101079053A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101236569B (en) * | 2008-02-01 | 2010-06-02 | 浙江大学 | An Efficient Dynamic Path Resolution Method Based on ContextFS Context File System |
| CN101840419A (en) * | 2009-03-19 | 2010-09-22 | 赛门铁克公司 | Be used for from the method for integral body backup restore data |
| CN104395898A (en) * | 2012-04-27 | 2015-03-04 | 网络装置公司 | Virtual storage appliance gateway |
| CN105528443A (en) * | 2015-12-23 | 2016-04-27 | 北京金山安全软件有限公司 | Application management method and device and electronic equipment |
| CN105704218A (en) * | 2016-01-19 | 2016-06-22 | 国家电网公司 | Data storage and management method in cloud computing platform |
| CN105740134A (en) * | 2016-01-29 | 2016-07-06 | 浪潮(北京)电子信息产业有限公司 | File based testing method and apparatus |
| CN108806773A (en) * | 2018-05-21 | 2018-11-13 | 上海熙业信息科技有限公司 | Medical image cloud storage platform designing method |
| CN109725997A (en) * | 2018-08-17 | 2019-05-07 | 平安普惠企业管理有限公司 | File open method, terminal and the storage medium of terminal applies |
-
2007
- 2007-07-02 CN CN 200710069838 patent/CN101079053A/en active Pending
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101236569B (en) * | 2008-02-01 | 2010-06-02 | 浙江大学 | An Efficient Dynamic Path Resolution Method Based on ContextFS Context File System |
| CN101840419A (en) * | 2009-03-19 | 2010-09-22 | 赛门铁克公司 | Be used for from the method for integral body backup restore data |
| CN101840419B (en) * | 2009-03-19 | 2015-03-25 | 赛门铁克公司 | Method for restoring data from a monolithic backup |
| CN104395898A (en) * | 2012-04-27 | 2015-03-04 | 网络装置公司 | Virtual storage appliance gateway |
| CN105528443A (en) * | 2015-12-23 | 2016-04-27 | 北京金山安全软件有限公司 | Application management method and device and electronic equipment |
| CN105704218A (en) * | 2016-01-19 | 2016-06-22 | 国家电网公司 | Data storage and management method in cloud computing platform |
| CN105704218B (en) * | 2016-01-19 | 2019-04-05 | 国家电网公司 | Data storage and management method in cloud computing platform |
| CN105740134A (en) * | 2016-01-29 | 2016-07-06 | 浪潮(北京)电子信息产业有限公司 | File based testing method and apparatus |
| CN108806773A (en) * | 2018-05-21 | 2018-11-13 | 上海熙业信息科技有限公司 | Medical image cloud storage platform designing method |
| CN109725997A (en) * | 2018-08-17 | 2019-05-07 | 平安普惠企业管理有限公司 | File open method, terminal and the storage medium of terminal applies |
| CN109725997B (en) * | 2018-08-17 | 2023-11-03 | 顺维(重庆)科技有限公司 | File opening method for terminal application, terminal and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11593319B2 (en) | Virtualized data storage system architecture | |
| US11630807B2 (en) | Garbage collection for objects within object store | |
| US11797477B2 (en) | Defragmentation for objects within object store | |
| US11144503B2 (en) | Snapshot storage and management within an object store | |
| CN101079053A (en) | ContextFS based file management method | |
| US8892846B2 (en) | Metadata management for virtual volumes | |
| US20240184746A1 (en) | Metadata attachment to storage objects within object store | |
| US10467188B2 (en) | In-line policy management with multi-level object handle | |
| KR101137299B1 (en) | Hierarchical storage management for a file system providing snapshots | |
| US7765189B2 (en) | Data migration apparatus, method, and program for data stored in a distributed manner | |
| US9565254B2 (en) | Object location service for network-based content repository | |
| US7640262B1 (en) | Positional allocation | |
| US8180813B1 (en) | Content repository implemented in a network storage server system | |
| US9460177B1 (en) | Managing updating of metadata of file systems | |
| US8938425B1 (en) | Managing logical views of storage | |
| US20130232215A1 (en) | Virtualized data storage system architecture using prefetching agent | |
| US9542401B1 (en) | Using extents of indirect blocks for file mapping of large files | |
| US20090265519A1 (en) | Method and system for power aware i/o scheduling | |
| WO2019015479A1 (en) | Method for achieving data copying in ftl of solid state drive, system and solid state drive | |
| CN1848118A (en) | Device and method for managing file system | |
| CN1904889A (en) | Method for storing metadata of logic document system by adhesion property | |
| US9195686B2 (en) | Optimistic versioning concurrency scheme for database streams | |
| Whitehouse | The GFS2 filesystem | |
| CN1813253A (en) | Detection and alerting of viruses in a shared read-only file system | |
| CN110134509A (en) | A data caching method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20071128 |