CN115964204A - File reading and writing method of embedded file system, electronic equipment and storage medium - Google Patents
File reading and writing method of embedded file system, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115964204A CN115964204A CN202111183447.3A CN202111183447A CN115964204A CN 115964204 A CN115964204 A CN 115964204A CN 202111183447 A CN202111183447 A CN 202111183447A CN 115964204 A CN115964204 A CN 115964204A
- Authority
- CN
- China
- Prior art keywords
- file
- read
- write
- embedded
- restart
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000005192 partition Methods 0.000 claims abstract description 75
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 239000000126 substance Substances 0.000 claims description 2
- 230000006870 function Effects 0.000 description 6
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention relates to the field of embedded equipment, and discloses a file reading and writing method of an embedded file system, electronic equipment and a storage medium. The method comprises the steps that a file in a read-write partition is reestablished after the operation of reading/writing the file is failed based on service triggering; after the file is failed to be created, judging whether the embedded equipment has undergone restarting operation; if yes, the read-write partition is mounted again, and after data in the read-write partition are initialized, the embedded device is restarted; and if not, executing the restarting operation of the embedded equipment so as to improve the read-write reliability of the embedded file system.
Description
Technical Field
The present invention relates to the field of embedded devices, and in particular, to a file read/write method for an embedded file system, an electronic device, and a storage medium.
Background
At present, embedded devices are widely applied in multiple fields, and when errors such as Error Correction Code (ECC) occur in a read-write partition of a storage medium of the embedded device, for example, NAND FLASH, a file stored in the read-write partition cannot be read, written, deleted, and created, so that a related service function is lost, and reliability of normal operation of related devices or systems is affected.
Disclosure of Invention
The invention provides a file reading and writing method of an embedded file system, electronic equipment and a storage medium, which are used for improving the reading and writing reliability of the embedded file system.
In order to solve the above technical problem, an embodiment of the present invention provides a file reading and writing method for an embedded file system, including:
based on service triggering, after the failure of executing read/write operation on the file in the read-write partition, the file is created again;
after the file is failed to be created, judging whether the embedded equipment has already undergone restarting operation;
if yes, the read-write partition is mounted again, and after data in the read-write partition are initialized, the embedded device is restarted;
and if not, executing the restarting operation of the embedded equipment.
An embodiment of the present invention also provides an electronic device, including:
at least one processor; and (c) a second step of,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a file read and write method of an embedded file system as described above.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program, and the computer program realizes the file reading and writing method of the embedded file system when being executed by a processor.
Compared with the prior art, the implementation mode of the invention has the advantages that the embedded equipment reestablishes the file after the operation of executing the read/write operation on the file in the read-write partition fails after the triggering based on the service; after the file is failed to be created, judging whether the embedded equipment has undergone restarting operation; if yes, the read-write partition is mounted again, and after data in the read-write partition is initialized, restarting operation of the embedded equipment is executed; and if not, executing the restarting operation of the embedded device. According to the scheme, after the file read/write operation fails, the reason for the read/write operation failure is eliminated by recreating the file; when the file is not created again, the reason of failure of the read/write operation is eliminated by restarting the embedded equipment; when the embedded device is selected to be restarted, if the current embedded device is restarted, the probability that the read-write partition with the read/write operation failure has a fault is high, the formatted read-write partition can be mounted again, and the restart operation of the embedded device is executed after the data in the read-write partition is initialized, so that the probability of eliminating the reason of the read/write operation failure is improved; if the current embedded device is not restarted, the restarting operation of the embedded device can be directly executed to eliminate the reason of the failure of the read/write operation, thereby improving the reliability of the file read-write operation of the embedded file system.
Drawings
FIG. 1 is a first flowchart illustrating a first embodiment of a method for reading and writing files in an embedded file system;
FIG. 2 is a specific flowchart II of a file reading/writing method of an embedded file system according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a method for reading and writing files in an embedded file system according to an embodiment of the present invention;
FIG. 4 is a detailed flowchart IV of a file read/write method of an embedded file system according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present application in various embodiments of the present invention. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments.
The invention relates to a file reading and writing method of an embedded file system. The embedded device refers to a terminal device running an embedded system. The embedded file system refers to a file system based on NAND FLASH, NOR FLASH, eMMc, and other storage media, such as ubifs, yaffs, extfs, and so on.
As shown in fig. 1, the file reading and writing method of the embedded file system provided in this embodiment includes the following steps.
Step 101: and based on the service trigger, after the file in the read-write partition fails to be read/written, the file is re-created.
Wherein, the read-write partition refers to an embedded file system logical partition or volume with read-write attribute. And the files stored in the read-write partition are used for storing the service data of the key service in the terminal equipment, and the key service module in the embedded equipment performs read-write operation on the files. This critical business function is lost when reading or writing is abnormal.
For example, in a vehicle-mounted TBOX implemented by using an embedded device, the TBOX is authenticated before being connected with a private network of a car factory, an authentication file is stored in a read-write partition of the TBOX, and all functions related to the whole private cloud are lost due to the failure of reading and writing of the authentication file; for example, a config file for storing key information such as equipment types and the like in vehicle-mounted TBOX equipment is used, when the file is synchronized among vehicles, reading operation is carried out and needs to be copied to a reading and writing partition of the TBOX, and the equipment cannot be normally started due to the failure of reading of the file; for example, before The vehicle-mounted TBOX and TBOX are connected with an Over-The-Air (FOTA) upgrading server of The mobile terminal, authentication is carried out, the authentication file is stored in a read-write partition of The TBOX, and The FOTA upgrading function is lost due to The read-write failure of The authentication file.
Specifically, after the embedded device is powered on and started, the key service module in the embedded device operates normally. And the key business module executes read/write operation on the file in the read-write partition based on external trigger operation. When the read/write operation fails, the service module recreates the file with the current failed read/write operation so as to eliminate the reason causing the current operation failure as much as possible. After the file is failed to be created, step 102 is entered.
Step 102: and judging whether the embedded device has undergone the restarting operation. If yes, go to step 103; if not, step 104 is entered.
Specifically, when the file is not created again, the key service module triggers the restart operation of the embedded device to eliminate the reason of the operation failure. Before the restart operation is executed, the key service module judges whether the embedded device has already undergone the restart operation, namely judges whether the restart operation to be executed is the non-first-time restart operation after the power-on of this time. And then determining which mode to adopt to execute the restarting operation according to the judgment result.
Step 103: and mounting the formatted read-write partition again, and initializing the data in the read-write partition.
Specifically, when the restart operation to be performed is a non-first-time restart operation after the embedded device is powered on, it indicates that the embedded device has been restarted due to a previous read/write operation failure, and the read/write partition for storing the read/write operation file is likely to be damaged, at this time, the read/write partition needs to be mounted and formatted again, and after data in the read/write partition is initialized, the restart operation on the embedded device can be performed, so that the reason for the operation failure may be effectively eliminated.
In one example, this step may be implemented as follows.
Step 1: and removing the mount of the read-write subarea used for storing the read/write operation file. After the mount is removed, other functional modules can not perform read/write operation on the read-write partition, so that the read-write partition is conveniently subjected to related processing, and the external functional modules cannot be influenced.
Step 2: and formatting the read-write partition, and clearing the data stored in the read-write partition.
And 3, step 3: and mounting the formatted read-write partition, and initializing data in the read-write partition.
Specifically, the key service module initializes the read-write partition, that is, restores the read-write partition to a factory state. Factory state data of the read-write partition is packaged into a version file and is stored in the rootfs read-only partition in advance, and the data comprises a configuration file, a logfs file path specification and the like. Initializing the read-write partition, namely copying the configuration file into the read-write partition, performing soft linking on a file path and the like.
After step 103 is performed, step 104 may continue to be performed.
Step 104: and executing the restarting operation of the embedded file system.
Compared with the related art, in the embodiment, after the embedded device is triggered based on the service and fails to perform read/write operation on the file in the read-write partition, the file is created again; after the file is failed to be created, judging whether the embedded equipment has undergone restarting operation; if so, mounting the read-write partition again, initializing data in the read-write partition, and then executing restart operation on the embedded equipment; and if not, executing the restarting operation of the embedded device. According to the scheme, after the file read/write operation fails, the reason for the read/write operation failure is eliminated by recreating the file; when the file is not established again, the original failure of the read/write operation is eliminated by restarting the embedded equipment; when the embedded device is selected to be restarted, if the current embedded device is restarted, the probability that the read-write partition with the read/write operation failure has a fault is high, the formatted read-write partition can be mounted again, and the restart operation of the embedded device is executed after the data in the read-write partition is initialized, so that the probability of eliminating the reason of the read/write operation failure is improved; if the current embedded device is not restarted, the restarting operation of the embedded device can be directly executed to eliminate the reason of the failure of the read/write operation, thereby improving the reliability of the file read-write operation of the embedded file system.
Another embodiment of the invention relates to a file reading and writing method of an embedded file system. In this embodiment, after the read/write operation on the file in the read-write partition fails, the process of recreating the file is refined. Accordingly, as shown in fig. 2, the step 101 may specifically include the following sub-steps.
Substep 1011: and deleting the file after the failure of executing the read/write operation on the file in the read-write partition.
Specifically, prior to recreating the file, the critical business module may delete the old file that failed the read/write operation.
Substep 1012: and judging whether the file is deleted successfully or not. If yes, go to substep 1013; if not, step 102 is entered.
Specifically, when the file deletion is successful, the key business module can normally execute the re-creation of the file; when the file deletion fails, it indicates that the read-write partition for storing the read/write operation file is likely to be damaged, which not only causes the read/write operation failure, but also fails to delete the file normally, and at this time, it is necessary to consider the restart operation performed on the embedded device, so that it is possible to effectively eliminate the reason causing the operation failure. Before the restart operation is performed on the embedded device, the key service module may determine which restart operation is more suitable by performing step 102. After the specific manner of the restart operation is determined in step 102, the restart operation may be performed according to the corresponding manner, that is, step 104 is performed after step 103 is performed, or step 104 is directly performed.
Substep 1013: the file is recreated.
After sub-step 1013, the steps of step 102 may continue to be performed after a failure to recreate the file.
Compared with the related art, in the embodiment, the embedded device deletes the file first when the file is recreated after the embedded device fails to execute the read/write operation on the file in the read-write partition based on the service trigger, and recreates the file after the file is successfully deleted; if the deletion fails, step 102 can be entered, and a restart operation is performed by selecting a proper restart scheme of the embedded device, so that the reason of the failure of the read/write operation is eliminated, and the reliability of the file read-write operation of the embedded file system is improved.
Another embodiment of the invention relates to a file reading and writing method of an embedded file system. In the present embodiment, the process of determining whether the embedded device has undergone a reboot operation is detailed. A restart identifier is stored in the read-write partition, and when the value of the restart identifier is 0, the embedded device is indicated to have not been subjected to restart operation; when the value of the restart flag is 1, it indicates that the embedded device has undergone a restart operation. Accordingly, as shown in fig. 3, the step 102 may specifically include the following sub-steps.
Substep 1021: and judging whether the value of the current restart identifier is 1.
Specifically, after the embedded device is powered on, the value of the restart identifier is set to 0 by default. And when the key service module triggers the embedded equipment to restart, the key service module sets the value of the restart identifier to be 1.
On this basis, if the result of the determination in sub-step 1021 is negative, step 105 is further included after sub-step 1021.
Step 105: the value of the restart flag is set to 1.
Step 106: it is determined whether the value of the restart flag is successfully set to 1. If yes, go to step 104; if not step 103 is entered.
Specifically, due to the setting process of setting the value of the restart flag to 1, it is essential to perform a write operation to the read-write partition once. If the write operation is successful, step 104 may be entered directly to perform a reboot operation on the embedded device. If the write operation fails, the representation read-write partition is likely to be damaged, which not only causes the read/write operation failure, but also fails to normally write the restart identifier, at this time, step 103 may be entered, the formatted read-write partition is mounted again, and after initializing the data in the read-write partition, step 104 is executed again, and the restart operation of the embedded device is performed, so as to improve the possibility of eliminating the cause of the read/write operation failure.
Compared with the related art, in the embodiment, the embedded device marks whether the embedded device has already undergone the state of the restart operation by storing the restart identifier in the read-write partition. When the current restart identifier is judged not to be 1, the write operation can be executed on the read-write partition first, and the restart identifier is set to be 1. Whether the value of the restart identifier is successfully set to be 1 or not is judged, so that the scheme of the restart operation is further determined to carry out the restart operation, the reason of the failure of the read/write operation is eliminated, and the reliability of the file read-write operation of the embedded file system is improved.
Another embodiment of the invention relates to a file reading and writing method of an embedded file system. In the present embodiment, operations after the file is successfully recreated in step 101 are supplemented. Correspondingly, as shown in fig. 4, after the step 101, after the file is successfully re-created, the method may further include the following steps.
Step 107: and carrying out file initialization on the file.
And the data in the initialized file is the data which is to be stored in the file before the read-write operation fails.
Specifically, by re-creating the file before the current read/write operation fails, the reason causing the current read/write operation failure can be eliminated as much as possible without restarting the embedded device, and the read/write reliability of the embedded file system is improved.
On this basis, after the file initialization is performed on the file, the method may further include: the value of the restart flag is set to 0. Thereby setting the embedded device to a state in which the reboot operation has not been performed.
In addition, the restart operation after the failure of executing the read/write operation on the file in the read-write partition based on the above description may also be applied to the embedded device after the failure of executing the delete operation on the file in the read-write partition based on the service trigger, or after the failure of executing the file create operation in the read-write partition.
In an example, on the basis of the embodiment of the method shown in fig. 1, the method may further include: and executing step 102 and the subsequent steps after the deletion operation of the file in the read-write partition fails based on the service trigger.
In another example, on the basis of the embodiment of the method shown in fig. 1, the method may further include: and based on the service trigger, executing the step 102 and the subsequent steps after the file creating operation in the read-write partition fails.
The corresponding step 102 and the subsequent steps can refer to the foregoing contents, which are not described herein again.
Compared with the prior art, in the embodiment, after the embedded device recreates the file, by initializing the recreated file after the file is successfully created, the reason causing the failure of the current read/write operation can be eliminated as much as possible without restarting the embedded device, and the read/write reliability of the embedded file system is improved.
In addition, in the embodiment of the method, the restart operation after the read/write operation fails is performed on the file in the read-write partition, which can also be applied to the embedded device based on service triggering, after the deletion operation fails to be performed on the file in the read-write partition, or after the file creation operation fails to be performed in the read-write partition, so that the read-write reliability of the embedded file system is improved from the operation perspective of various read-write partitions.
Another embodiment of the invention relates to an electronic device, as shown in FIG. 5, comprising at least one processor 202; and a memory 201 communicatively coupled to the at least one processor 202; wherein the memory 201 stores instructions executable by the at least one processor 202, the instructions being executable by the at least one processor 202 to enable the at least one processor 202 to perform any of the method embodiments described above.
Wherein the memory 201 and processor 202 are coupled in a bus, which may include any number of interconnected buses and bridges that couple one or more of the various circuits of the processor 202 and memory 201 together. The bus may also connect various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 202 is transmitted over a wireless medium through an antenna, which further receives the data and transmits the data to the processor 202.
The processor 202 is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 201 may be used to store data used by processor 202 in performing operations.
Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The computer program realizes any of the above-described method embodiments when executed by a processor.
That is, as can be understood by those skilled in the art, all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.
Claims (10)
1. A file read-write method of an embedded file system is characterized by comprising the following steps:
based on service triggering, after the failure of executing read/write operation on the file in the read-write partition, the file is created again;
after the file is not established again, judging whether the embedded equipment has already undergone restarting operation;
if yes, the formatted read-write partition is mounted again, and after data in the read-write partition is initialized, the embedded equipment is restarted;
and if not, executing the restarting operation of the embedded equipment.
2. The method of claim 1, wherein recreating the file after the failure of performing the read/write operation on the file in the read-write partition comprises:
deleting the file after the file in the read-write partition fails to execute read/write operation;
judging whether the file is deleted successfully or not;
if so, executing the re-creation of the file;
if not, executing the judgment whether the embedded equipment has already undergone the restarting operation.
3. The method according to claim 1, wherein a restart flag is stored in the read-write partition, and when a value of the restart flag is 0, it indicates that the embedded device has not undergone a restart operation; when the value of the restart identifier is 1, indicating that the embedded device has already undergone a restart operation;
the determining whether the embedded device has undergone a reboot operation includes:
and judging whether the value of the current restart identifier is 1.
4. The method of claim 3, wherein after determining whether the current restart flag is 1, the method comprises:
if not, setting the value of the restart identifier to be 1;
judging whether the value of the restart identifier is successfully set to 1;
if yes, executing the restarting operation of the embedded equipment;
and if not, re-mounting the read-write partition, initializing the data in the read-write partition, and then restarting the embedded equipment.
5. The method of claim 1, wherein after said recreating said file, further comprising:
and after the file is successfully created, carrying out file initialization on the file.
6. The method of claim 5, wherein after the initializing the file, further comprising:
and setting the value of the restart identifier to be 0.
7. The method of claim 1, further comprising:
and executing the judgment whether the embedded equipment has undergone restarting operation or not after the deletion operation of the files in the read-write partition fails based on the service trigger.
8. The method of claim 1, further comprising:
and based on the service trigger, after the file creating operation executed in the read-write partition fails, executing the judgment whether the embedded equipment has already undergone the restarting operation.
9. An electronic device, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method of reading and writing files of an embedded file system according to any one of claims 1 to 8.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the file reading and writing method of the embedded file system according to any one of claims 1 to 8.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111183447.3A CN115964204A (en) | 2021-10-11 | 2021-10-11 | File reading and writing method of embedded file system, electronic equipment and storage medium |
| PCT/CN2022/107147 WO2023060976A1 (en) | 2021-10-11 | 2022-07-21 | File reading and writing method for embedded file system, and electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111183447.3A CN115964204A (en) | 2021-10-11 | 2021-10-11 | File reading and writing method of embedded file system, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115964204A true CN115964204A (en) | 2023-04-14 |
Family
ID=85894816
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111183447.3A Pending CN115964204A (en) | 2021-10-11 | 2021-10-11 | File reading and writing method of embedded file system, electronic equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115964204A (en) |
| WO (1) | WO2023060976A1 (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9804925B1 (en) * | 2014-02-25 | 2017-10-31 | Google Inc. | Data reconstruction in distributed storage systems |
| CN104484241B (en) * | 2014-12-10 | 2018-12-11 | 广东欧珀移动通信有限公司 | The method and device that a kind of pair of terminal system file is backed up and restored |
| CN105825126A (en) * | 2016-03-08 | 2016-08-03 | 北京网康科技有限公司 | File protecting method and device |
| CN113488082B (en) * | 2021-07-02 | 2022-07-29 | 山东恒宇电子有限公司 | Audio and video storage method for embedded equipment mechanical hard disk |
-
2021
- 2021-10-11 CN CN202111183447.3A patent/CN115964204A/en active Pending
-
2022
- 2022-07-21 WO PCT/CN2022/107147 patent/WO2023060976A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023060976A1 (en) | 2023-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20110004871A1 (en) | Embedded electronic device and firmware updating method thereof | |
| CN108932249B (en) | Method and device for managing file system | |
| CN110018783B (en) | Data storage method, device and system | |
| CN109086078B (en) | Android system upgrading method and device, server and mobile terminal | |
| US20190227710A1 (en) | Incremental data restoration method and apparatus | |
| RU2653254C1 (en) | Method, node and system for managing data for database cluster | |
| CN110647333A (en) | Firmware upgrading method and equipment configured to upgrade firmware therein | |
| CN113568566A (en) | Method, host device and storage server for seamless migration of simple storage service by using index object | |
| CN111651304B (en) | Software recovery method and device based on double-core intelligent ammeter and computer equipment | |
| CN106227620A (en) | Recoverable Flash data storage method | |
| CN114116305A (en) | BIOS firmware recovery method, system, terminal and storage medium based on PFR | |
| CN111475335B (en) | Method, system, terminal and storage medium for quickly recovering database | |
| CN116361817B (en) | Protection method of ubi file system under Linux | |
| CN106933604B (en) | System upgrading method and device | |
| CN111506450B (en) | Method, apparatus and computer program product for data processing | |
| US11740969B2 (en) | Detecting and recovering a corrupted non-volatile random-access memory | |
| CN115964204A (en) | File reading and writing method of embedded file system, electronic equipment and storage medium | |
| US11226875B2 (en) | System halt event recovery | |
| CN115878381A (en) | Data recovery method and device based on SRM disc, storage medium and electronic device | |
| CN114840362A (en) | Cloud host recovery method, device and medium | |
| CN115309336A (en) | Data writing method, cache information updating method and related device | |
| CN106547589A (en) | A kind of upgrade-system and upgrade method | |
| CN114968297A (en) | OTA (over the air) upgrading method, electronic equipment and chip system | |
| CN107357536B (en) | Data modification and writing method and system for distributed storage system | |
| CN110704085A (en) | RAID executable file updating method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination |