File system unmounting method, electronic device, and computer readable storage medium

Abstract

Embodiments of the present invention provide a file system unmounting method, an electronic device, and a computer readable storage medium. The file system unmounting method comprises: in a multi-container operating system, when a shutdown button or restart button of any container is triggered, said any container sends a trigger signal to a main container, wherein the multi-container comprises at least one sub-container and the main container (S11); and on the basis of the trigger signal, the main container performs a container file system unmounting operation on the sub-container and the main container in a united manner (S12). According to the embodiments of the present invention, the trigger signal is sent to the main container, and the main container performs process stop and container file system unmounting operations on the sub-container and the main container itself in a united manner on the basis of the trigger signal, so that the file system unmounting of the multi-container operating system can be efficiently and smoothly implemented, normally shutting down or restarting is implemented, avoiding the problems such as incomplete file system unmounting among the containers or a system crash caused by a hardware device conflict.

Description

File system uninstallation method, electronic device, and computer-readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202311551904.9 filed with the China Patent Office on November 20, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to, but is not limited to, the field of operating systems. Background Art

[0004] With the widespread adoption of multi-operating systems in the security endpoint market, their key technologies are becoming an increasing focus of industry attention. In many scenarios, to conserve system hardware storage resources and facilitate users' rapid switching between multiple operating systems at any time, these multi-operating systems, unlike traditional multi-ROM (read-only memory) operating systems, are designed as multi-container systems running simultaneously on the same physical storage device. In particular, for data security reasons, the data area of ​​each container must be strictly isolated. Therefore, file system design for these multi-container operating systems has become a core and key technology in multi-operating system research, encompassing the mounting, isolation, and unmounting of multi-container file systems.

[0005] Summary of the Invention

[0006] Embodiments of the present disclosure provide a file system uninstallation method, an electronic device, and a computer-readable storage medium.

[0007] In a first aspect, embodiments of the present disclosure provide a file system unmounting method. The method may include: when a shutdown button or a restart button of any container in a multi-container operating system is triggered, the any container sends a trigger signal to a main container; the multi-container includes at least one child container and the main container; and the main container uniformly performs a container file system unmounting operation on the child containers and the main container based on the trigger signal.

[0008] In a second aspect, an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a memory on which one or more programs are stored, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the file system unloading method; and one or more input / output (I / O) interfaces connected between the one or more processors and the memory, and configured to implement information interaction between the one or more processors and the memory.

[0009] In a third aspect, an embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the file system unloading method is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG1 is a schematic diagram of a file system framework in the related art;

[0011] FIG2 is a flowchart of a method for uninstalling a file system according to an embodiment of the present disclosure;

[0012] FIG3 is a flowchart of a method for a main container to uniformly unmount a container file system on a sub-container and a main container according to a trigger signal, provided by an embodiment of the present disclosure;

[0013] FIG4 is a schematic diagram of a method for monitoring the status of a super block of multiple containers and unloading the super block of multiple containers according to the status of the super block, provided by an embodiment of the present disclosure;

[0014] FIG5 is a block diagram of an electronic device according to an embodiment of the present disclosure;

[0015] FIG6 is a block diagram of the composition of a computer-readable storage medium provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0016] To enable those skilled in the art to better understand the technical solutions of the present disclosure, the file system unloading method, electronic device, and computer-readable storage medium provided by the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0017] The present disclosure will be described more fully hereinafter with reference to the accompanying drawings, but the illustrated embodiments may be embodied in different forms, and the present disclosure should not be construed as limited to the embodiments set forth below. Rather, these embodiments are provided so that the present disclosure will be thorough and complete and will fully understand the scope of the present disclosure to those skilled in the art.

[0018] The accompanying drawings of the embodiments of the present disclosure are used to provide a further understanding of the embodiments of the present disclosure and constitute a part of the specification. Together with the detailed embodiments, they are used to explain the present disclosure and do not constitute a limitation of the present disclosure. The above and other features and advantages will become more apparent to those skilled in the art by describing the detailed embodiments with reference to the accompanying drawings.

[0019] The present disclosure may be described with reference to plan views and / or cross-sectional views by way of ideal schematic views of the present disclosure. Therefore, the exemplary illustrations may be modified according to manufacturing techniques and / or tolerances.

[0020] In the absence of conflict, the various embodiments of the present disclosure and the various features therein may be combined with each other.

[0021] The terms used in this disclosure are only used to describe specific embodiments and are not intended to limit the disclosure. As used in this disclosure, the term "and / or" includes any and all combinations of one or more related enumerated items. As used in this disclosure, the singular forms "a" and "the" are also intended to include plural forms, unless the context clearly indicates otherwise. As used in this disclosure, the terms "comprising" and "made of" specify the presence of the features, wholes, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof.

[0022] Unless otherwise defined, all terms (including technical and scientific terms) used in this disclosure have the same meanings as those commonly understood by those skilled in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning unless expressly defined in this disclosure.

[0023] The present disclosure is not limited to the embodiments shown in the drawings, but includes modifications of the configurations formed based on the manufacturing process. Therefore, the regions illustrated in the drawings have schematic properties, and the shapes of the regions shown in the drawings illustrate the specific shapes of the regions of the elements, but are not intended to be limiting.

[0024] Currently, there are two main methods for shutting down or restarting multi-container operating systems running on the same physical storage device with isolated file systems:

[0025] The first solution is to shut down or restart each container in turn. For example, in an Android system, each container follows the standard Android shutdown and restart process, first stopping all processes within its own container and then unmounting its own file system. In actual use, this solution is prone to causing various abnormal conflicts, including hardware device operations, crashes, and the inability to release file resources normally, resulting in problems such as failure to unmount the system's main data area ( / data). Resolving these conflicts and problems requires a lot of effort.

[0026] The second method is simpler and doesn't require stopping processes or unmounting the file system. Instead, it directly sends a shutdown or restart command to the underlying system hardware. The biggest problem with this method is that it's essentially a hard shutdown, known as a sudden power-off on Android. This can easily damage the file system and cause user data loss. Furthermore, upon restarting the device, a hard shutdown indicator will be detected, requiring a file system self-check, which can cause slow startups or unexplained freezes.

[0027] To address the shortcomings of the above conventional methods, the embodiments of the present disclosure propose a shutdown or restart process for a multi-container operating system, the core of which is a method for unmounting the file system of the multi-container.

[0028] In the disclosed embodiment, a trigger signal is sent to the main container, which then stops the processes of the child containers and the main container itself and unmounts the container file systems in a unified manner according to the trigger signal. This allows for efficient and smooth file system unmounting of multi-container operating systems, and allows for normal shutdown or restart, thus avoiding problems such as system crashes caused by unclean file system unmounting between containers or hardware device conflicts.

[0029] The multi-container system uninstallation method of the disclosed embodiments can be executed by any electronic device requiring multi-container system uninstallation, such as a terminal device or server. Terminal devices may include, but are not limited to, in-vehicle devices, user equipment (UE), mobile devices, computing devices, wearable devices, and the like, including, but not limited to, cellular phones, cordless phones, personal digital assistants (PDAs), and portable computers. The multi-container system uninstallation method can be implemented by a processor invoking computer-readable program instructions stored in a memory, or by a server.

[0030] The embodiments of the present disclosure can be applied to a terminal running multiple operating systems (for example, dual operating systems) simultaneously, such as a mobile phone with dual Android systems, where the user chooses to shut down or restart the current system.

[0031] As shown in Figure 1, multiple operating systems in a multi-container system according to an embodiment of the present disclosure have unified hardware devices (storage, network, etc.) and an operating system kernel (e.g., the Linux kernel). The multi-container system may include a main container and multiple sub-containers (e.g., sub-container 1, sub-container 2, ..., sub-container n, etc., where n is a positive integer). Each container may include a container file system and processes that are isolated from each other.

[0032] The following is a detailed introduction to the embodiments of the present disclosure.

[0033] An embodiment of the present disclosure provides a file system unloading method, as shown in FIG2 , and the method may include steps S11 - S12 .

[0034] S11. When a shutdown button or a restart button of any container in a multi-container operating system is triggered, the arbitrary container sends a trigger signal to a main container; the multi-container includes at least one sub-container and a main container.

[0035] In the embodiment of the present disclosure, the embodiment of the present disclosure can be illustrated by taking a smartphone with dual Android systems as an example. For example, the multi-container can include a main container and two sub-containers (such as a work container and a life container).

[0036] In an embodiment of the present disclosure, when a user clicks a shutdown or restart button on a container (such as a living container or a working container), the container (living container or working container) first transmits a shutdown or restart signal to the main container.

[0037] S12: The main container performs a container file system unmounting operation on the sub-container and the main container in a unified manner according to the trigger signal.

[0038] In the embodiment of the present disclosure, after receiving a shutdown or restart signal, the main container will uniformly unmount the file system of each container in the multi-container.

[0039] In an embodiment of the present disclosure, as shown in FIG3 , the main container uniformly performs a container file system unmounting operation on the sub-container and the main container according to a trigger signal, including steps S21 - S22 .

[0040] S21. Stop the processes in multiple containers at the same time.

[0041] In the disclosed embodiment, because the processes of each container are isolated from each other, each container can only see the processes belonging to its own system. Only the main container can see the processes in all containers (including the main container and sub-containers). All processes of all containers can be stopped uniformly through the main container.

[0042] S22. Monitor the status of the super blocks of the multiple containers and unload the super blocks of the multiple containers according to the status of the super blocks. The super blocks are used to isolate the container file systems of different containers.

[0043] To ensure system security, the file systems of different containers must be isolated. Therefore, during system startup, the file system corresponding to each container must be mounted. These file systems correspond to the corresponding container's data area, system area, and other superblocks. For example, the data area superblock of the home system container corresponds to: mount / data / cells / home / data; the data area superblock of the work system container corresponds to: mount / data / cells / work / data. Therefore, unmounting the container's corresponding superblock unmounts the container's file system.

[0044] In an embodiment of the present disclosure, as shown in FIG4 , monitoring the status of a super block of multiple containers and unloading the super block of multiple containers according to the status of the super block include:

[0045] Detect the number of active states of the superblock of each child container and the main container; the number of active states of the superblock is the count of processes that share each superblock;

[0046] If the active state count of any super block is not 0, check the reference count of each mounted object of the super block;

[0047] If the reference count of any mounted object is not 0, force the reference count of the mounted object to be 0;

[0048] When the reference count of all mounted objects of each super block is 0, the super block is unmounted.

[0049] In an embodiment of the present disclosure, monitoring the status of the super block of multiple containers and unloading the super block of multiple containers according to the status of the super block may further include:

[0050] When the number of active states of any super block is 0, the process of detecting the number of active states of the next super block is entered; when the number of references of any mounted object is 0, the process of detecting the number of references of the next mounted object is entered.

[0051] In the embodiment of the present disclosure, the super block may include a first super block corresponding to the sub-container and a second super block corresponding to the main container.

[0052] In an embodiment of the present disclosure, monitoring the status of a super block of multiple containers and unloading the super block of multiple containers according to the status of the super block may include:

[0053] monitoring the status of the first super block corresponding to each sub-container, and unloading each first super block according to the status of the first super block; and

[0054] Monitor the status of the second super block corresponding to the main container, and unload the second super block according to the status of the second super block.

[0055] In an embodiment of the present disclosure, monitoring the status of the super block of multiple containers and unloading the super block of multiple containers according to the status of the super block may further include:

[0056] After each first super block is unloaded according to the status of the first super block, the status of the second super block corresponding to the main container is monitored, and the second super block is unloaded according to the status of the second super block.

[0057] In the disclosed embodiment, since the first Super Block of the child container and the second Super Block of the main container have a parent-child relationship, the second Super Block of the main container can only be successfully unmounted after the first Super Block is unmounted. Therefore, the first Super Blocks of multiple child containers can be unmounted first. For example, the main container can first unmount these Super Blocks:

[0058] unmount / data / cells / home / data (the first superblock corresponding to the living container);

[0059] Unmount / data / cells / work / data (the first superblock corresponding to the work container).

[0060] In an embodiment of the present disclosure, monitoring the status of the first super block corresponding to each sub-container and unloading each first super block according to the status of the first super block may include:

[0061] For each first super block, the activity state number of the first super block is detected respectively; the activity state number of the first super block is a count of processes that share and occupy each first super block;

[0062] When the active state count of any first super block is not 0, check the reference count of each first mount object of the first super block;

[0063] If the reference count of any first mounted object is not 0, the reference count of the first mounted object is forcibly set to 0;

[0064] When the number of references to all first mount objects of each first super block is 0, the first super block is unmounted.

[0065] In an embodiment of the present disclosure, monitoring the status of the first super block corresponding to each sub-container and unloading each first super block according to the status of the first super block may further include:

[0066] When the activity state number of any first super block is 0, the process of detecting the activity state number of the next first super block is entered;

[0067] When the reference count of any first mounted object is 0, the process of detecting the reference count of the next first mounted object is entered.

[0068] In an embodiment of the present disclosure, when the first super block of the child container is unmounted, the number of active states of the first super block and the number of references to the first mounted object may be monitored.

[0069] In the embodiment of the present disclosure, the activity status number of each first super block mounted on each sub-container can be checked. The activity status number of the first super block is a count of the number of processes sharing and occupying this first super block. If the activity status number of the first super block is 0, the current check is exited and the next first super block is checked. If the activity status number of the first super block is not 0, the reference number of each first mounted object of the first super block is checked.

[0070] In the disclosed embodiment, each process in the first superblock will occupy the first superblock when it starts, and the system will clone a first mount object for the process to use the first superblock. The reference count of the first mount object (including but not limited to file objects, file path objects, etc.) is the number of times file operations, folder path accesses, etc. are performed on the first mount object. Each file operation and folder path access will increase the reference count.

[0071] In the embodiment of the present disclosure, if it is checked that the reference count of any first mount object is 0, the current check is exited and the next first mount object is checked. If it is checked that the reference count of any first mount object is not 0, the reference count of the first mount object is forcibly set to 0, and when the reference count of all first mount objects of each first super block of all sub-containers is 0, the first super blocks of all sub-containers are unmounted.

[0072] In the disclosed embodiment, after the main container unloads the first superblock of the child container, it can unload its own main file system, including the superblocks corresponding to the data area and system device area (i.e., the second superblock). The main container unloads its own file system by unloading its own second superblock.

[0073] In an embodiment of the present disclosure, monitoring the status of the second super block corresponding to the main container and unloading the second super block according to the status of the second super block includes:

[0074] Detecting the number of activity states of the second super block; the number of activity states of the second super block is a count of processes that share and occupy each second super block;

[0075] When the active state number of the second super block is not 0, checking the reference number of each second mount object of the second super block;

[0076] If the reference count of any second mounted object is not 0, the reference count of the second mounted object is forcibly set to 0;

[0077] When the reference count of all the second mount objects of the second super block is 0, the second super block is unmounted.

[0078] In the embodiment of the present disclosure, monitoring the status of the second super block corresponding to the main container and unloading the second super block according to the status of the second super block may further include:

[0079] When the activity state number of any second super block is 0, the process of detecting the activity state number of the next second super block is entered;

[0080] When the reference count of any second mounted object is 0, the process of detecting the reference count of the next second mounted object is entered.

[0081] In an embodiment of the present disclosure, before unmounting the main container file system, the activity status counts of all second super blocks mounted on the main container can be checked. The activity status count of the second super block is a count of the number of processes sharing and occupying this second super block. If the activity status count of the second super block is 0, the current check is exited and the next second super block is checked. If the activity status count of the second super block is not 0, the reference count of each second mounted object of the second super block is checked.

[0082] In the disclosed embodiment, each process in the second superblock will occupy the second superblock when it starts, and the system will clone a second mount object for the process to use the second superblock. The reference count of a second mount object (including but not limited to a file object, a file path object, etc.) is the number of times file operations, folder path accesses, etc. are performed on the second mount object. Each file operation or folder path access will increase the reference count.

[0083] In the embodiment of the present disclosure, if it is checked that the reference count of any second mount object is 0, the current check is exited and the next second mount object is checked. If it is checked that the reference count of any second mount object is not 0, the reference count of the second mount object is forcibly set to 0, and when the reference count of all second mount objects of each second super block of all sub-containers is 0, all second super blocks of the main container are unmounted.

[0084] In the embodiment of the present disclosure, the main container unmounts its own main file system, including the second super block corresponding to the data area and the system device area, such as:

[0085] unmount / data;

[0086] unmount / dev / *.

[0087] In an embodiment of the present disclosure, unloading a super block of multiple containers according to a state of the super block includes:

[0088] Detection system alarm;

[0089] Record the file resources corresponding to each detected system alarm as an abnormal file node.

[0090] In the disclosed embodiment, by recording each abnormal file node, it is convenient to eliminate each system alarm after the super block (first super block and second super block) is unloaded, thereby preventing file data loss and abnormal conflicts, and avoiding unclean unloading of file systems between containers.

[0091] In an embodiment of the present disclosure, after recording the file resource corresponding to each detected system alarm as an abnormal file node, the method may further include:

[0092] Check for unreleased file system resources based on abnormal file nodes;

[0093] Correction of unreleased file system resources.

[0094] In the embodiment of the present disclosure, the file system resources include processes and / or files.

[0095] In the embodiment of the present disclosure, since some file system resources were deployed earlier, these file system resources have not been divided into containers, so that when the super block is unloaded, these file system resources are still being referenced and not released, and a system alarm is generated. Therefore, after obtaining the system alarm information, the unreleased file system resources can be corrected according to the recorded abnormal file nodes (that is, the corresponding file system resources are checked according to each abnormal file node, and the file system resources are attributed to the corresponding sub-container or main container). Then, the alarm can be eliminated during the unloading of the super block when shutting down or restarting the computer next time, thereby ensuring that all super blocks are unloaded smoothly during the shutdown or restart process, and finally ensuring that the / data partition of the main container is unloaded successfully, avoiding the sudden-power-off problem when starting the computer.

[0096] In summary, the embodiments of the present disclosure enable efficient and smooth file system unloading of multi-container operating systems, as well as normal shutdown or restart, to avoid problems such as incomplete unloading of file systems between containers or system crashes caused by hardware device conflicts.

[0097] An embodiment of the present disclosure also provides an electronic device 100, as shown in Figure 5, the electronic device 100 includes: one or more processors 101; a memory 102, on which one or more programs are stored, when the one or more programs are executed by the one or more processors 101, the one or more processors 101 implement the file system unloading method; one or more input / output I / O interfaces 103, connected between the one or more processors 101 and the memory 102, and configured to implement information interaction between the one or more processors 101 and the memory 102.

[0098] Among them, the processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read-write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus), etc.

[0099] In some embodiments, the processor 101 , the memory 102 , and the I / O interface 103 are connected to each other via a bus 104 , and further connected to other components of the computing device.

[0100] The embodiment of the present disclosure further provides a computer-readable storage medium 200, as shown in FIG6 . The computer-readable storage medium 200 stores a computer program, and when the computer program is executed by a processor, the file system unloading method is implemented.

[0101] In the disclosed embodiment, a trigger signal is sent to the main container, and the main container uniformly performs container file system unmounting operations on the sub-containers and the main container according to the trigger signal. This can efficiently and smoothly implement file system unmounting of multi-container operating systems and enable normal shutdown or restart, avoiding problems such as system crashes caused by unclean file system unmounting between containers or hardware device conflicts.

[0102] Those skilled in the art will appreciate that all or some of the functional modules / units disclosed above may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0103] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation.

[0104] Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit (CPU), a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As is well known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH) or other disk storage; compact disc (CD-ROM), digital versatile disc (DVD) or other optical disc storage; magnetic cassettes, tapes, disk storage or other magnetic storage; any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0105] The present disclosure has disclosed example embodiments, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for purposes of limitation. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly indicated, features, characteristics, and / or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in conjunction with other embodiments. Therefore, it will be understood by those skilled in the art that various changes in form and detail may be made without departing from the scope of the present disclosure as set forth in the appended claims.

Claims

1. A method for unloading a file system, comprising: When a shutdown button or a restart button of any container in a multi-container operating system is triggered, the any container sends a trigger signal to a main container; the multi-container includes at least one sub-container and the main container; The main container uniformly performs a container file system unmounting operation on the sub-container and the main container according to the trigger signal.

2. The file system unloading method according to claim 1, wherein: The main container uniformly performs a container file system unloading operation on the sub-container and the main container according to the trigger signal, including: Stopping the processes in the multiple containers uniformly; The state of the super blocks of the multiple containers is monitored, and the super blocks of the multiple containers are unloaded according to the state of the super blocks; the super blocks are used for isolating the container file systems of different containers.

3. The file system unloading method according to claim 2, wherein: The monitoring the state of the super block of the multi-container and unloading the super block of the multi-container according to the state of the super block includes: Detecting the number of activity states of the super blocks of each of the sub-containers and the main container; the number of activity states of the super blocks is a count of processes that share and occupy each of the super blocks; In the case where the number of active states of any of the super blocks is not 0, checking the number of references of each mounted object of the super block; If the reference count of any of the mounted objects is not 0, forcibly set the reference count of the mounted object to 0; When the reference count of all the mounted objects of each super block is 0, the super block is unmounted.

4. The file system unloading method according to claim 3, wherein: The monitoring the state of the super block of the multi-container and unloading the super block of the multi-container according to the state of the super block further includes: When the number of active states of any of the super blocks is 0, the process of detecting the number of active states of the next super block is entered; when the number of references of any of the mounted objects is 0, the process of detecting the number of references of the next mounted object is entered.

5. The file system unloading method according to claim 2, wherein: The super block includes a first super block corresponding to the sub-container and a second super block corresponding to the main container.

6. The file system unloading method according to claim 5, wherein: The monitoring the state of the super block of the multi-container and unloading the super block of the multi-container according to the state of the super block includes: After each of the first super blocks is unloaded according to the status of the first super blocks, the status of the second super blocks corresponding to the main container is monitored, and the second super blocks are unloaded according to the status of the second super blocks.

7. The file system unloading method according to claim 2, wherein: The step of unloading the super block of the multi-container according to the state of the super block comprises: Detection system alarm; The file resources corresponding to each detected system alarm are recorded as an abnormal file node.

8. The file system unloading method according to claim 7, wherein: After recording the file resource corresponding to each detected system alarm as an abnormal file node respectively, the method further includes: Checking unreleased file system resources according to the abnormal file node; The unreleased file system resources are modified.

9. An electronic device, comprising: one or more processors; A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the file system unloading method according to any one of claims 1 to 8; One or more input / output I / O interfaces are connected between the one or more processors and the memory, and are configured to implement information interaction between the one or more processors and the memory.

10. A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the file system unloading method according to any one of claims 1 to 8.

Images