Method for using file system, electronic device, and storage medium

Abstract

The application discloses a file system use method, an electronic device and a storage medium. The method is applied to an electronic device, the electronic device is installed with an operating system and a file system simulator, the file system simulator runs on the operating system, the electronic device comprises a file system filter driver, the file system filter driver runs on the operating system and is used for calling the file system, and the method comprises the following steps: in response to an operation request input by a user through the file system simulator, calling the file system filter driver, so that the file system filter driver acquires the operation request, and in response to the operation request, calling the file system to execute an operation task corresponding to the operation request; and returning operation information corresponding to the operation task to the file system simulator, so that the user obtains the operation information. The application realizes the use of the F2FS file system on the Windows operating system, and enhances the debugging flexibility and accuracy of the F2FS file system.

Description

Technical Field

[0001] The embodiments disclosed in this application relate to the field of storage technology, and more specifically, to a method of using a file system, an electronic device, and a storage medium. Background Technology

[0002] In modern computing environments, F2FS (Flash-Friendly File System), a file system designed specifically for flash memory devices, has been widely adopted in Linux and Android operating systems due to its high performance and optimized storage management, especially on mobile devices such as phones and tablets. However, with the continuous development of technology, more and more developers and system analysts need to debug and analyze the F2FS file system on the Windows operating system, facing numerous challenges such as inter-system incompatibility in this process. Summary of the Invention

[0003] According to embodiments of this application, this application proposes a method for using a file system, an electronic device, and a storage medium to solve the above-mentioned problems.

[0004] The first aspect of this application discloses a method for using a file system, applied to an electronic device. The electronic device has an operating system and a file system emulator installed, wherein the file system emulator runs on the operating system, and the electronic device includes a file system filter driver that runs on the operating system and is used to invoke the file system. The method includes: responding to an operation request input by a user through the file system emulator, invoking the file system filter driver to obtain the operation request, and responding to the operation request by invoking the file system to execute an operation task corresponding to the operation request; and returning operation information corresponding to the operation task to the file system emulator so that the user obtains the operation information.

[0005] In some embodiments, responding to the operation request by invoking the file system to execute the operation task corresponding to the operation request includes: converting the operation request into a preset interface, so as to invoke the file system to execute the operation task corresponding to the operation request through the preset interface.

[0006] In some embodiments, the file system simulator further includes a test application, and the method further includes: in response to a test request input by a user through the test application, invoking the file system filter driver so that the file system filter driver obtains the operation request, and in response to the operation request, invoking the file system to execute the operation task corresponding to the operation request; returning the operation result corresponding to the operation task to the test application, and returning the operation information corresponding to the operation task to the file system simulator.

[0007] In some embodiments, the operation request includes at least one of a creation request, a read request, and a write request; the step of converting the operation request into a preset interface to call the file system to perform the operation task corresponding to the operation request through the preset interface includes: converting the creation request into the preset interface to call the file system to perform a creation task through the preset interface; or converting the read request into the preset interface to call the file system to perform a read task through the preset interface; or converting the write request into the preset interface to call the file system to perform a write task through the preset interface.

[0008] In some embodiments, the method further includes: in response to the power failure request input by the user through the file system emulator, the file system performs a recovery operation; and returns system information corresponding to the recovery operation to the file system emulator so that the user can obtain the system information.

[0009] In some embodiments, the file system emulator includes a preset power-off procedure. The file system performs a recovery operation in response to the power-off request, including: in response to a power-off request input by the user through the preset power-off procedure, performing a corresponding write operation to trigger the file system to perform the recovery operation on a preset node, wherein the power-off request is used to indicate that the write operation is stopped on the preset node.

[0010] In some embodiments, the file system emulator includes an analysis interface, which includes at least one of a logging interface, a performance monitoring interface, and an error tracing interface.

[0011] In some embodiments, the analysis interface is used to parse the metadata of the file system to obtain the corresponding storage address information; data processing is performed based on the storage address information to generate a data graph related to the file system, thereby enabling monitoring of the operating status of the file system.

[0012] The second aspect of this application discloses an electronic device including a memory and a processor coupled to each other, the processor being configured to execute program instructions stored in the memory to implement the file system usage method described in the first aspect.

[0013] The third aspect of this application discloses a non-volatile computer-readable storage medium storing program instructions thereon, which, when executed by a processor, implement the method of using the file system described in the first aspect.

[0014] The beneficial effects of this application are as follows: in response to the operation request input by the user through the file system simulator, the file system filter driver is called so that the file system filter driver can obtain the operation request; and in response to the operation request, the file system filter driver calls the file system to execute the operation task corresponding to the operation request, and returns the operation information corresponding to the operation task to the file system simulator so that the user can obtain the operation information. This realizes the use of the F2FS file system on the Windows operating system and enhances the debugging flexibility and accuracy of the F2FS file system. Attached Figure Description

[0015] The present application will be further described below with reference to the accompanying drawings and embodiments. In the drawings:

[0016] Figure 1 This is a schematic diagram of the framework of an electronic device according to an embodiment of this application;

[0017] Figure 2 This is a flowchart illustrating the method of using the file system according to an embodiment of this application;

[0018] Figure 3 This is a schematic diagram of the framework of a file system simulator according to an embodiment of this application;

[0019] Figure 4 This is a schematic diagram of the user interface of a method for using a file system according to an embodiment of this application;

[0020] Figure 5 This is a schematic diagram of some interfaces according to an embodiment of this application;

[0021] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application;

[0022] Figure 7 This is a schematic diagram of the structure of a non-volatile computer-readable storage medium according to an embodiment of this application. Detailed Implementation

[0023] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0024] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Additionally, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship. Furthermore, "many" in this application means two or more. Moreover, the term "at least one" in this application means any combination of at least two of any one or more of a plurality of objects. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C. Furthermore, the terms "first," "second," and "third" in this application are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features.

[0025] Debugging and analyzing the F2FS file system on the Windows operating system presents numerous challenges. For example, the F2FS file system was originally designed to run in the Linux kernel environment, which results in a lack of direct support and tools for debugging on the Windows platform. The F2FS file system has specific logic and mechanisms for handling abnormal power outages, data consistency, and performance optimization, which are difficult to reproduce and test directly in the Windows environment. Furthermore, current debugging tools and methods often fail to meet the accuracy and flexibility requirements of system analysts when conducting in-depth analysis of the F2FS file system.

[0026] Therefore, this application proposes a method for using a file system, an electronic device, and a storage medium to solve the above-mentioned problems.

[0027] To enable those skilled in the art to better understand the technical solution of this application, the technical solution of this application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0028] Please see Figure 1 , Figure 1This is a schematic diagram of the framework of an electronic device according to an embodiment of this application. The electronic device 10 includes an operating system 11 and a file system simulator 12. The file system simulator 12 runs on the operating system 11, and the electronic device 10 includes a file system filter driver 13, which also runs on the operating system 11 and is used to call the file system 14. The operating system 11 can be a Windows operating system. The file system simulator 12 runs on the operating system 11, which can be understood as creating a virtual file system environment on the Windows operating system. For example, when the file system simulator 12 runs on the Windows operating system, it is displayed as a virtual drive letter on the system operation interface. The file system simulator 12 runs on the operating system 11, and the file system filter driver 13 can also run on the operating system 11 and call the file system 14, which can be an F2FS file system.

[0029] Please see Figure 2 , Figure 2 This is a flowchart illustrating the method of using the file system according to an embodiment of this application. The subject executing this method can be an electronic device with computing capabilities (e.g., the electronic device 10 mentioned above), such as a microcomputer, a server, and mobile devices such as laptops and tablets.

[0030] It should be noted that if substantially the same result is obtained, the method of this application is not based on... Figure 2 The sequence of processes shown is limited.

[0031] In some possible implementations, this method can be implemented by the processor calling computer-readable instructions stored in memory, such as... Figure 2 As shown, the method may include the following steps:

[0032] S21: In response to the operation request input by the user through the file system emulator, the file system filter driver is invoked so that the file system filter driver can obtain the operation request and, in response to the operation request, invoke the file system to execute the operation task corresponding to the operation request.

[0033] In response to an operation request input by the user through the file system simulator 12, the file system filter driver 13 is invoked so that the file system filter driver 13 can obtain the operation request. For example, after entering the relevant interface by clicking on the file system simulator 12, the user generates an operation request A by editing or clicking, and the file system filter driver 13 intercepts and obtains the operation request A.

[0034] Furthermore, in response to an operation request, the file system filter driver 13 invokes the file system 14 to execute the operation task corresponding to the operation request. For example, if the file system filter driver 13 intercepts and obtains operation request A, it can invoke the file system 14 to execute the operation task corresponding to operation request A.

[0035] S22: Return the operation information corresponding to the operation task to the file system simulator so that the user can obtain the operation information.

[0036] The operation information corresponding to the operation task is returned to the file system simulator 12. This operation information includes metadata generated during the execution of the operation task and file storage information of the files involved in the operation task. Users can obtain this operation information; for example, developers can monitor the running status of the file system 14 in real time to quickly locate and resolve problems.

[0037] In this embodiment, in response to the operation request input by the user through the file system simulator, the file system filter driver is invoked so that the file system filter driver can obtain the operation request. In response to the operation request, the file system filter driver invokes the file system to execute the operation task corresponding to the operation request and returns the operation information corresponding to the operation task to the file system simulator so that the user can obtain the operation information. This realizes the use of the F2FS file system on the Windows operating system and enhances the debugging flexibility and accuracy of the F2FS file system.

[0038] In some embodiments, in response to an operation request, the file system 14 is invoked to perform the operation task corresponding to the operation request, including: converting the operation request into a preset interface, so as to invoke the file system 14 to perform the operation task corresponding to the operation request through the preset interface.

[0039] The default interface can refer to the FUSE interface (Filesystem in Userspace), which provides an interface (Application Programming Interface, API) compatible with file system 14.

[0040] In some examples, the operation request is converted into a preset interface so that the file system 14 can be called through the preset interface to execute the operation task corresponding to the operation request. For example, the operation request B intercepted by the file system filter driver 13 is converted into the format corresponding to the FUSE interface. Then, the file system 14 can be called through the FUSE interface to execute the operation task corresponding to the operation request B. Accordingly, the operation information corresponding to the operation task corresponding to the operation request B is returned to the file system simulator 12 so that the user can obtain the operation information.

[0041] Understandably, the file system emulator 12 runs on the operating system 11, that is, by integrating the file system filter driver 13 and the FUSE interface, a runtime environment for the file system 14 is created on the operating system 11. The file system filter driver 13 is responsible for intercepting and forwarding system operation requests to application layer programs, and the FUSE interface is used to provide APIs compatible with the file system 14, so that the source code of the file system 14 can run on the operating system 11.

[0042] In some embodiments, such as Figure 3 As shown, Figure 3 This is a schematic diagram of the framework of a file system simulator according to an embodiment of this application. The file system simulator 12 includes a test application 121. The test application 121 can be a cross-platform storage performance testing tool (e.g., fio (Flexible I / O Tester) and other testing programs), such as including but not limited to createfile.exe, readfile.exe, or writefile.exe.

[0043] In response to the test request input by the user through the test application 121, the file system filter driver 13 is invoked so that the file system filter driver 13 can obtain the operation request and, in response to the operation request, invoke the file system 14 to execute the operation task corresponding to the operation request; the operation result corresponding to the operation task is returned to the test application 121, and the operation information corresponding to the operation task is returned to the file system simulator 12.

[0044] In some examples, when a user clicks on the test application 121 in the file system simulator 12, the test application 121 starts running and sends a test request C. At this time, the file system filter driver 13 intercepts and obtains the operation request C. In response to the intercepted operation request C, the file system filter driver 13 calls the file system 14 to execute the operation task corresponding to the operation request C. That is, the operation request C is converted into a preset interface so that the file system 14 can be called to execute the operation task corresponding to the operation request C through the preset interface. Furthermore, the operation result corresponding to the operation task executed by the file system 14 is returned to the test application 121, and the operation information corresponding to the operation task is returned to the file system simulator 12.

[0045] In some embodiments, the operation request includes at least one of a create request, a read request, and a write request. For example, it may be multiple create requests, read requests, and write requests generated by user operations such as editing or clicking, or multiple create requests, read requests, and write requests automatically generated by the test application 121.

[0046] The process of converting operation requests into preset interfaces to call the file system 14 to execute the corresponding operation tasks includes: converting creation requests into preset interfaces to call the file system 14 to execute creation tasks; or converting read requests into preset interfaces to call the file system 14 to execute read tasks; or converting write requests into preset interfaces to call the file system 14 to execute write tasks.

[0047] For example, the file system filter driver 13 can convert intercepted creation requests into the format corresponding to the FUSE interface and call the file system 14 to execute the creation task corresponding to the creation request, such as batch creating a large number of files to test the metadata processing capabilities of the file system 14 (e.g., creation speed, directory structure scalability, etc.). Alternatively, the file system filter driver 13 can convert intercepted read requests into the format corresponding to the FUSE interface and call the file system 14 to execute read tasks to test sequential / random read performance, such as throughput, IOPS, latency, etc. Alternatively, the file system filter driver 13 can convert intercepted write requests into the format corresponding to the FUSE interface and call the file system 14 to execute write tasks to test sequential / random write performance, such as checksum verification of write correctness, etc.

[0048] In some examples, the file system filter driver 13 can convert the intercepted read request into the format corresponding to the FUSE interface and call the file system 14 to execute the read task corresponding to the read request. For example, if a user requests to read a file, the file system filter driver 13 intercepts the read operation, converts the read operation into the FUSE interface, and then the user-space program can call the interface of the file system 14 to read the file and return the read file to the application layer. The user-space program then receives the file.

[0049] In some embodiments, in response to a power failure request input by the user through the file system simulator 12, the file system 14 performs a recovery operation; and returns the system information corresponding to the recovery operation to the file system simulator 12 so that the user can obtain the system information.

[0050] The user inputs a power-off request through the file system simulator 12. For example, the user can edit the power-off request through the file system simulator 12. The power-off request can be a preset write command, which controls the writing of the file to stop when it reaches a preset position. In response to the power-off request input through the file system simulator 12, the file system 14 performs a recovery operation and returns the corresponding system information to the file system simulator 12, so that the user can obtain system information. That is, the file system simulator 12 can simulate abnormal power-off scenarios to monitor the performance of the file system's self-recovery mechanism.

[0051] In some embodiments, such as Figure 3 As shown, the file system simulator 12 also includes a preset power-off procedure 122. In response to a power-off request, the file system performs a recovery operation, including: in response to a power-off request input by the user through the preset power-off procedure 122, performing a corresponding write operation to trigger the file system 14 to perform a recovery operation on a preset node, wherein the power-off request is used to indicate that the write operation is stopped on the preset node.

[0052] In some examples, the user clicks on the preset power-off procedure 122 in the file system simulator 12, which sends multiple power-off requests. In response to the power-off requests input by the user through the preset power-off procedure 122, the corresponding write operation is executed to trigger the file system 14 to perform a recovery operation on a preset node. The power-off request indicates that write operations are stopped on the preset node. That is, the preset power-off procedure 122 simulates an abnormal power-off scenario by controlling the cessation of write operations on the preset node, thereby triggering the file system 14 to perform a recovery operation on the preset node, thus realizing a self-recovery mechanism for monitoring the file system.

