Stack file system, system management method, controller, chip device, and vehicle

Abstract

A stack file system, a system management method, a controller, a computer readable storage medium, a computer program product, a chip device, and a vehicle. The stack file system comprises a first write partition and a second write partition; the first write partition and the second write partition are used for storing upgrade firmware in a system version file; the first write partition is located on the upper layer of the second write partition; and the second write partition is used for covering or recovering the first write partition.

Description

Stacked file system, system management method, controller, chip device and vehicle

[0001] This application claims priority to Chinese application No. 202410844192.8, filed on June 26, 2024, entitled: Stacked file system, system management method, controller, chip device and vehicle, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] Embodiments of the present application relate to, but are not limited to, the technical field of file system, and more particularly to a stacked file system, a system management method, and related chip device, controller, computer readable storage medium, computer program product and vehicle. BACKGROUND

[0003] The automotive domain controller architecture generally includes a bottom layer operating system and an in-vehicle middleware, and inevitably exists a disk writing service. In the prior art, the read-only partition and the write partition of the file system are usually mounted, but only the read-only partition is protected, and the writeable partition is not protected, which will cause the data of the writeable partition to be lost when the system is damaged, and the system reliability and security are poor; or when the file system is upgraded by over-the-air (OTA) technology, the read-only partition and the write partition files are backed up at the same time, which occupies too much system storage resources, and the flexibility and scalability are low. TECHNICAL SOLUTION

[0004] The present application is proposed to solve at least one of the above problems. According to a first aspect of the present application, a stacked file system is provided, the stacked file system comprising: a first write partition and a second write partition;

[0005] The first write partition and the second write partition are used to store upgrade firmware in a system version file;

[0006] The first write partition is located above the second write partition; and

[0007] The second write partition is used to cover or repair the first write partition.

[0008] In an embodiment of the present application, the file system comprises: a read-only partition;

[0009] The read-only partition is used to store non-upgrade firmware in a system version file; and

[0010] The read-only partition is located below the second write partition.

[0011] According to a second aspect of the present application, a system management method is provided, the method being applied to any one of the above stacked file systems, comprising:

[0012] receiving a system version file; and

[0013] storing upgrade firmware in the system version file to a first write partition and a second write partition;

[0014] the second write partition is used to overwrite or repair the first write partition.

[0015] In one embodiment of the present application, the method further comprises:

[0016] storing non-upgrade firmware in the system version file to a read-only partition.

[0017] In one embodiment of the present application, the method further comprises:

[0018] repairing the first write partition in response to the first write partition being damaged.

[0019] In one embodiment of the present application, repairing the first write partition when the first write partition is damaged comprises:

[0020] analyzing disk data of the first write partition by a system tool in response to the first write partition being damaged and repairable, and self-repairing the first write partition by the disk data;

[0021] supplementing the first write partition by data in the second write partition in response to data in the repaired first write partition being lost;

[0022] deleting data in the first write partition by an application in response to data in the repaired first write partition being unusable, and updating data in the second write partition to the first write partition; and

[0023] formatting the first write partition in response to the first write partition being damaged and unrepairable, and updating data in the second write partition to the first write partition.

[0024] In one embodiment of the present application, the method further comprises:

[0025] updating upgrade firmware in the latest system version file to the second write partition in response to the system version file being upgraded;

[0026] updating the second write partition to an upper partition after the updating is successful;

[0027] updating the first write partition to a lower partition; and

[0028] updating the upgrade firmware to the lower partition.

[0029] In an embodiment of the present application, the method further comprises: loading the files in the read-only partition that need to be updated into the first write partition of the upgraded firmware, and hiding the files in the read-only partition that need to be updated, when the files in the read-only partition need to be updated.

[0030] In an embodiment of the present application, the method further comprises:

[0031] In response to the files in the read-only partition needing to be upgraded, obtaining the non-upgraded firmware in the storage system version file; and

[0032] Upgrading the files in the read-only partition that need to be upgraded by the non-upgraded firmware.

[0033] According to a third aspect of the present application, a controller is provided, comprising a memory and a processor, the memory storing any of the above-mentioned stacked file systems and computer instructions, and the computer instructions being executed by the processor to implement any of the above-mentioned system management methods.

[0034] According to a fourth aspect of the present application, a computer-readable storage medium is provided, storing any of the above-mentioned stacked file systems and computer instructions, and the computer instructions being executed by a processor to implement any of the above-mentioned system management methods.

[0035] According to a fifth aspect of the present application, a computer program product is provided, comprising any of the above-mentioned stacked file systems and computer instructions, and the computer instructions being executed by a processor to implement any of the above-mentioned system management methods.

[0036] According to a sixth aspect of the present application, a chip device is provided, comprising any of the above-mentioned stacked file systems, or being capable of executing any of the above-mentioned system management methods.

[0037] According to a seventh aspect of the present application, a vehicle is provided, comprising any of the above-mentioned stacked file systems, or being capable of executing any of the above-mentioned system management methods.

[0038] The stacked file system, the system management method, the controller, the computer-readable storage medium, the computer program product, the chip device and the vehicle provided by the embodiments of the present application, the stacked file system of the present application stores the upgraded firmware in the first write partition and the second write partition in the system version file, the second write partition can repair the first write partition, and the reliability and the safety of the system are improved. Meanwhile, when OTA is needed, only the upgraded firmware in the first write partition needs to be upgraded, and the entire file system does not need to be upgraded, storage resources are saved, and the flexibility and the scalability of the system are improved. BRIEF DESCRIPTION OF DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiment description. Obviously, the drawings described in the following embodiment are only some embodiments of the present application, and the present application should not be limited to these drawings. Based on the embodiments of the present application described in the present application, all other embodiments obtained by those skilled in the art without creative labor should fall within the protection scope of the present application.

[0040] FIG. 1 is a structural schematic diagram of a read-only partition and a write partition in the related art;

[0041] FIG. 2 is a structural schematic diagram of a stacked file system provided by an embodiment of the present application;

[0042] FIG. 3 is a structural schematic diagram of a stacked file system provided by another embodiment of the present application;

[0043] FIG. 4 is a flow schematic diagram of a system management method provided by an embodiment of the present application;

[0044] FIG. 5 is a flow schematic diagram of self-rescue and repair of a stacked file system provided by an embodiment of the present application;

[0045] FIG. 6 is a schematic diagram of OTA based on A / B partition in the related art;

[0046] FIG. 7 is a structural schematic diagram of a first write partition after update provided by an embodiment of the present application;

[0047] FIG. 8 is a flow schematic diagram of SOC software OTA provided by an embodiment of the present application;

[0048] FIG. 9 is a structural schematic diagram of a controller provided by an embodiment of the present application;

[0049] FIG. 10 is a structural schematic diagram of a chip device provided by an embodiment of the present application.

[0050] Embodiments of the present application

[0051] In order to make the purpose, technical solutions and advantages of the present application more obvious, the following will describe the example embodiments according to the present application with reference to the drawings. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments of the present application, and it should be understood that the present application is not limited to the example embodiments described herein. Based on the embodiments of the present application described in the present application, all other embodiments obtained by those skilled in the art without creative labor should fall within the protection scope of the present application.

[0052] In the following description, numerous specific details are set forth to provide a more thorough understanding of the present application. However, it will be apparent to one of skill in the art upon

[0053] It should be understood that the present application can be carried out in various forms without departing from the spirit or essential character thereof. Rather, the present application is to cover by the appended claims any and all resulting forms of the application, including cases where the following detailed description is implemented in a different sequence.

[0054] For a thorough understanding of the present application, reference should be made to the following detailed description together with the accompanying drawings wherein:

[0055] In the related art, as shown in FIG. 1, the read-only partition is placed in the Lower layer (lower partition), the write partition is placed in the Upper layer (upper partition), and the Merged layer combines the contents of the Lower layer and the Upper layer, so that the content displayed on the operating system is the combined content of the read-only partition and the write partition. Since important data such as root files in the related art can be stored in the write partition, in the case of abnormal power failure, the write partition has a probability of causing file system damage. Because software cannot predict when power failure will occur, the write disk process will perform a cyclic erase and write action, at which time if power is removed, there will be a probability of incomplete write data, old data being erased, etc., so the write partition file system will be damaged and cannot be normally loaded.

[0056] Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The following embodiments and features in the embodiments can be combined with each other without conflict.

[0057] The first aspect of the present application provides a stacked file system, as shown in FIG. 2, the stacked file system 1000 includes a first write partition 1001 and a second write partition 1002.

[0058] The first write partition 1001 and the second write partition 1002 are used to store the upgraded firmware in the system version file; the first write partition 1001 is located above the second write partition 1002, and the second write partition 1002 is located below the first write partition 1001; the second write partition 1002 is used to cover or repair the first write partition 1001.

[0059] It should be noted that the first write partition 1001 allows writing and modifying of data, which enables the stacked file system 1000 to receive and install updates from a remote server. By placing the upgrade firmware that needs to be updated in the first write partition 1001, the update can be performed without affecting the root file, thereby improving the flexibility and scalability of the stacked file system 1000.

[0060] Specifically, as shown in FIG. 3, the stacked file system 1000 further includes a read-only partition 1003. The read-only partition is used to store non-upgrade firmware in the system version file. The read-only partition is located below the second write partition 1002.

[0061] As an example, the non-upgrade firmware includes the root file, the heartbeat file, and the like.

[0062] It should be noted that for the read-only partition, data cannot be modified once written, which guarantees the high stability and reliability of the data stored therein, thereby ensuring the safety of the firmware such as the root file that does not need to be updated.

[0063] As an example, when the first write partition 1001 abnormally powers off, the second write partition 1002 is placed on the upper layer of the stacked file system 1000, the first write partition 1001 is placed on the lower layer of the stacked file system 1000, and the stacking order in the stacked file system 1000 is changed to the second write partition 1002, the first write partition 1001, and the read-only partition from top to bottom.

[0064] It is worth mentioning that the second write partition 1002 can serve as a backup of the first write partition 1001, and before the upgrade firmware in the first write partition 1001 is updated, the firmware that needs to be updated stored in the first write partition 1001 and the second write partition 1002 is the same. When the first write partition 1001 is working normally, the second write partition 1002 does not participate in read-write operations.

[0065] As an example, the firmware such as the root file that does not need to be updated can be classified into the read-only partition according to directories and subdirectories, and the firmware that needs to be updated can be divided into the first write partition 1001 and the second write partition 1002.

[0066] As another example, in the automotive domain controller architecture, the first write partition 1001 and the second write partition 1002 can further include most of the vehicle middleware. A small part of the vehicle middleware (such as the heartbeat service) can be stored in the read-only partition.

[0067] It should be further noted that when the file system first receives a file or receives a new file (system version file), it is first stored in the fixed disk of the file system and saved all the time; then the OTA file is updated to the first write partition 1001 and the second write partition 1002 through the stacked file system.

[0068] The stack file system 1000 of the embodiment of the present application stores the non-upgrade firmware in the system version file in the read-only partition and protects it, and stores the upgrade firmware in the system version file in the first write partition 1001 and the second write partition 1002, and the second write partition 1002 can repair the first write partition 1001; when the system is abnormal, the read-only partition is protected and the write partition is backed up, thereby improving the reliability and security of the system. At the same time, when the firmware needs to be upgraded, only the upgrade firmware in the first write partition 1001 needs to be upgraded, and the entire file system does not need to be upgraded, thereby saving storage resources and improving the flexibility and scalability of the system.

[0069] The second aspect of the present application provides a system management method applied to the stack file system described above, as shown in FIG. 4, the system management method comprises:

[0070] S1, receiving a system version file.

[0071] S2, storing the upgrade firmware in the system version file to the first write partition and the second write partition, and the second write partition is used to overwrite or repair the first write partition.

[0072] Specifically, the system management method further comprises: storing the non-upgrade firmware in the system version file to the read-only partition.

[0073] As a feasible implementation, the first write partition can be placed in the Upper layer of the stack file system, and the second write partition and the read partition can be placed in the Lower layer of the stack file system. When an application reads a file, the stack file system will first check whether the file exists in the Upper layer. If it exists, the file content in the Upper layer is returned. If the Upper layer does not have the file, the stack file system will search for the file in the Lower layer. When the application writes a file, regardless of whether the file exists in the Lower layer, the stack file system will write data to the Upper layer. If the Lower layer has a file with the same name, the file in the Upper layer will "cover" or "overwrite" the file in the Lower layer. The stack file system writes data to the Upper layer is a kind of data redirection disk operation, but the application cannot perceive.

[0074] The system management method of the embodiment of the application stores the non-upgrade firmware in the system version file in the read-only partition and protects it, stores the upgrade firmware in the system version file in the first write partition and the second write partition, and the second write partition can repair the first write partition; when the system is abnormal, the read-only partition is protected and the write partition is backed up, thereby improving the reliability and security of the system. Meanwhile, when the firmware needs to be upgraded, only the upgrade firmware in the first write partition needs to be upgraded, and the whole file system does not need to be upgraded, thereby saving storage resources and improving the flexibility and scalability of the system.

[0075] In some embodiments, the system management method further comprises repairing the first write partition when the first write partition is damaged.

[0076] Specifically, repairing the first write partition when the first write partition is damaged comprises:

[0077] S31, when the first write partition is damaged and can be repaired, analyzing the disk data of the first write partition by a system tool and repairing the first write partition by the disk data.

[0078] S32, when the data in the repaired first write partition is lost, supplementing the first write partition by the data in the second write partition.

[0079] S33, when the data in the repaired first write partition cannot be used, deleting the data in the first write partition by an application program and updating the data in the second write partition to the first write partition.

[0080] S34, when the first write partition is damaged and cannot be repaired, formatting the first write partition and updating the data in the second write partition to the first write partition.

[0081] Preferably, the application program comprises relevant middleware or algorithms.

[0082] As an example, when the data in the repaired first write partition cannot be used, the data in the first write partition can be deleted by a file self-checking program.

[0083] Taking the startup of a system on chip (SOC) software (with a stacked file system installed) as an example, the self-saving and repairing process of the stacked file system is illustrated in FIG. 5:

[0084] A11, the SOC is powered on to enter an initramfs memory file system, which is a temporary system of a DDR memory and will release the memory after use, and is a process before the root file system is loaded.

[0085] A12, initiate detection of the first write partition in the upper layer, and if the first write partition is normal, directly enter step A5.

[0086] A13, if the first write partition is abnormal, enter a repair process, and the disk can be repaired by using an open source tool Fsck.

[0087] A14, if the first write partition cannot be repaired, format the first write partition, and after the formatting operation, the first write partition will be restored to the original state, and the data in the second write partition is updated to the first write partition.

[0088] A15, the read-only partition, the first write partition and the second write partition form a stacked file system, and the disk repair does not modify the stacking order.

[0089] In this embodiment, when the first write partition is damaged but can be repaired, the first write partition can be self-repaired. If the data is lost after repair, the data in the second write partition can be supplemented in time to ensure the integrity of the key data. If the repaired data cannot be used, the data of the second write partition can be updated to the first write partition, thereby restoring the normal operation of the system. When the first write partition is damaged and cannot be repaired, it can be quickly formatted and updated using the data of the second write partition, thereby improving the fault tolerance of the stacked file system.

[0090] In the related art, as shown in FIG. 6, the related art A / B partition OTA-based solution needs to update the A / B partition at the same time, so that the A / B upgrade partition disk resource occupies too much.

[0091] In some embodiments, as shown in FIG. 7, the system management method further includes: when the system version file is upgraded, updating the latest system version file to the second write partition; and after the update is successful, updating the second write partition to the upper layer partition, updating the first write partition to the lower layer partition, and updating the upgrade firmware to the lower layer partition.

[0092] Specifically, after the update is successful, the stacking order in the stacked file system is changed to the second write partition, the first write partition and the read-only partition from top to bottom.

[0093] It should be noted that this upgrade method may cause the write partition file to be asymmetric, and cannot guarantee that the first write partition and the second write partition are completely the same. Based on this consideration, the OTA package maker needs to appropriately add or delete files in the image. The first write partition and the second write partition can also be updated at the same time, but this method may cause the first write partition and the second write partition to be damaged at the same time.

[0094] In this embodiment, the updating operation of the upgrade firmware is limited to the second write partition, which can effectively reduce the risk in the upgrading process. If a failure occurs in the upgrading process, the stack file system can still fall back to the old version of the firmware in the first write partition, ensuring stable operation of the stack file system. At the same time, only the second write partition needs to be updated via OTA, saving memory resources.

[0095] In some embodiments, the system management method further includes: when a file in the read-only partition needs to be updated, loading the file in the read-only partition that needs to be updated into the upgrade firmware of the first write partition, and hiding the file in the read-only partition that needs to be updated.

[0096] It should be noted that all or part of the files in the read-only partition can be updated.

[0097] As an example, when a file in the read-only partition needs to be updated, the file that needs to be updated can also be directly written to the read-only partition. However, such direct writing to the read-only partition is not safe.

[0098] Specifically, the updated file corresponding to the read-only partition can be recorded as a first target file. The first target file is stored in the first write partition. When the system needs to access the first target file, the first target file will be read from the first write partition instead of the un-updated first target file in the read-only partition.

[0099] In this embodiment, the stack file system can update the files in the read-only partition without damaging the stability of the read-only partition. At the same time, by writing the upgrade file to the first write partition and hiding the old file in the read-only partition, the smooth progress of the updating process and the integrity of the data are ensured.

[0100] In some embodiments, the system management method further includes: when a file in the read-only partition needs to be upgraded, obtaining non-upgrade firmware in the storage system version file, and upgrading the file in the read-only partition that needs to be upgraded by using the non-upgrade firmware.

[0101] It should be noted that when the file in the read-only partition is upgraded, the memory file system (a disk storing, for example, an OTA file) can be entered to download the relevant file in the read-only partition in the OTA package for upgrading.

[0102] If the heartbeat service is damaged, the functional safety chip may not be able to monitor the SOC heartbeat, and the SOC software will be reset.

[0103] In some embodiments, the firmware that does not need to be upgraded includes the heartbeat service; and the first write partition is further used to store a log service of the read-only partition.

[0104] It should be noted that the log service is an important component of the system, which records various events and state information during the running of the system. These information is crucial for troubleshooting, performance analysis and system optimization. Storing the log service in the first write partition enables the system to dynamically record log information during runtime without modifying the data in the read-only partition. At the same time, redirecting the path of the write log to the write partition is imperceptible to the application software.

[0105] In this embodiment, the stability and reliability of the core firmware are ensured, and sufficient flexibility is provided to support real-time updating and access of the log service.

[0106] In some embodiments, the system management method further comprises: when the first write partition abnormally powers off, placing the second write partition in the upper partition of the stacked file system, placing the first write partition in the lower partition of the stacked file system, and changing the stacking order in the stacked file system to the second write partition, the first write partition and the read-only partition from top to bottom.

[0107] When the second target file needs to be written to the stacked file system, the second target file is written to the second write partition.

[0108] It should be noted that the second write partition can serve as a backup for the first write partition. Before the firmware in the first write partition is updated, the firmware stored in the first write partition and the second write partition is the same. When the first write partition is working normally, the second write partition does not participate in read and write operations.

[0109] As an example, the root file and the firmware that does not need to be upgraded can be classified into the read-only partition according to the directory and subdirectory, and the firmware that needs to be upgraded can be divided into the first write partition and the second write partition.

[0110] As another example, in the automotive domain controller architecture, the first write partition and the second write partition can also include most of the vehicle middleware. A small part of the vehicle middleware (such as the heartbeat service) can be stored in the read-only partition.

[0111] Next, taking the OTA of the SOC software (installed with the stacked file system) as an example, the OTA process is illustrated in FIG. 8.

[0112] A21, start the SOC, receive the OTA instruction, and perform the conventional operations such as local packet reception, verification and FLAG setting.

[0113] A22, after the stacked file system is started, the disk FLAG is searched. If Upper = 1, it indicates that the current stacking order from top to bottom is the first write partition-second write partition-read-only partition, and the OTA is performed on the second write partition. If Upper = 2, the OTA will be performed on the first write partition.

[0114] A23, after the update is completed and synchronized to the disk, reconfiguring the stacking order of the stacked file system, assuming Upper = 1, the stacking order is updated from top to bottom as the second write partition - the first write partition - the read-only partition, Upper = 2, the stacking order is updated from top to bottom as the first write partition - the second write partition - the read-only partition.

[0115] In addition, the application further provides a controller, as shown in Figure 9, the controller 100 comprises: a memory 101, a processor 102 and computer instructions stored in the memory 101 and the stacked file system described above. Wherein, the memory 101 and the processor 102 are connected, such as through the bus 103. Optionally, the controller 100 can also include a transceiver 104. The computer instructions are executed by the processor 102 to implement the system management method described above. It should be noted that the transceiver 104 is not limited to one in actual application, and the structure of the controller 100 does not constitute a limitation on the embodiments of the application.

[0116] The processor 102 can be a central processing unit (CPU), 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, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, devices and circuits described in combination with the disclosure. The processor 102 can also be a combination of computing functions, such as one or more microprocessor combinations, combinations of DSP and microprocessor, etc.

[0117] The bus 103 can include a channel for transmitting information between the above-mentioned components. The bus 103 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus 103 can be divided into address bus, data bus, control bus, etc. For the convenience of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or only one type of bus.

[0118] The memory 101 is configured to store computer instructions corresponding to the system management method of the embodiments of the present application, and the computer instructions are executed by the processor 102. The processor 102 is configured to execute the computer instructions stored in the memory 101, so as to realize the content shown in the foregoing system management method embodiments.

[0119] The controller 100 includes, but is not limited to, a mobile terminal such as a personal digital assistant, a tablet computer, and the like. The controller 100 shown in FIG. 9 is merely an example, and should not bring any limitation to the functions and use range of the embodiments of the present application.

[0120] The controller 100 of the embodiments of the present application stores the upgrade firmware in the first write partition and the second write partition in the system version file, and the second write partition can repair the first write partition, thereby improving the reliability and security of the system. Meanwhile, when OTA is needed, only the upgrade firmware in the first write partition needs to be upgraded, and the entire file system does not need to be upgraded, thereby saving storage resources and improving the flexibility and scalability of the system.

[0121] In addition, the present application further provides a computer readable storage medium, which stores computer instructions and the stacked file system described above, and the instructions are executed by the processor to realize the system management method described above.

[0122] The computer readable storage medium of the embodiments of the present application can realize the system management method, so that when OTA is needed, only the upgrade firmware in the first write partition needs to be upgraded, and the entire file system does not need to be upgraded, thereby saving storage resources and improving the flexibility and scalability of the system.

[0123] In addition, the present application further provides a computer program product, which includes computer instructions and the stacked file system described above, and the computer instructions are executed by the processor to realize the system management method described above.

[0124] The computer program product of the embodiments of the present application can realize the system management method, so that when OTA is needed, only the upgrade firmware in the first write partition needs to be upgraded, and the entire file system does not need to be upgraded, thereby saving storage resources and improving the flexibility and scalability of the system.

[0125] In addition, as shown in FIG. 10, the present application further provides a chip device 10, which includes the stacked file system 1000 described above or the system management method described above.

[0126] The chip device of the embodiment of the present application stores the upgrade firmware in the system version file in the first write partition and the second write partition, the second write partition can repair the first write partition, and the reliability and security of the system are improved. Meanwhile, when OTA is needed, only the upgrade firmware in the first write partition needs to be upgraded, and the whole file system does not need to be upgraded, storage resources are saved, and the flexibility and scalability of the system are improved.

[0127] In addition, the present application also provides a vehicle comprising the controller, the computer program product or the chip device.

[0128] Although the example embodiments have been described herein with reference to the accompanying drawings, it is to be understood that the example embodiments are only exemplary and are not intended to limit the scope of the present application. Those of ordinary skill in the art can make various changes and modifications without departing from the scope and spirit of the present application. All these changes and modifications are intended to be included within the scope of the present application as claimed in the appended claims.

[0129] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be realized by electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on the specific application and design constraints of the technical solution. Those of ordinary skill in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0130] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the units is only a logical functional division, and actual implementation can have another division manner, for example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0131] In the specification provided herein, a large number of specific details are described. However, it can be understood that the embodiments of the present application can be practiced without these specific details. In some examples, well-known methods, structures and techniques are not shown in detail in order not to obscure the understanding of the present specification.

[0132] Similarly, it is to be understood that the features of the present application that are of a proprietary nature are set forth in the appended set of claims. If specific embodiments are described in detail in the specification and illustrated in the drawings, it will nonetheless be understood that the generic principles of the application as set forth in the claims are not to be limited to such specific embodiments. Namely, it is not intended that the application be limited to the embodiments contained herein, but on the contrary, it is intended to cover alternatives, modifications, and equivalents as can be included within the spirit and scope of the application as defined by the appended claims. Similarly, it should be understood that, in describing embodiments of the application, specific terminology is employed for the sake of clarity. However, the application is not limited to the specific terminology so selected. A still further object of the application is to each and every patentable aspect, subaspect or implementation thereof described herein.

[0133] Those skilled in the art will appreciate that all features described in this specification (including the summary of the application, abstract, and drawings) and / or any accompanying claims can be combined in any combination. The above summary of the application is not intended to describe each and every implementation of the application, aspects and / or implementations of which can include, but are not limited to, exemplary environments in which aspects of the application can be used. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing this application, but one of ordinary skill in the art will recognize that modifications and / or

[0134] Further, those skilled in the art will appreciate that a combination of aspects from different embodiments can indeed be within the scope of the application and form different embodiments. For example, in the claims, any of the claims can be used in combination with any of the examples, features, component combinations, or method steps described herein.

[0135] Various component embodiments of the application can be implemented in hardware, or as software modules running in one or more processors, or in combinations thereof. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all of the functionality of some of the modules according to embodiments of the application. The application can also be implemented as a program (e.g., computer program and computer program product) for performing part or all of the methods described herein. Such program(s) can be stored on a computer readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, or provided on a carrier medium, or in any other form.

[0136] It should be noted that the above-mentioned embodiments illustrate rather than limit the application, and that one skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps other than those listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The application can be implemented by means of both hardware and software, and any combination thereof. In a unitary claim, several devices or sub-claims can be joined by means of the expression "and / or". The use of the term "at least" followed by a list of one or more items should be interpreted as including at least one of the items but it does not exclude the presence of others not listed. The use of the term "one" followed by a list of one or more items should be interpreted as including at least one of the items but it does not exclude the presence of others not listed. It is emphasized that the terms "comprises / comprising" when used in this specification are taken to specify the presence of stated features, integers, steps or components but do not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.

[0137] The above description is only specific embodiments of the present application or specific explanations of specific embodiments, and the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, and all of them should be covered in the protection scope of the present application. The protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A stacked file system, wherein, The file system includes: a first write partition and a second write partition; The first write partition and the second write partition are used to store the upgrade firmware in the system version file; The first write partition is located above the second write partition; and The second write partition is used to overwrite or repair the first write partition.

2. The stacked file system as described in claim 1, wherein, The file system includes: a read-only partition; The read-only partition is used to store non-upgrade firmware in the system version files; and The read-only partition is located below the second write partition.

3. A system management method, said method being applied to a stacked file system as described in any one of claims 1-2, wherein, include: Receive system version file; and Store the upgrade firmware in the system version file to the first write partition and the second write partition; The second write partition is used to overwrite or repair the first write partition.

4. The system management method as described in claim 3, wherein, include: Store the non-upgrade firmware in the system version file to a read-only partition.

5. The system management method as described in any one of claims 3-4, wherein, include: In response to the first write partition being corrupted, the first write partition is repaired.

6. The system management method as described in claim 5, wherein, Repairing the first write partition when it becomes corrupted includes: In response to the first write partition being damaged and repairable, the system analyzes the disk data of the first write partition using system tools and performs self-repair using the disk data; In response to the loss of data in the repaired first write partition, the first write partition is supplemented with data from the second write partition; In response to the unavailability of data in the repaired first write partition, the application deletes the data in the first write partition and updates the first write partition with data from the second write partition; and In response to the first write partition being corrupted and unrepairable, the first write partition is formatted, and the data in the second write partition is updated to the first write partition.

7. The system management method as described in claim 6, wherein, include: In response to the upgrade of the system version file, the upgrade firmware in the latest system version file is updated to the second write partition; After the update is successful, update the second write partition to the parent partition; Update the first write partition to the lower-level partition; and Update the firmware to the lower partition.

8. The system management method as described in claim 7, wherein, include: In response to the need to update files in the read-only partition, the files that need to be updated in the read-only partition are loaded into the upgrade firmware of the first write partition; and Hide the files that need to be updated in the read-only partition.

9. The system management method as described in claim 8, wherein, include: In response to the need to upgrade files in the read-only partition, obtain the non-upgrade firmware from the storage system version file; and Upgrade the files that need to be upgraded in the read-only partition using non-upgrade firmware.

10. A controller, wherein, include: A memory and a processor, wherein the memory stores a stacked file system and computer instructions as described in any one of claims 1-2, and the computer instructions, when executed by the processor, implement the system management method as described in any one of claims 3-9.

11. A computer-readable storage medium applying the system management method of claim 3, wherein a stacked file system and computer instructions as described in any one of claims 1-2 are stored thereon, When the computer instructions are executed by the processor, they implement the system management method according to any one of claims 3-9.

12. A computer program product applying the system management method of claim 3, comprising a stacked file system and computer instructions as described in any one of claims 1-2, wherein, When the computer instructions are executed by the processor, they implement the system management method according to any one of claims 3-9.

13. A chip device comprising the stacked file system of claim 1, wherein, Includes a stacked file system as described in any one of claims 1-2, or performs a system management method as described in any one of claims 3-9.

14. A vehicle comprising the stacked file system of claim 1, wherein, Includes a stacked file system as described in any one of claims 1-2, or performs a system management method as described in any one of claims 3-9.

Images