File system unloading method, electronic equipment and computer readable storage medium
By sending trigger signals uniformly in a multi-container operating system to uninstall the subcontainer and its own file system of the main container, the problem of unclear file system uninstallation or hardware device conflicts during shutdown or restart of the multi-container operating system is solved, and the file system is effectively uninstalled and smoothly uninstalled.
Patent Information
- Application Number
- CN202311551904.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-11-20
- Publication Date
- 2025-05-20
AI Technical Summary
Existing multi-container operating systems are prone to problems such as unclear file system uninstallation or hardware device conflicts during shutdown or restart.
In a multi-container operating system, when the shutdown or restart button of any container is triggered, a trigger signal is sent to the main container, and the main container uniformly performs container file system uninstallation operations on the subcontainer and itself.
It realizes efficient and smooth uninstallation of file systems of multi-container operating systems, avoiding the crash problems caused by unclear uninstallation of file systems between containers or hardware device conflicts.
Smart Images
Figure CN120020717A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of operating systems, and particularly to a file system unmounting method, an electronic device, and a computer-readable storage medium. Background Art
[0002] With the wide application of multi-operating systems in the security terminal market, their key technologies have increasingly become the focus of industry attention. In many scenarios, in order to save system hardware storage resources and facilitate users to quickly switch between several systems at any time, different from traditional multi-ROM (read only memory) operating systems, such multi-operating systems are designed as multi-container systems that run simultaneously on the same physical storage device. Especially for data security considerations, the data areas of each container must be strictly isolated. Therefore, the file system design of such multi-container operating systems has become one of the core key technologies in the research of multi-operating systems, which includes mounting, isolation, unmounting, etc. of multi-container file systems. Summary of the Invention
[0003] Embodiments of the present disclosure provide a file system unmounting method, an electronic device, and a computer-readable storage medium.
[0004] In a first aspect, embodiments of the present disclosure provide a file system unmounting method, which may include:
[0005] When the shutdown button or restart button of any container in a multi-container operating system is triggered, the any container sends a trigger signal to the main container; the multi-container includes at least one sub-container and the main container;
[0006] The main container uniformly performs a container file system unmounting operation on the sub-container and the main container according to the trigger signal.
[0007] In a second aspect, embodiments of the present disclosure provide an electronic device, which includes:
[0008] One or more processors;
[0009] A memory having one or more programs stored thereon, and when the one or more programs are executed by the one or more processors, the one or more processors implement the file system unmounting method;
[0010] One or more input / output I / O interfaces connected between the processor and the memory and configured to implement information interaction between the processor and the memory.
[0011] In a third aspect, embodiments of the present disclosure provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the file system unloading method described above is implemented.
[0012] By sending a trigger signal to the main container, and having the main container perform container file system unloading operations on sub-containers and the main container according to the trigger signal, embodiments of the present disclosure can efficiently and smoothly implement file system unloading of a multi-container operating system, and shut down or restart normally, avoiding problems such as incomplete file system unloading between containers or crashes caused by hardware device conflicts. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] In the drawings of the embodiments of the present disclosure:
[0014] Figure 1 is a schematic diagram of a file system framework in the related art;
[0015] Figure 2 is a schematic diagram of the process flow of the file system unloading method provided by embodiments of the present disclosure;
[0016] Figure 3 is a schematic diagram of the process flow of the method for the main container to uniformly perform container file system unloading operations on sub-containers and the main container according to a trigger signal provided by embodiments of the present disclosure;
[0017] Figure 4 is a schematic diagram of the method for monitoring the status of the superblocks of multiple containers and unloading the superblocks of multiple containers according to the status of the superblocks provided by embodiments of the present disclosure;
[0018] Figure 5 is a block diagram of the composition of an electronic device provided by embodiments of the present disclosure;
[0019] Figure 6 is a block diagram of the composition of a computer-readable storage medium provided by embodiments of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0020] To enable those skilled in the art to better understand the technical solutions of the present disclosure, the communication perception data processing method and computer-readable storage medium provided by embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0021] The present disclosure will be described more fully hereinafter with reference to the accompanying drawings. However, the disclosed embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth below. On the contrary, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
[0022] 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 to the present disclosure. By describing the detailed embodiments with reference to the accompanying drawings, the above and other features and advantages will become more obvious to those skilled in the art.
[0023] The present disclosure can be described with reference to the plan view and / or sectional view by means of the ideal schematic diagram of the present disclosure. Therefore, the example illustrations can be modified according to the manufacturing technology and / or tolerances.
[0024] In the case of no conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other.
[0025] The terms used in the present disclosure are only used to describe specific embodiments and are not intended to limit the present disclosure. As used in the present disclosure, the term "and / or" includes any and all combinations of one or more related listed items. As used in the present disclosure, the singular forms "a" and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. As used in the present disclosure, the terms "comprising", "made of", specify the presence of the described 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 their groups.
[0026] Unless otherwise defined, the meanings of all terms (including technical and scientific terms) used in the present disclosure are the same as those commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in common dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless the present disclosure clearly defines so.
[0027] The present disclosure is not limited to the embodiments shown in the accompanying drawings, but includes modifications to the configurations formed based on the manufacturing process. Therefore, the regions illustrated in the accompanying 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 restrictive.
[0028] Currently, for a multi-container operating system that runs simultaneously on the same physical storage device and whose file systems are isolated from each other, there are mainly the following two solutions for its shutdown or restart process:
[0029] The first solution is to shut down or restart each container in turn. For example, in an Android system, each container follows the Android standard shutdown and restart process, first stopping all processes in its own container, and then uninstalling the container's own file system. In actual use, this solution is prone to cause various abnormal conflicts, including hardware device operations, crashes, and file resources cannot be released normally, resulting in problems such as failure to uninstall the system's main data area ( / data). It takes a lot of effort to solve these conflicts and problems.
[0030] The second method is relatively simple. It does not require stopping the process and unloading the file system. It directly sends a shutdown or restart command to the underlying system hardware. The biggest problem with this method is that this operation is essentially a hard shutdown operation, such as what is called sudden power-off in the Android system. It is very easy to damage the file system and lose user data. In addition, after restarting, the hard shutdown mark will be detected, and the file system self-check is required, which will cause problems such as slow startup or inexplicable freeze.
[0031] Aiming at the defects in the above conventional methods, the embodiment of the present disclosure proposes a shutdown or restart process of a multi-container operating system, the core of which is a method for uninstalling a multi-container file system.
[0032] The disclosed embodiment sends a trigger signal to the main container, and the main container stops the process and unloads the container file system on the sub-container and the main container itself according to the trigger signal, so that the file system of the multi-container operating system can be unloaded efficiently and smoothly, and the system can be shut down or restarted normally, avoiding problems such as unclean unloading of the file system between containers or crashes caused by hardware device conflicts.
[0033] The multi-container system uninstallation method of the embodiment of the present disclosure can be executed by any electronic device such as a terminal device or a server that needs to execute the multi-container system uninstallation. The terminal device may include but is not limited to: vehicle-mounted equipment, user equipment (User Equipment, UE), mobile equipment, computing equipment, wearable devices, etc., for example, including but not limited to cellular phones, cordless phones, personal digital assistants (Personal Digital Assistant, PDA), portable computers, etc. The multi-container system uninstallation method can be implemented by a processor calling a computer-readable program instruction stored in a memory, or it can be implemented by a server.
[0034] The embodiments of the present disclosure can be applied to multiple operating systems (e.g., dual operating systems) running simultaneously on a terminal, such as dual Android systems on a mobile phone, where the user chooses to shut down or restart the current system.
[0035] If Figure 1As shown in the figure, in the solution of the embodiment of the present disclosure, multiple operating systems in a multi-container system have unified hardware devices (such as storage, network, etc.) and operating system kernels (such as the Linux kernel). The multi-container may include a main container and multiple sub-containers (such as 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.
[0036] The following is a detailed introduction to the solution of the embodiment of the present disclosure.
[0037] The embodiment of the present disclosure provides a method for unmounting a file system, as Figure 2 shown, the method may include steps S11 - S12:
[0038] S11. When the shutdown button or restart button of any container in the operating system of the multi-container is triggered, the trigger signal is sent by the any container to the main container; the multi-container includes at least one sub-container and a main container.
[0039] In the embodiment of the present disclosure, the solution of the embodiment of the present disclosure can be illustrated by taking the dual Android system of a smart phone as an example. For example, the multi-container may include a main container and two sub-containers (such as a work container and a life container).
[0040] In the embodiment of the present disclosure, when the user clicks the shutdown or restart button on a certain container (such as the life container or the work container), the container (the life container or the work container) first sends the shutdown or restart signal to the main container.
[0041] S12. The main container uniformly performs an operation of unmounting the container file systems for the sub-containers and the main container according to the trigger signal.
[0042] In the embodiment of the present disclosure, after receiving the shutdown or restart signal, the main container will uniformly unmount the file system of each container in the multi-container.
[0043] In the embodiment of the present disclosure, as Figure 3 shown, the main container uniformly performs an operation of unmounting the container file systems for the sub-containers and the main container according to the trigger signal, including steps S21 - S22:
[0044] S21. Uniformly stop the processes in the multi-container.
[0045] In the embodiment of the present disclosure, since the processes of each container are isolated from each other, each container can only see the processes belonging to its own system internally. Only the main container can see the processes in all containers (including the main container and the sub-containers). Through the main container, all processes of all containers can be uniformly stopped.
[0046] S22. Monitor the status of the superblocks of multiple containers, and unmount the superblocks of multiple containers according to the status of the superblocks; the superblocks are used for isolation between the container file systems of different containers.
[0047] To ensure system security, it is necessary to isolate the file systems of different containers. Therefore, during the system startup phase, it is necessary to mount the file systems corresponding to each container. These file systems correspond to superblocks such as the data area and system area of the corresponding containers. For example, the superblock of the data area of the life system container corresponds to: mount / data / cells / home / data; the superblock of the data area of the work system container corresponds to: mount / data / cells / work / data. Therefore, unmounting the superblock corresponding to the container can achieve unmounting the container file system.
[0048] In the embodiments of the present disclosure, as Figure 4 shown, monitoring the status of the superblocks of multiple containers and unmounting the superblocks of multiple containers according to the status of the superblocks includes:
[0049] Detect the active status count of the superblocks of each sub-container and the main container; the active status count of the superblock is the count of processes sharing and occupying each superblock;
[0050] When the active status count of any superblock is not 0, check the reference count of each mount object of the superblock;
[0051] When the reference count of any mount object is not 0, forcibly set the reference count of the mount object to 0;
[0052] When the reference counts of all mount objects of each superblock are 0, unmount the superblock.
[0053] In the embodiments of the present disclosure, monitoring the status of the superblocks of multiple containers and unmounting the superblocks of multiple containers according to the status of the superblocks may further include:
[0054] When the active status count of any superblock is 0, enter the process of detecting the active status count of the next superblock; when the reference count of any mount object is 0, enter the process of detecting the reference count of the next mount object.
[0055] In the embodiments of the present disclosure, the superblock may include a first superblock corresponding to the sub-container and a second superblock corresponding to the main container.
[0056] In the embodiments of the present disclosure, monitoring the status of the superblocks of multiple containers and unmounting the superblocks of multiple containers according to the status of the superblocks may include:
[0057] Monitor the status of the first superblock corresponding to each sub-container, and unmount each first superblock according to the status of the first superblock; and,
[0058] Monitor the status of the second superblock corresponding to the main container, and unmount the second superblock according to the status of the second superblock.
[0059] In the embodiments of the present disclosure, monitoring the status of the superblocks of multiple containers and unmounting the superblocks of multiple containers according to the status of the superblocks may further include:
[0060] After unmounting each first superblock according to the status of the first superblock, monitor the status of the second superblock corresponding to the main container, and unmount the second superblock according to the status of the second superblock.
[0061] In the embodiments of the present disclosure, since the first superblock of the sub-container and the second superblock of the main container have a parent-child association relationship, only after unmounting the first superblock can the second superblock of the main container be successfully unmounted. Therefore, the first superblocks of multiple sub-containers can be unmounted first. For example, the main container first unmounts these superblocks:
[0062] unmount / data / cells / home / data (the first superblock corresponding to the living container);
[0063] unmount / data / cells / work / data (the first superblock corresponding to the work container).
[0064] In the embodiments of the present disclosure, monitoring the status of the first superblock corresponding to each sub-container and unmounting each first superblock according to the status of the first superblock may include:
[0065] For each first superblock, respectively detect the number of active statuses of the first superblock; the number of active statuses of the first superblock is the count of processes sharing and occupying each first superblock;
[0066] When the number of active statuses of any first superblock is not 0, check the reference count of each first mount object of the first superblock;
[0067] When the reference count of any first mount object is not 0, forcibly set the reference count of the first mount object to 0;
[0068] When the reference counts of all first mount objects of each first superblock are 0, unmount the first superblock.
[0069] In the embodiments of the present disclosure, monitoring the status of the first superblock corresponding to each sub-container and unmounting each first superblock according to the status of the first superblock may further include:
[0070] When the active status number of any first superblock is 0, enter the process of detecting the active status number of the next first superblock;
[0071] When the reference count of any first mount object is 0, enter the process of detecting the reference count of the next first mount object.
[0072] In the embodiments of the present disclosure, when unloading the first superblock of a sub-container, the active status number of the first superblock and the reference count of the first mount object can be monitored.
[0073] In the embodiments of the present disclosure, the active status number of each first superblock mounted by each sub-container can be checked. The active status number of the first superblock is the count of each process sharing and occupying this first superblock; if the active status number of this first superblock is 0, exit this check and continue to check the next first superblock. If the active status number of this first superblock is not 0, then check the reference count of each first mount object of this first superblock.
[0074] In the embodiments of the present disclosure, each process of the first superblock will occupy this first superblock when starting, and the system will clone a first mount object for this process to use this first superblock. The reference count of the first mount object (including but not limited to file object, file path object, etc.) is the number of times of performing operations such as file operations and folder path accesses on this first mount object. Each file operation and folder path access will increase this reference count.
[0075] In the embodiments of the present disclosure, if it is detected that the reference count of any first mount object is 0, exit this check and continue to check the next first mount object. If it is detected that the reference count of any first mount object is not 0, then forcibly set the reference count of this first mount object to 0, and when the reference counts of all first mount objects of each first superblock of all sub-containers are 0, unload the first superblocks of all sub-containers.
[0076] In the embodiments of the present disclosure, after the main container unloads the first superblock of the sub-container, it can unload its own main file system of the main container, including the superblocks corresponding to the data area and the system device area (i.e., the second superblock). The main container realizes the unloading of its own file system by unloading its own second superblock.
[0077] In the embodiments of the present disclosure, monitor the status of the second superblock corresponding to the main container, and unload the second superblock according to the status of the second superblock, including:
[0078] Detect the active status number of the second superblock; the active status number of the second superblock is the count of the processes sharing and occupying each second superblock;
[0079] When the number of active states of the second superblock is not 0, check the reference count of each second mount object of the second superblock;
[0080] When the reference count of any second mount object is not 0, forcibly set the reference count of the second mount object to 0;
[0081] When the reference counts of all the second mount objects of the second superblock are 0, unmount the second superblock.
[0082] In the embodiments of the present disclosure, monitoring the status of the second superblock corresponding to the main container and unmounting the second superblock according to the status of the second superblock may further include:
[0083] When the number of active states of any second superblock is 0, enter the process of detecting the number of active states of the next second superblock;
[0084] When the reference count of any second mount object is 0, enter the process of detecting the reference count of the next second mount object.
[0085] In the embodiments of the present disclosure, before unmounting the main container file system, the number of active states of all the second superblocks mounted by the main container may be checked. The number of active states of the second superblock is the count of this second superblock shared and occupied by each process; if the number of active states of this second superblock is 0, exit this check and continue to check the next second superblock, if the number of active states of this second superblock is not 0, then check the reference count of each second mount object of this second superblock.
[0086] In the embodiments of the present disclosure, each process of the second superblock will occupy this second superblock when starting, and the system will clone a second mount object for this process to use this second superblock. The reference count of the second mount object (including but not limited to file object, file path object, etc.) is the number of times of performing operations such as file operations and folder path accesses on this second mount object, and each file operation and folder path access will increase this reference count.
[0087] In the embodiments of the present disclosure, if it is detected that the reference count of any second mount object is 0, exit this check and continue to check the next second mount object. If it is detected that the reference count of any second mount object is not 0, forcibly set the reference count of this second mount object to 0, and when the reference counts of all the second mount objects of each second superblock of all sub - containers are 0, unmount all the second superblocks of the main container.
[0088] In the embodiments of the present disclosure, the main container unmounts its own main file system, including the second superblocks corresponding to the data area and the system device area, such as:
[0089] unmount / data;
[0090] unmount / dev / *。
[0091] In the embodiments of the present disclosure, unloading the superblocks of multiple containers according to the status of the superblocks includes:
[0092] Detecting system alarms;
[0093] Recording the file resources corresponding to each detected system alarm as an abnormal file node respectively.
[0094] In the embodiments of the present disclosure, by recording each abnormal file node, it facilitates eliminating each system alarm after unloading the superblocks (the first superblock and the second superblock), thereby preventing file data loss and abnormal conflicts, and avoiding incomplete unloading of the file system between containers.
[0095] In the embodiments of the present disclosure, after recording the file resources corresponding to each detected system alarm as an abnormal file node respectively, the method may further include:
[0096] Checking the unreleased file system resources according to the abnormal file nodes;
[0097] Correcting the unreleased file system resources.
[0098] In the embodiments of the present disclosure, the file system resources include processes and / or files.
[0099] In the embodiments of the present disclosure, since some file system resources are deployed earlier, these file system resources are not containerized, so that when the superblocks are unloaded, these file system resources are still being referenced and not released, resulting in system alarms. Therefore, after obtaining the system alarm information, the unreleased file system resources can be corrected according to the recorded abnormal file nodes (that is, checking the corresponding file system resources according to each abnormal file node and attributing the file system resources to the corresponding sub-container or main container), so that when shutting down or restarting next time, the alarms will be eliminated during the process of unloading the superblocks, thus ensuring the successful unloading of all superblocks during the shutdown or restart process, and finally ensuring the successful unloading of the / data partition of the main container, and avoiding the sudden-power-off problem when starting up.
[0100] In summary, through the solution of the embodiments of the present disclosure, the file system of the multi-container operating system can be unloaded efficiently and smoothly, and the system can be shut down or restarted normally, avoiding problems such as incomplete unloading of the file system between containers or hardware device conflicts causing the system to freeze.
[0101] The embodiments of the present disclosure further provide an electronic device 100, such asFigure 5 As shown in the figure, the electronic device 100 includes:
[0102] One or more processors 101;
[0103] 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;
[0104] One or more input / output (I / O) interfaces 103, connected between the processor 101 and the memory 102, configured to implement information interaction between the processor 101 and the memory 102.
[0105] Among them, the processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.; the memory 102 is a device with data storage capabilities, including but not limited to a random access memory (RAM, more specifically such as SDRAM, DDR, etc.), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory (FLASH); the I / O interface (read / write interface) 103 is connected between the processor 101 and the memory 102 and can implement information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus), etc.
[0106] In some embodiments, the processor 101, the memory 102, and the I / O interface 103 are interconnected through a bus 104 and are further connected to other components of the computing device.
[0107] The embodiments of the present disclosure also provide a computer-readable storage medium 200, such as Figure 6 As shown in the figure, a computer program is stored on the computer-readable storage medium 200. When the computer program is executed by a processor, the file system unloading method is implemented.
[0108] Those of ordinary skill in the art can understand that all or some of the functional modules / units disclosed above can be implemented as software, firmware, hardware, and their appropriate combinations.
[0109] In a hardware implementation, the division of the functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be executed by several physical components in cooperation.
[0110] 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 transitory medium). As is well known to those of ordinary skill 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 includes, but is 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 magnetic disk storage; compact disc read only memory (CD-ROM), digital versatile disc (DVD), or other optical disc storage; magnetic cassettes, tapes, magnetic disk storage, or other magnetic storage; and any other medium that can be used to store the desired information and that can be accessed by a computer. In addition, as is well known to those of ordinary skill 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.
[0111] The present disclosure has disclosed example embodiments, and although specific terms have been employed, they are used only and should be interpreted only as having a general illustrative meaning and not for a limiting purpose. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in connection with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in connection with other embodiments, unless otherwise expressly stated. Accordingly, those skilled in the art will understand that various forms and details may be changed without departing from the scope of the present disclosure as set forth by the appended claims.
Claims
1. A method for uninstalling a file system, characterized in that: The method comprises: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: The electronic device comprises: 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 processor and the memory and are configured to implement information interaction between the processor 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.