[0053] Understandably, in this embodiment, by simulating read and write operations, complex scenarios such as data loss and abnormal power outages can be accurately simulated, providing powerful tool support for the stability testing / use of the file system 14.

[0054] In some embodiments, such as Figure 3 As shown, the file system simulator 12 includes an analysis interface 123, which includes at least one of a logging interface, a performance monitoring interface, and an error tracing interface. The logging interface can be used to track and record user operations, service status, and abnormal events; the performance monitoring interface can be used to collect hardware metrics such as CPU, memory, disk, and network; and the error tracing interface can be used to automatically record errors thrown by the code, such as unhandled exceptions and unresponsive events.

[0055] In some embodiments, the analysis interface 123 is used to parse the metadata of the file system 14 to obtain the corresponding storage address information; data processing is performed based on the storage address information to generate a data graph related to the file system 14, thereby enabling monitoring of the running status of the file system 14.

[0056] The metadata of the file system 14 is parsed using analysis interface 123 to obtain corresponding storage address information. For example, the metadata of the file system 14 is parsed to obtain the storage address information of files created / read / written through the file system 14. Furthermore, data processing is performed based on the storage address information to generate a storage information graph related to the file system 14, enabling real-time monitoring of the operating status of the file system 14.

[0057] In some examples, the analysis interface 123 is used to parse the metadata of the file system 14, obtain the storage address information of each file, process the storage address information, calculate the fragmentation index, and use Web visualization to draw a dynamic scatter plot, where each point can represent the number of fragment segments of a file, thereby realizing real-time monitoring of the fragmentation degree of the file system 14 and displaying it in a graphical form. For example, when the file system simulator 12 is running, the dynamic scatter plot can be displayed in real time on the relevant operation interface.

[0058] In this embodiment, the file system simulator 12 includes an analysis interface 123, which enables the file system 14 to be debugged directly on the operating system 11, reducing the time and resource consumption for developers to switch between different operating systems, shortening the development cycle, and improving the overall development efficiency.

[0059] In some examples, the file system emulator 12 runs on the operating system 11 and is displayed as a virtual drive letter on the system interface, such as... Figure 4 As shown, Figure 4 This is a schematic diagram of the user interface for a method of using a file system according to an embodiment of this application. The file system simulator 12 is... Figure 4 The F2FS file simulator (P:) responds to an operation request input by the user through the file system simulator 12, invoking the file system filter driver 13 to obtain the operation request. In response to the operation request, the file system filter driver 13 converts the operation request into a preset interface, which then calls the file system 14 to execute the corresponding operation task. The preset interface can be the FUSE interface, and the operation object can be a disk file, such as... Figure 5 As shown, Figure 5 This is a schematic diagram of some interfaces of an embodiment of this application.

[0060] In some examples, the file system filter driver 13 can run on the operating system 11 and call the file system 14. The source code of the file system 14 can be ported and optimized according to the differences in the interface and compiler of the operating system 11 to adapt to the environment of the operating system 11. This allows the file system 14 to communicate with the application layer through a preset interface, thus achieving compatibility under the operating system 11.

[0061] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0062] Please see Figure 6 , Figure 6This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. The electronic device 60 includes a memory 61 and a processor 62 coupled to each other. The processor 62 is used to execute program instructions stored in the memory 61 to implement the steps of the above-described method for using the file system. In a specific implementation scenario, the electronic device 60 may include, but is not limited to, a microcomputer or a server.

[0063] Specifically, processor 62 controls itself and memory 61 to implement the steps of the above-described method of using the file system. Processor 62 may also be called a CPU (Central Processing Unit), and may be an integrated circuit chip with signal processing capabilities. Processor 62 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or any conventional processor. Furthermore, processor 62 may be implemented using integrated circuit chips.

[0064] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a non-volatile computer-readable storage medium according to an embodiment of this application. The non-volatile computer-readable storage medium 70 is used to store a computer program 701. When the computer program 701 is executed by a processor, for example, by the aforementioned... Figure 6 When the processor 62 in the embodiment is executed, it is used to implement the steps of the above-described embodiment of the method for using the file system.

[0065] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.

[0066] In the several embodiments provided in this application, it should be understood that the disclosed methods and related devices can be implemented in other ways. For example, the related device implementations described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication disconnection shown or discussed may be indirect coupling or communication disconnection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0067] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0068] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0069] Those skilled in the art will readily recognize that numerous modifications and variations can be made to the apparatus and method while maintaining the teachings of this application. Therefore, the above disclosure should be considered limited only by the scope of the appended claims.

Claims

1. A method for using a file system, characterized in that, Applied to an electronic device, the electronic device having an operating system and a file system emulator installed, wherein the file system emulator runs on the operating system, and the electronic device includes a file system filter driver that runs on the operating system and is used to invoke the file system, the method comprising: In response to an operation request input by the user through the file system emulator, the file system filter driver is invoked so that the file system filter driver obtains the operation request and, in response to the operation request, invokes the file system to execute the operation task corresponding to the operation request; The operation information corresponding to the operation task is returned to the file system simulator so that the user can obtain the operation information.

2. The method according to claim 1, characterized in that, The step of responding to the operation request by invoking the file system to execute the operation task corresponding to the operation request includes: The operation request is converted into a preset interface, and the file system is invoked through the preset interface to execute the operation task corresponding to the operation request.

3. The method according to claim 1, characterized in that, The file system emulator also includes a test application, and the method further includes: In response to a test request input by the user through the test application, the file system filter driver is invoked so that the file system filter driver obtains the operation request and, in response to the operation request, invokes the file system to execute the operation task corresponding to the operation request; The operation result corresponding to the operation task is returned to the test application, and the operation information corresponding to the operation task is returned to the file system simulator.

4. The method according to claim 2 or 3, characterized in that, The operation request includes at least one of a create request, a read request, and a write request; The step of converting the operation request into a preset interface, and then calling the file system through the preset interface to execute the operation task corresponding to the operation request, includes: The creation request is converted into the preset interface, and the file system is invoked through the preset interface to execute the creation task; or The read request is converted into the preset interface, and the file system is invoked to perform the read task through the preset interface; or The write request is converted into the preset interface, so that the file system can be invoked to perform the write task through the preset interface.

5. The method according to claim 1, characterized in that, The method further includes: In response to a power outage request input by the user through the file system emulator, the file system performs a recovery operation; The system information corresponding to the recovery operation is returned to the file system simulator so that the user can obtain the system information.

6. The method according to claim 5, characterized in that, The file system emulator includes a preset power-off procedure. In response to the power-off request, the file system performs a recovery operation, including: In response to a power outage request input by the user through the preset power outage procedure, a corresponding write operation is executed to trigger the file system to perform the recovery operation on a preset node, wherein the power outage request is used to indicate that the write operation is stopped on the preset node.

7. The method according to claim 1, characterized in that, The file system simulator includes an analysis interface, which includes at least one of a logging interface, a performance monitoring interface, and an error tracing interface.

8. The method according to claim 7, characterized in that, The method further includes: The analysis interface is used to parse the metadata of the file system to obtain the corresponding storage address information; Data processing is performed based on the storage address information to generate a data graph related to the file system, thereby enabling monitoring of the file system's operating status.

9. An electronic device, characterized in that, It includes a memory and a processor coupled to each other, the processor being used to execute program instructions stored in the memory to implement the method of using the file system according to any one of claims 1 to 8.

10. A non-volatile computer-readable storage medium storing program instructions thereon, characterized in that, When the program instructions are executed by the processor, they implement the method of using the file system as described in any one of claims 1 to 8.

Images