WO2023077283A1 - Procédé et appareil de gestion de fichier, et dispositif électronique - Google Patents

Procédé et appareil de gestion de fichier, et dispositif électronique Download PDF

Info

Publication number
WO2023077283A1
WO2023077283A1 PCT/CN2021/128271 CN2021128271W WO2023077283A1 WO 2023077283 A1 WO2023077283 A1 WO 2023077283A1 CN 2021128271 W CN2021128271 W CN 2021128271W WO 2023077283 A1 WO2023077283 A1 WO 2023077283A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
status
state
target file
latest
Prior art date
Application number
PCT/CN2021/128271
Other languages
English (en)
Chinese (zh)
Inventor
萨塔德卡尔•罗希特•兰吉特
瓦什尼•萨迈尔
冯永刚
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2021/128271 priority Critical patent/WO2023077283A1/fr
Publication of WO2023077283A1 publication Critical patent/WO2023077283A1/fr

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/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems

Definitions

  • the present application relates to the technical field of data security, in particular to a file management method, device and electronic equipment.
  • the storage field has higher and higher requirements for data security. Some files can only be read or deleted after being written, and cannot be modified.
  • the WORM (write once, read many, write once, read many) mechanism can exactly meet this requirement.
  • each file in the directory must correspond to a file status, and the status of the file includes unprotected status, protected status, expired status and deleted status. If a file is submitted to a protected state (hereinafter also referred to as a WORM state), the file is allowed to be read but not modified or deleted.
  • determining the latest status of a file is generally implemented based on a scanner. Use the scanner to continuously scan and query the entire file directory with WORM attributes set, and then calculate and judge the latest status of the file. This method of actively updating the file state occupies a large amount of processing and computing resources, and is inefficient.
  • the present application provides a file management method, device and electronic equipment, which are used to solve the problem in the related art that updating file status based on a scanner occupies a large amount of processing and computing resources and is inefficient.
  • the present application provides a file management method, which can be executed by the electronic device provided in the present application, and the method includes:
  • the target file has a read-many-write WORM attribute
  • the method further includes: responding to the file operation request according to the latest file status of the target file.
  • the latest file status is determined first, and then the file operation request is executed based on the latest file status, which can ensure that the file operation request is executed in an accurate file status. For example, determining the latest file status as the protected status can effectively protect the file.
  • the file status includes one of an unprotected status, a protected status, an expired status, and a deleted status.
  • any file state in the WORM mechanism can be switched through a file operation request, which can improve the efficiency of file state management compared to the scanner method.
  • the file state includes an unprotected state
  • the state transition parameters corresponding to the unprotected state include a waiting period for automatically submitting a protected state and the last modification time of the target file
  • the updating of the latest file status of the target file according to the current file status and status transition parameters includes:
  • an efficient way of automatically submitting the worm state is provided.
  • Executed file operation requests are limited, so as to achieve the purpose of protecting files in time.
  • the file state includes a protection state, and a state transition parameter corresponding to the protection state includes an expiration time of a protection period;
  • the updating of the latest file status of the target file according to the current file status and status transition parameters includes:
  • an efficient way of transitioning to an expired state is provided.
  • first update the latest file status to the expired status and then respond to the file operation request make up for the lag of the file status update, so that the expired status can support more file operations than the WORM status ask.
  • the file state includes an expired state
  • the state transition parameters corresponding to the expired state include the retention period of the target file and the expiration time of the protection period
  • the updating of the latest file status of the target file according to the current file status and status transition parameters includes:
  • determining the expiration time of the protection period includes:
  • the expiration time of the protection period is determined based on the last modification time of the target file, the duration of the protection period, and the waiting period for automatic submission of protection status.
  • the responding to the file operation request according to the latest file status of the target file includes:
  • the read request can be responded to based on the latest file state, so as to ensure that the execution result conforms to the execution result that the WORM mechanism should have at the current time.
  • the responding to the file operation request according to the latest file status of the target file includes:
  • the write request can be responded based on the latest file status, so that the execution result conforms to the execution result that the WORM mechanism should have at the current time.
  • the responding to the file operation request according to the latest file status of the target file includes:
  • a deleted prompt message is returned.
  • the deletion request can be responded to based on the latest file status, so that the execution result conforms to the execution result that the WORM mechanism should have at the current time.
  • the present application provides a file management device, the device comprising:
  • a receiving module configured to receive a file operation request for a target file, the target file having a read-many-write WORM attribute
  • a parameter acquisition module configured to acquire the current file state and state transition parameters of the target file
  • a status update module configured to update the latest file status of the target file according to the current file status and status transition parameters.
  • the device further includes:
  • a response module configured to respond to the file operation request according to the latest file status of the target file.
  • the file status includes one of an unprotected status, a protected status, an expired status, and a deleted status.
  • the file state includes an unprotected state
  • the state transition parameters corresponding to the unprotected state include a waiting period for automatically submitting a protected state and the last modification time of the target file
  • the status update module is specifically used for:
  • the file state includes a protection state, and a state transition parameter corresponding to the protection state includes an expiration time of a protection period;
  • the status update module is specifically used for:
  • the WORM clock is greater than the expiration time of the protection period, then update the latest file status of the target file to be an expired state.
  • the file state includes an expired state
  • the state transition parameters corresponding to the expired state include the retention period of the target file and the expiration time of the protection period
  • the status update module is specifically used for:
  • the device further includes:
  • An expiration time determining module configured to determine the expiration time of the protection period based on the last modification time of the target file, the duration of the protection period, and the waiting period for automatic submission of protection status.
  • the response module is configured to:
  • the response module is specifically configured to:
  • the response module is specifically configured to:
  • a deleted prompt message is returned.
  • the present application provides an electronic device, the electronic device includes: one or more processors; one or more memories; wherein, the one or more memories store readable programs, when the readable When the read program is executed by the processor, the storage device is made to execute the method described in any one of the above first aspects.
  • the present application provides a computer-readable storage medium, the computer-readable storage medium includes computer instructions, and when the computer instructions are run on a computer, the computer executes the computer as described in any one of the above-mentioned first aspects. described method.
  • the present application provides a computer program product, the computer program product includes computer instructions, and when the computer instructions are run on a computer, the computer executes the computer program described in any one of the above first aspects. method.
  • FIG. 1 is one of the schematic diagrams of file state transition provided by the embodiment of the present application.
  • FIG. 2 is the second schematic diagram of file state transition provided by the embodiment of the present application.
  • FIG. 3 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a file management method provided in an embodiment of the present application.
  • Fig. 5 is another schematic flowchart of the file management method provided by the embodiment of the present application.
  • FIG. 6 is another schematic flowchart of the file management method provided by the embodiment of the present application.
  • FIG. 7 is another schematic flowchart of the file management method provided by the embodiment of the present application.
  • FIG. 8 is another schematic flowchart of the file management method provided by the embodiment of the present application.
  • FIG. 9 is a structural block diagram of a file management device provided by an embodiment of the present application.
  • FIG. 10 is a structural block diagram of an electronic device provided by an embodiment of the present application.
  • first and second in the specification and drawings of the present application are used to distinguish different objects, or to distinguish different processes for the same object, rather than to describe a specific sequence of objects.
  • the terms “including” and “having” mentioned in the description of the present application and any variations thereof are intended to cover non-exclusive inclusion.
  • a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes other unlisted steps or units, or optionally also includes Other steps or elements inherent to the process, method, product or apparatus are included.
  • words such as “exemplary” or “for example” are used as examples, illustrations or descriptions.
  • WORM mechanism which can realize the technology of writing once and reading many times. That is, write once, read many times.
  • WROM attribute When a directory is set to have the WROM attribute, all files in the directory will also have the WORM attribute, and each file will be determined as one of the following file states:
  • WORM state also known as protected state, in this state the file is only allowed to be read and cannot be modified or deleted. However, the WORM state has a protection period. After the protection period, the WORM state ends and enters the expired state.
  • Overdue state in which the file can be read or deleted, and whether modification is allowed can be determined according to the pre-configured expiration policy, which can be configured by the user. For example, if the user configures the expiration policy as modifiable, the file is allowed to be modified in the expired state.
  • the WORM attribute includes multiple WORM parameters for determining whether to convert the file status.
  • the directory becomes the WORM root directory, and all new subdirectories and files under it will automatically inherit the WORM attribute of the WORM root directory.
  • the WORM parameters that can be set by the user include: the maximum protection period, the minimum protection period, the default protection period, the waiting time for automatically submitting the protection state, and the retention time.
  • the retention period may not be set in the WORM attribute, and the file can be kept after the protection period expires, and manual deletion is allowed.
  • the conversion process of the file state is described.
  • the file After the file is created, it first enters the unprotected state. In this state, the file can be modified, and the last modification time t 1 of the file is recorded. From t 1 , if the waiting time T 1 of the automatic submission protection state has passed and the time t 2 is not reached If it is modified again, the file will be submitted to WORM state to enter the protection period. The duration of the protection period is T 2 , counting from the time point t 2 , if the protection period T 2 reaches the time point t 3 , the protection period expires, and the file will enter the expired state at this time. The file is deleted when the time point t4 is reached after the retention period T3 .
  • the WORM attribute of the WORM root directory is set, modification and viewing are allowed.
  • the files under the WORM root directory all inherit the WORM attribute, the actual protection period of each file can be modified as needed.
  • the WORM mechanism will record the expiration time of the protection period, and the user can modify the expiration time to modify the protection period.
  • the expiration time the last modification time + the waiting time for automatically submitting the protection state + the default protection period.
  • This expiration time and the file's last modification time can be stored in the file's metadata, such as:
  • atime (Access time, access time) in the file metadata: used to record the expiration time of the file.
  • the purpose of extending the file protection period can be achieved by modifying the atime in the file metadata. It should be noted that the modified atime of a file is only valid for the file and will not affect the WORM attribute, and new files under the WORM root directory still inherit the WORM attribute of the WORM root directory.
  • mtime Modify time, modification time
  • file metadata used to record the last modification time of the file.
  • the file is in the unprotected state at first, and enters the protected state after the WORM state is submitted manually or automatically. After the protection period expires, the file enters the expired state. If you modify the expiration time of the file in the expired state, you can extend the protection period and re-enter the protected state. Of course, in the protected state, the protection period can also be extended or shortened by modifying the expiration time of the file. Among them, the calculation method of the expiration time of the protection period is as follows:
  • the WORM attribute can be stored in the file directory or in the file metadata.
  • some WORM parameters can also be stored in the file object, and some WORM parameters can be stored in the file metadata, which are applicable to the embodiment of this application. .
  • the file system is the method and data structure used by the operating system to specify files on storage devices (commonly disks, and solid-state drives based on NAND Flash (computer cache devices)) or partitions; that is, the organization of files on storage devices method.
  • the software mechanism in the operating system responsible for managing and storing file information is called the file system.
  • the file system consists of three parts: the interface of the file system, the software collection for operating and managing objects, objects and attributes. From a system point of view, a file system is a system that organizes and allocates space on file storage devices, is responsible for file storage, and protects and retrieves stored files. Specifically, it is responsible for creating files for users, storing, reading, modifying, and dumping files, etc.
  • WORM clock In order to avoid changes in the actual protection time of files caused by changes in the local time of the storage cluster, a set of independent clocks, that is, WORM clocks, are designed for file status conversion.
  • the WORM clock if the WORM clock is less than the cluster time, the WORM clock will be adjusted by catching up with the cluster time by 1 second every certain period of time, such as tens of seconds, until it catches up with the cluster time. If the WORM clock is greater than the cluster time, the WORM clock will be directly adjusted to the cluster time.
  • each file in the directory must correspond to a file state, and the state of the file includes unprotected state, WORM state, expired state and deleted state.
  • the status of the file can be updated through the scanner.
  • the scanner-based approach needs to scan the entire file directory with the WORM attribute set, which is inefficient and consumes CPU computing resources. Taking submitting the WORM status as an example, the scanner needs to scan each file in the file directory with the WORM attribute set, obtain the last modification time of the file, and then determine whether to submit the WORM status according to the waiting time for automatically submitting the WORM status in the WORM attribute .
  • an embodiment of the present application provides a file management method.
  • this method it is not necessary to use the scanner to "actively” detect whether each file should switch state, but to "passively” change the state of the file.
  • the state transition to the corresponding file is triggered by the file operation request.
  • the file management method provided by the embodiment of the present application can improve file management efficiency and save CPU computing resources because it does not need to scan the entire file directory with the WORM attribute set.
  • FIG. 3 is a schematic diagram of an application scenario of the file management method provided by the embodiment of the present application, and the application scenario includes a user 301 , a terminal device 302 and a server 303 .
  • the terminal device 302 includes, but is not limited to, electronic devices such as desktop computers, mobile computers, and tablet computers.
  • the server 303 may be a server, a server cluster composed of several servers, or a cloud computing center.
  • the server 303 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, and can also provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, Cloud servers for basic cloud computing services such as middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.
  • Operable files are stored in the server 303 .
  • the terminal device 302 is used to display a user interface. Based on the user interface, users can set WORM attributes for directories in the file system, modify and view WORM attributes, and users can also perform read/write operations on files.
  • the user 301 can send a file operation request to the server 303 through the terminal device 302 . Based on the file operation request, the server 303 first judges whether the file to be operated needs to change state, and then responds to the file operation request according to the latest state of the file.
  • the system architecture of the terminal device 302 is shown in FIG. 3 .
  • Application programs and a VFS system are implemented in the terminal device 302.
  • the file system is implemented in the server 303, and the file system contains a WORM component.
  • the WORM component can be a software module, a processor, or a combination of software and hardware, and is used to implement the file management method provided by the embodiment of the present application.
  • the file system running on the server 303 is the file system implementing the WORM mechanism in the embodiment of the present application.
  • the application program running on the terminal device 302 provides a human-computer interaction function, and the user can set, modify and view WORM attributes through the application program. Read/write operations to files can also be implemented.
  • the VFS system running in the terminal device 302 provides a unified abstract interface for different file systems. Therefore, multiple file systems of different types can be seamlessly used through VFS.
  • the applications in Figure 3 use the file system via this interface.
  • the access request to file A is transmitted to the file system in the server 303 through the VFS system running on the terminal device, and the WORM component in the file system determines file A based on the access request. Whether to convert the file status, if necessary, first convert the file status and then respond to the access request.
  • Step 401 Receive a file operation request for a target file.
  • the target file in the embodiment of the present application refers to a file with WORM attribute.
  • the file operation request may be a read/write (I/O) operation on file content, or a read/write operation on metadata of the file.
  • Step 402 Obtain the current file state and state transition parameters of the target file.
  • the file state of each file can be maintained by a corresponding file attribute.
  • the attribute value of the file attribute can be read to obtain the current file status of the target file.
  • the state conversion parameter is used to determine whether to convert the file state, which may include the WORM parameters described above and/or parameters in the file metadata, etc., which parameters are specifically determined according to the current state of the target file, for example:
  • the obtained state transition parameters include the waiting time for automatically submitting the protection state in the WORM attribute and the last modification time mtime of the target file in the file metadata;
  • the obtained state transition parameters include the expiration time atime of the protection period in the file metadata
  • the obtained status transition parameters include the retention period in the WORM attribute and the expiration time atime of the protection period in the file metadata.
  • Step 403 Update the latest file status of the target file according to the current file status and status transition parameters.
  • Step 501 Obtain the last modification time of the target file and the waiting time for automatic submission of protection status.
  • Step 502 Determine the first time difference between the last modification time of the target file and the WORM clock.
  • Step 503 Comparing the waiting time of the automatic submission protection state with the first time difference.
  • Step 504 If the first time difference is greater than the waiting time for automatically submitting the protected status, update the latest file status of the target file to the protected status.
  • Step 505 If the first time difference is less than or equal to the waiting time for automatically submitting the protected state, then determine that the latest file state of the target file is an unprotected state, and the file state does not need to be converted at this time.
  • the waiting time for automatic submission of protection status is 1 hour
  • the last modification time of file A is Tim1
  • read the last modification time Tim1 from the metadata of file A after receiving the file operation request for file A and then calculate the time difference ⁇ T 1 between Tim1 and the WORM clock, if ⁇ T 1 is less than or equal to 1 hour, it means that the requirement for automatic submission of WORM status has not been met, and file A continues to remain in the unprotected state. In this state, file A Can be modified, read or deleted. If ⁇ T 1 is greater than 1 hour, file A is automatically submitted to WORM state.
  • Step 601 Obtain the expiration time of the protection period of the target file.
  • Step 602 Compare the expiration time of the protection period with the size of the WORM clock.
  • Step 603 If the WORM clock is greater than the expiration time of the protection period, update the latest file status of the target file to the expired status.
  • Step 604 If the WORM clock is less than or equal to the expiration time of the protection period, determine that the latest file status of the target file is the protected status, and the file status does not need to be converted at this time.
  • the time of the WORM clock is Tim4.
  • the time of the WORM clock is Tim4.
  • the conversion to the expired state may be implemented by setting the file attribute of file A to the attribute value corresponding to the expired state.
  • Step 701 Obtain the expiration time of the protection period.
  • Step 702 Determine a second time difference between the expiration time of the protection period and the WORM clock.
  • step 703 compare the second time difference with the retention time.
  • step 704 if the second time difference is greater than the retention time, the latest file status of the update target file is a deleted status.
  • step 705 if the second time difference is less than or equal to the retention time, it is determined that the latest file status of the target file is expired, and the file status does not need to be converted at this time.
  • ⁇ T 2 For example, after receiving a file operation request for file A, read the metadata atime of file A, get the expiration time Tim3 of the protection period, and then calculate the time difference ⁇ T 2 between Tim3 and WORM clock Tim4, if ⁇ T 2 is less than or equal to the retention period T3, then file A remains in the expired state. If ⁇ T 2 is greater than T3, it means that the retention period is too long and file A needs to be deleted.
  • Step 405 Respond to the file operation request according to the latest file status of the target file.
  • responding to the file operation request according to the latest file status can be implemented as the operation shown in Figure 8, including:
  • Step 801 Obtain the latest file status of the target file.
  • step 802 respond to the write request to the file content according to the situation, wherein:
  • new data can be written to the file, data can be modified, and data can be deleted.
  • the expiration policy can define whether the file can be modified after the protection period expires. If the modification is allowed, the file attribute supports write operations, and then the file can be modified in the expired state, otherwise it cannot be modified.
  • the user first requests to write data to file A, then based on the request, it is first judged whether to change the state based on the request. If it is determined that file A is in the expired state and the retention time is exceeded, delete A, and then respond to the request , it will feed back a prompt message that the file A has been deleted.
  • Step 801 Obtain the latest file status of the target file.
  • Step 803 Respond to the read request for file content according to the situation, wherein:
  • Step 801 Obtain the latest file status of the target file.
  • Step 804 Respond to the file deletion request according to the situation, wherein:
  • the user first requests to delete file A, based on the request, it is first judged whether to change the state. If it is determined that file A is in the expired state and the retention time is too long, A will be deleted, and then when the deletion request is responded to, it is known that the file has been deleted. The deleted prompt message will be fed back.
  • the file operation request in the embodiment of the present application may also be a read/write operation request for the metadata of the target file.
  • the target file is in any state of unprotected state, protected state and expired state, If the metadata supports read/write operations, the read/write operation request on the metadata can be fulfilled.
  • read/write requests to metadata fail.
  • the status of the file may be progressive, for example, as shown in FIG. 1 , the unprotected status enters the protected status, the protected status enters the expired status, and then enters the deleted status.
  • cross-state transitions can also be implemented. For example, after receiving a file operation request, due to the long time since the last re-determined file state, the file state transition may cause a cross-state transition. Exemplarily, determining which state the file enters based on the current file state may include the following situations:
  • this embodiment describes the transition process of the file from the unprotected state to the expired state, and the transition process of the file from the unprotected state to the deleted state.
  • the current file status is protected. If the time since the last file operation request is long, you can compare the expiration time of the protection period of the file with the current time. If the current time is greater than or equal to the expiration time, the file status may be There are two situations, one is that the file is currently expired, and the other is that the file should be deleted after the expiration time. Therefore, the time difference between the current time and the expiration time can be further determined. If the time difference is less than the retention time, the file should be in an expired state. If the time difference is greater than or equal to the retention time, the file should be deleted.
  • this embodiment describes the transition process of a file from a protected state to a deleted state.
  • the embodiment of the present application compares two parameters (such as the expiration time and the current time), it often involves the situation that the two parameters are equal. In the case of equality, the state may or may not be converted. For example, when the expiration time is equal to the current time When the time is determined, it can be determined whether to remain in the protected state or to enter the expired state. During specific implementation, it can be determined according to the actual situation, and both are applicable to the embodiments of this application.
  • the embodiment of the present application also provides a file management device, as shown in FIG. 9, the device 900 includes:
  • the receiving module 901 is configured to receive a file operation request for a target file, and the target file has a read-many-write WORM attribute;
  • a parameter acquisition module 902 configured to acquire the current file state and state transition parameters of the target file
  • a status update module 903, configured to determine the latest file status of the target file according to the current file status and status transition parameters.
  • the device further includes:
  • a response module 904 configured to respond to the file operation request according to the latest file status of the target file.
  • the file status includes one of an unprotected status, a protected status, an expired status, and a deleted status.
  • the file state includes an unprotected state
  • the state transition parameters corresponding to the unprotected state include a waiting period for automatically submitting a protected state and the last modification time of the target file
  • the status update module is specifically used for:
  • the first time difference is less than or equal to the waiting time of the automatic submission protection state, then it is determined that the latest file state of the target file is an unprotected state.
  • the file state includes a protection state, and a state transition parameter corresponding to the protection state includes an expiration time of a protection period;
  • the status update module is specifically used for:
  • the WORM clock is less than or equal to the expiration time of the protection period, it is determined that the latest file status of the target file is the protection status.
  • the file state includes an expired state
  • the state transition parameters corresponding to the expired state include the retention period of the target file and the expiration time of the protection period
  • the status update module is specifically used for:
  • the second time difference is less than or equal to the retention period, it is determined that the latest file status of the target file is an expired status.
  • the device further includes:
  • An expiration time determining module 905 configured to determine the expiration time of the protection period based on the last modification time of the target file, the duration of the protection period, and the waiting time for automatic submission of protection status.
  • the response module is configured to:
  • the response module is specifically configured to:
  • the response module is specifically configured to:
  • a deleted prompt message is returned.
  • the embodiment of the present application also provides an electronic device.
  • the electronic device may have the structure shown in FIG. 10.
  • the electronic device may be a computer device (such as the server 303 shown in FIG. The chip or chip system of the above method.
  • the electronic device shown in FIG. 10 may include at least one processor 1001, and the at least one processor 1001 is used to be coupled with a memory, read and execute instructions in the memory to implement the file management method provided by the embodiment of the present application A step of.
  • the electronic device may further include a communication interface 1002, configured to support the electronic device in receiving or sending signaling or data.
  • the communication interface 102 in the electronic device can be used to realize interaction with other electronic devices.
  • the processor 101 may be configured to enable the electronic device to execute the steps in any of the methods shown in FIGS. 4-8 .
  • the electronic device may also include a memory 103, in which computer instructions are stored, and the memory 103 may be coupled with the processor 101 and/or the communication interface 102, and is used to support the processor 101 to call the computer instructions in the memory 103 to implement The steps in the method shown in any one of Figures 4-8; in addition, the memory 103 can also be used to store the data involved in the method embodiment of the present application, for example, to store the data necessary to support the communication interface 102 to realize interaction , instructions, and/or are used to store configuration information such as WORM attributes necessary for the electronic device to execute the method described in the embodiment of the present application.
  • the memory 103 can also be used to store the data involved in the method embodiment of the present application, for example, to store the data necessary to support the communication interface 102 to realize interaction , instructions, and/or are used to store configuration information such as WORM attributes necessary for the electronic device to execute the method described in the embodiment of the present application.
  • the embodiment of the present application also provides a computer-readable storage medium.
  • Computer instructions are stored on the computer-readable storage medium. When these computer instructions are called and executed by a computer, the computer can complete any one of the above-mentioned method embodiments and method embodiments. methods involved in a possible design.
  • the computer-readable storage medium is not limited, for example, it may be RAM (random-access memory, random access memory), ROM (read-only memory, read-only memory), etc.
  • the present application also provides a computer program product.
  • the computer program product includes computer instructions. When the computer instructions are run on the computer, the computer can complete any possible design of the above-mentioned method embodiments and method embodiments. methods involved.
  • the present application also provides a chip, which may include a processor and an interface circuit, and is used to implement the method involved in the foregoing method embodiment and any possible implementation manner of the method embodiment.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software it may be implemented in whole or in part in the form of computer instructions.
  • the computer instructions When the computer instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber) or wireless (eg, infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data electronic device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (Solid State Disk, SSD)), etc.
  • a magnetic medium such as a floppy disk, a hard disk, or a magnetic tape
  • an optical medium such as a DVD
  • a semiconductor medium such as a solid state disk (Solid State Disk, SSD)
  • the steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, a software unit executed by a processor, or a combination of both.
  • the software unit may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other storage medium in the art.
  • the storage medium can be connected to the processor, so that the processor can read information from the storage medium, and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium can be set in the ASIC, and the ASIC can be set in the terminal device.
  • the processor and the storage medium may also be disposed in different components in the terminal device.
  • These computer instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device Steps are provided for implementing the functions specified in the flow chart or flow charts and/or block diagram block or blocks.

Landscapes

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

Abstract

La présente demande se rapporte au domaine technique de la sécurité des données, et divulgue un procédé et un appareil de gestion de fichier, ainsi qu'un dispositif électronique, qui permettent de résoudre les problèmes dans la technologie associée selon lesquels un grand nombre de ressources informatiques de traitement sont occupées par la mise à jour de l'état des fichiers sur la base d'un dispositif de balayage et selon lesquels l'efficacité est faible. Dans la présente demande, plutôt que de devoir détecter " activement " l'état de fichier le plus récent de chaque fichier à l'aide d'un dispositif de balayage, le dernier état de fichier est mis à jour " passivement ". Pendant la mise en œuvre, pour n'importe quel fichier cible, l'état de fichier le plus récent du fichier cible est mis à jour uniquement lorsqu'une demande d'opération de fichier correspondant au fichier cible est reçue. L'état de fichiers sans demandes d'opération de fichier reste inchangé par défaut. Étant donné qu'il n'est pas nécessaire qu'un système entier de fichier WORM soit balayé, l'efficacité de gestion de fichier peut être améliorée, et les ressources informatiques de CPU sont conservées.
PCT/CN2021/128271 2021-11-02 2021-11-02 Procédé et appareil de gestion de fichier, et dispositif électronique WO2023077283A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/128271 WO2023077283A1 (fr) 2021-11-02 2021-11-02 Procédé et appareil de gestion de fichier, et dispositif électronique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/128271 WO2023077283A1 (fr) 2021-11-02 2021-11-02 Procédé et appareil de gestion de fichier, et dispositif électronique

Publications (1)

Publication Number Publication Date
WO2023077283A1 true WO2023077283A1 (fr) 2023-05-11

Family

ID=86240485

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/128271 WO2023077283A1 (fr) 2021-11-02 2021-11-02 Procédé et appareil de gestion de fichier, et dispositif électronique

Country Status (1)

Country Link
WO (1) WO2023077283A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108984437A (zh) * 2018-06-28 2018-12-11 郑州云海信息技术有限公司 一种存储对象防篡改方法、装置及设备
CN109117667A (zh) * 2018-07-27 2019-01-01 郑州云海信息技术有限公司 一种文件保护方法、系统、设备及计算机可读存储介质
US20190034295A1 (en) * 2017-07-25 2019-01-31 Hubstor Inc. Methods and systems relating to network based storage
CN109542850A (zh) * 2018-11-20 2019-03-29 郑州云海信息技术有限公司 一种文件的worm属性更新方法、装置、设备及介质
CN109669923A (zh) * 2018-12-03 2019-04-23 郑州云海信息技术有限公司 一种worm状态自动判断方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190034295A1 (en) * 2017-07-25 2019-01-31 Hubstor Inc. Methods and systems relating to network based storage
CN108984437A (zh) * 2018-06-28 2018-12-11 郑州云海信息技术有限公司 一种存储对象防篡改方法、装置及设备
CN109117667A (zh) * 2018-07-27 2019-01-01 郑州云海信息技术有限公司 一种文件保护方法、系统、设备及计算机可读存储介质
CN109542850A (zh) * 2018-11-20 2019-03-29 郑州云海信息技术有限公司 一种文件的worm属性更新方法、装置、设备及介质
CN109669923A (zh) * 2018-12-03 2019-04-23 郑州云海信息技术有限公司 一种worm状态自动判断方法及系统

Similar Documents

Publication Publication Date Title
US10896102B2 (en) Implementing secure communication in a distributed computing system
KR20200093597A (ko) 콘텐츠 아이템의 동기화를 위한 고유 식별자의 할당 및 재할당
US10885060B2 (en) On-demand file synchronization
US11709841B2 (en) Methods for updating reference count and shared objects in a concurrent system
CN110046133B (zh) 一种存储文件系统的元数据管理方法、装置及系统
US10097659B1 (en) High performance geographically distributed data storage, retrieval and update
US10235047B2 (en) Memory management method, apparatus, and system
WO2019061352A1 (fr) Procédé et dispositif de chargement de données
US9910881B1 (en) Maintaining versions of control plane data for a network-based service control plane
WO2019109854A1 (fr) Procédé et dispositif de traitement de données pour base de données distribuée, support d'informations, et dispositif électronique
US20170153909A1 (en) Methods and Devices for Acquiring Data Using Virtual Machine and Host Machine
US20210216523A1 (en) Data Storage Method, Metadata Server, and Client
CN109522043B (zh) 一种配置数据的管理方法、装置及存储介质
US20230101774A1 (en) Techniques for performing clipboard-to-file paste operations
US20210374107A1 (en) Distributed file system and distributed file managing method
US7418478B1 (en) System and method for application discovery in a computing environment
US20110302138A1 (en) Network aware storage device
US20110208761A1 (en) Coordinating content from multiple data sources
CN112433921A (zh) 用于动态埋点的方法及设备
CN109165078B (zh) 一种虚拟分布式服务器及其访问方法
WO2023077283A1 (fr) Procédé et appareil de gestion de fichier, et dispositif électronique
TWI571754B (zh) 用來進行檔案同步控制之方法與裝置
US9529812B1 (en) Timestamp handling for partitioned directories
US10015248B1 (en) Syncronizing changes to stored data among multiple client devices
CN111078643B (zh) 一种批量删除文件的方法、装置及电子设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE