US11886383B2ActiveUtilityA1
Method, device and computer program product for managing file system
Est. expiryJan 21, 2041(~14.5 yrs left)· nominal 20-yr term from priority
G06F 16/128G06F 16/122G06F 16/16G06M 1/27G06F 16/1734
54
PatentIndex Score
0
Cited by
22
References
19
Claims
Abstract
Techniques for managing a file system involve: receiving an event published by the file system, the event being associated with an operation on an object in the file system; determining a value of a counter corresponding to the event based on execution information of the operation; determining a target action corresponding to the value of the counter based on a trigger strategy associated with the counter, the trigger strategy defining at least one action that can be triggered by the counter; and generating an indication for causing the file system to execute the target action. Accordingly, file system management in finer granularity can be provided.
Claims
exact text as granted — not AI-modifiedThe invention claimed is:
1. A method for managing a file system, comprising:
receiving an event published by a file system, the event being associated with an operation on an object in the file system;
determining a value of a counter corresponding to the event based on execution information of the operation;
determining a target action corresponding to the value of the counter based on a trigger strategy associated with the counter, the trigger strategy defining at least one action that can be triggered by the counter; and
generating an indication for causing the file system to execute the target action;
wherein the event is published by the file system prior to executing the operation on the object in the file system; and
wherein the method further comprises:
after generating the indication, executing the target action in the file system; and
based on an execution result of the target action,
executing the operation on the object in the file system.
2. The method according to claim 1 , further comprising:
determining the execution information of the operation based on an event type of the event.
3. The method according to claim 2 , wherein the event type indicates that the event is published in response to receiving a request associated with the operation, and determining the execution information comprises:
acquiring the execution information, the execution information indicating whether the operation is allowed to be executed.
4. The method according to claim 3 , wherein determining the value of the counter corresponding to the event comprises:
in response to determining that the execution information indicates that the operation is allowed to be executed, incrementing the counter to determine the value of the counter.
5. The method according to claim 2 , wherein the execution information comprises an execution status of the operation, and wherein determining the execution information of the operation comprises:
determining the execution status of the operation based on the event type, the execution status indicating that the operation is executed successfully or unsuccessfully.
6. The method according to claim 1 , wherein the at least one action corresponds to a corresponding trigger threshold of the counter, and determining the target action corresponding to the value of the counter comprises:
determining the target action from the at least one action based on comparison of the value with the corresponding trigger threshold.
7. The method according to claim 1 , further comprising:
resetting the counter.
8. The method according to claim 1 , wherein the operation comprises at least one of the following operations on files or directories in the file system: read operation, create operation, modify operation, or delete operation.
9. An electronic device, comprising:
at least one processing unit;
at least one memory that is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit, wherein the instructions, when executed by the at least one processing unit, cause the device to execute actions comprising:
receiving an event published by a file system, the event being associated with an operation on an object in the file system;
determining a value of a counter corresponding to the event based on execution information of the operation;
determining a target action corresponding to the value of the counter based on a trigger strategy associated with the counter, the trigger strategy defining at least one action that can be triggered by the counter; and
generating an indication for causing the file system to execute the target action;
wherein the event is published by the file system prior to executing the operation on the object in the file system; and
wherein the method further comprises:
after generating the indication, executing the target action in the file system; and
based on an execution result of the target action,
executing the operation on the object in the file system.
10. The device according to claim 9 , wherein the actions further comprise:
determining the execution information of the operation based on an event type of the event.
11. The device according to claim 10 , wherein the event type indicates that the event is published in response to receiving a request associated with the operation, and determining the execution information comprises:
acquiring the execution information, the execution information indicating whether the operation is allowed to be executed.
12. The device according to claim 11 , wherein determining the value of the counter corresponding to the event comprises:
in response to determining that the execution information indicates that the operation is allowed to be executed, incrementing the counter to determine the value of the counter.
13. The device according to claim 10 , wherein the execution information comprises an execution status of the operation, and wherein determining the execution information of the operation comprises:
determining the execution status of the operation based on the event type, the execution status indicating that the operation is executed successfully or unsuccessfully.
14. The device according to claim 9 , wherein the at least one action corresponds to a corresponding trigger threshold of the counter, and determining the target action corresponding to the value of the counter comprises:
determining the target action from the at least one action based on comparison of the value with the corresponding trigger threshold.
15. The device according to claim 9 , wherein the actions further comprise:
resetting the counter.
16. The device according to claim 9 , wherein the operation comprises at least one of the following operations on files or directories in the file system: read operation, create operation, modify operation or delete operation.
17. A computer program product having a non-transitory computer readable medium which stores a set of instructions to manage a file system; the set of instructions, when carried out by computerized circuitry, causing the computerized circuitry to perform a method of:
receiving an event published by a file system, the event being associated with an operation on an object in the file system;
determining a value of a counter corresponding to the event based on execution information of the operation;
determining a target action corresponding to the value of the counter based on a trigger strategy associated with the counter, the trigger strategy defining at least one action that can be triggered by the counter; and
generating an indication for causing the file system to execute the target action;
wherein the event is published by the file system prior to executing the operation on the object in the file system; and
wherein the method further comprises:
after generating the indication, executing the target action in the file system; and
based on an execution result of the target action,
executing the operation on the object in the file system.
18. The method according to claim 1 , further comprising:
receiving, from a client of the file system, an operation request to perform the operation on the object in the file system;
in response to receiving the request, generating the event based on a predetermined control strategy defining a set of events corresponding to a respective set of operation requests; and
after generating the event, publishing the event using a module of the file system.
19. The method according to claim 1 , wherein determining the target action includes:
after determining the value of the counter, comparing the value of the counter to a predetermined threshold that triggers, as the target action, a snapshot creation operation on the object in the file system; and
wherein the method further comprises:
in response to comparing the value of the counter to the predetermined threshold, issuing a request to perform the snapshot creation operation on the object.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.