TWI687803B - Computer system and fault tolerance processing method of image file - Google Patents

Abstract

A computer system and a fault tolerance processing method of image file are provided. In the method, whether to divide image file(s) is determined. The image file is segment-divided in order and a division history is recorded. The division history relates to a last dividing number, which is accumulated whenever the image file is divided once. In response to a division exception situation, the division of the image file could be continued according to the division history. In addition, image segment files are segment-recovered in order and a recovery history is recorded. The recovery history relates to a last recovering number, which is accumulated whenever one image segment file is recovered. In response to a recovery exception situation, the recovery of the image segment files could be continued according to the recovery history.

Description

Computer system and fault-tolerant processing method of image file

The invention relates to a method for processing image files, and in particular to a computer system and a method for processing fault tolerance of image files.

Computer systems (for example, desktop computers, notebook computers, All-in-One (AIO), etc.) are already one of the tools commonly used by people in work, entertainment, leisure, and even daily life. Inevitably, the computer system may encounter abnormal conditions such as system errors, update failures, driver conflicts, and malware attacks. Some users will restore the operating system (Operating System, OS), hard disk volume, or files in the computer system to restore the computer system to its previous normal state. However, the recovery operation of the computer system is not 100% successful. Occasionally, the operating system itself, hardware-related problems, or user improper operation (for example, the user kicks the computer system power supply, the battery loses power, etc.) Cause the restore to be interrupted). And because there is no recovery remedy at present, when the user encounters the recovery failure, usually The equipment will still be handed over to the repair center. However, the repair process for restoration failure is complicated, which leads to expensive repair costs, and the computer system may not be repaired and needs to be returned.

In view of this, the present invention provides a computer system and a fault-tolerant processing method of an image file, which can ensure that the image file is segmented to restore the image file after the image file is cut into image files, regardless of whether the computer system is abnormal or not, thereby improving the image file recovery Efficiency and success rate.

The fault-tolerant processing method of the image file of the present invention includes the following steps. Determine whether to cut the image file. If it is decided to cut the image file, the image file is cut sequentially and the cutting history is recorded. The cutting process is related to the number of last cuts. The number of last cuts is accumulated once per image file. In addition, in response to the abnormal cutting situation, the cutting image file is continued according to the cutting process.

The computer system of the present invention includes a storage and a processor. The storage records image files and several modules. The processor is coupled to the memory, and accesses and loads those modules recorded in the memory. And those modules include segmentation modules. This segmentation module determines whether to cut the image file. If it is decided to cut the image file, the segmentation module sequentially cuts the image file in segments and records the cutting history. In response to the abnormal cutting situation, the segmentation module continues to cut the image file according to the cutting process. The cutting process is related to the last cutting number, and the last cutting number is accumulated once for each pair of image files.

Based on the above, the fault tolerance of the computer system and the image file according to the embodiment of the invention The method is to cut the image file into several image files or confirm it as an image file before restoring the image file. During the cutting process, the computer system will record the cutting process, so that the cutting operation can still be continued after abnormal cutting occurs. On the other hand, the embodiment of the present invention is to restore the image bulk in stages. If any abnormality in the computer system unfortunately occurs during the restoration process, the computer system can continue the restoration. Compared with restoring a single image file, when the fault tolerance mechanism of the embodiment of the present invention encounters any abnormal situation, the restoration operation does not need to be restarted, which significantly improves efficiency and success rate, so that the public can easily cope with the abnormal situation.

In order to make the above-mentioned features and advantages of the present invention more obvious and understandable, the embodiments are specifically described below in conjunction with the accompanying drawings for detailed description as follows.

1: Computer system

110: storage

111: Restore interface module

112: Split module

113: Segmented Restore Module

114: Log

115: counter

S210~S250, S310~S350: Steps

FIG. 1 is a block diagram of components of a computer system according to an embodiment of the invention.

FIG. 2 is a flowchart of a cutting-out stage of a fault-tolerant processing method for image files according to an embodiment of the present invention.

FIG. 3 is a flowchart of the restoration process of the image file fault-tolerant processing method according to an embodiment of the present invention.

FIG. 1 is a block diagram of components of a computer system 1 according to an embodiment of the invention. Please refer to FIG. 1, the computer system 1 includes at least but not limited to the storage 110 and its location 理器150。 150. The computer system 1 may be an electronic device such as a desktop computer, a notebook computer, a server, an All-in-One (AIO), a smart phone, and a tablet computer.

The memory 110 may be any type of fixed or removable random access memory (RAM), read-only memory (ROM), flash memory (Flash memory), or the like Or a combination of the above components, the storage 110 is used to store buffered or permanent data, software modules (restore interface module 111, partition module 112, segment restore module 113, counter 115, etc.), logs 114. Image files, image files, cutting history, segmented restoration history and other data, and the detailed content thereof will be described in detail in subsequent embodiments.

The processor 150 is coupled to the storage 110, and may be a central processing unit (CPU), or other programmable general-purpose or special-purpose microprocessor (Microprocessor), digital signal processor (DSP), programmable Controller, application specific integrated circuit (ASIC) or other similar components or a combination of the above components. In the embodiment of the present invention, the processor 150 is used to execute all operations of the computer system 1, and can be loaded and executed (for example, through an application programming interface (API) or function call, etc.) in the storage 110 Recorded software modules, files and data.

In order to facilitate understanding of the operation flow of the embodiment of the present invention, a number of embodiments will be given below to describe in detail the processing flow of the image file by the computer system 1 in the embodiment of the present invention. In the following, the methods described in the embodiments of the present invention will be described with various components and modules of the computer system 1. The various processes of the method can be adjusted according to the implementation situation, and it is not limited to this.

FIG. 2 is a flowchart illustrating a fault-tolerant processing method of image file-segmentation stage according to an embodiment of the invention. Referring to FIG. 2, the restoration interface module 111 presents the restoration interface through the display of the computer system 1 (for example, a liquid crystal display (LCD), a light emitting diode (LED) display, etc.). The restoration interface is, for example, a restoration function integrated into an operating system (OS) (for example, Windows, Mac OS, Linux, etc.), or belongs to an independent application, and provides such as restoration startup and suspension operation reception, information presentation, etc. Features. When the restoration interface module 111 receives the user's operation of restoration activation on the restoration interface through the input device (for example, keyboard, mouse, touch screen, etc.), the restoration interface module 111 triggers the fault tolerance mechanism of the embodiment of the present invention .

This fault-tolerant mechanism will access and communicate with the recovery function of the operating system and the recovery partition in the hard disk. Specifically, the processor 150 will copy the bootloader (bootloader) and other system startup related files (for example, boot configuration data (Boot Configuration Data, BCD) files, boot manager, etc.) to the restore of the storage 110 Partition (that is, the partition that stores the image file for restoration), and instructs to enter this restoration partition after rebooting, and records the storage path of the system startup related files. It should be noted that in other embodiments, these system startup related files may also be stored in other partitions of the storage 110, as long as the storage paths of these files are recorded and available for access.

Next, the segmentation module 112 checks whether the type of the image file used for restoration is a single image file to determine whether to cut the image file (step S210). It is worth noting that a single image file is composed of several image files. In order for the fault-tolerance mechanism of the embodiment of the present invention to run smoothly in stages, the subsequent image files for restoration need to be Cut into image files. In other words, the segmentation module 112 checks whether the image file stored in the storage 110 is an image file. In this embodiment, the segmentation module 112 determines whether these image files are image bulk files according to at least one of the number, name relationship, and size of the image files stored in the storage 110. For example, the segmentation module 112 sequentially determines whether the number of these image files exceeds one, whether the name relationship has a sequential relationship (for example, numerical order (for example, ending in 111, 112, 113...), and alphabetical order (for example, for ending (A, b, c...) relationship, etc.), and determine whether the file size of each image file is less than or equal to the maximum bulk value (for example, 50, 60, 100 megabytes (MB), etc.). As long as the number, name relationship and size of the image files do not meet any of the above conditions, the segmentation module 112 determines that the image file is not an image file (may be a single image file, an image file with an inconsistent size) and decides on the image File cutting.

It should be noted that the aforementioned number, name relationship and size are based on the general image file splitting program's setting rules for image bulk, but different image file splitting programs may also have other setting rules. The embodiments of the present invention do not use the aforementioned setting rules To limit, and can be adjusted according to the setting rules of other image file division programs. In addition, the order of judging the number, the relationship of names and the size is not limited to the foregoing examples, and the users can adjust or increase or decrease the conditions according to their needs.

When it is decided to cut the image file, the partitioning module 112 can shrink the remaining space of the restored partition in the storage 110 to store the image bulk file obtained by subsequent cutting. It should be noted that, in other embodiments, the partition module 112 may also first determine whether the remaining space is greater than or equal to the size of the image file; if the conditions are met, the partition module 112 may omit the step of compressing the space, that is, restore the partition Available for not yet cut The image file and the resulting image image are stored in bulk (approximately twice the size of the image file); otherwise, the segmentation module 112 requires compressed space.

For example, Table (1) is an example of disk partitions. The recovery partition for image files used for restoration is usually planned on the last disk partition (fifth partition) (Partition boot record (PBR) may also record downgrade right recovery partition). If necessary, the processor 150 will increase the space of the recovery partition through the compression function to use unused disk space.

If the storage 110, the recovery partition, or other disk partitions have enough space to store the cut image bins, the split module 112 will perform a sequential split map Image file and record the cutting history (step S230). Specifically, during the file cutting process, the processor 150 will record through the counter 115 which image partition is currently cut, where the counter 115 will accumulate the last number of cuts for each pair of image files. For example, if the dividing module 112 cuts for the third time, the counter 115 records the number of the last cut as three. The segmentation module 112 will use this last number of cuts as the cutting history, and record the cutting history in the log 114. In addition, the segmentation module 112 also writes the image file to the log 114 at the starting address of the storage 110.

Then, in response to the abnormal cutting situation (for example, a failure exception issued by the OS or the program, a power interruption, etc.), the segmentation module 112 may continue to cut the image file according to the cutting process (step S250). In this embodiment, the dividing module 112 will determine the subsequent cutting address based on the last number of cuts recorded in the log 114 and the starting address of the image file (physical address in the disk). This continuous cutting address is based on formula 1: SA=IMG_Init_Address+[Counter*(ImageTotalSize/DF)]*1024*1024*8... (1) SA is the continuous cutting address, and IMG_Init_Address is the physical start bit of the image file Address, Counter is the last number of cuts, ImageTotalSize is the size of the image file, DF is the total number of cuts (ie, the total number of image files being cut). The dividing module 112 can cut the uncut image file according to the continuous cutting address.

Assume that the starting address of the image file is 2500, the size of the image file is 10 gigabytes (Gigabytes, GBs), the total number of cuts is 200, and the process is aborted when cutting to the 85th file (ie, the last number of cuts) Is 85). The segmentation module 112 brings the formula 1, 2500+[85*(10000MB/200)]*1024*1024*8, so as to know the next time from the entity The address 35651586500 starts image file cutting.

Since the embodiment of the present invention adopts the segmented cutting method, after the cutting abnormality occurs, the segmentation module 112 continues to cut the physical address processed at the time when the cutting abnormality occurs, and the image scattered files that have been cut will continue to remain in In the storage 110, the processor 150 does not need to cut the image file again.

It should be noted that the aforementioned continuous cutting address can be calculated after each cutting is completed, or it may be calculated in response to abnormal cutting conditions. In addition, in some embodiments, for some image files with inconsistent sizes but belonging to the same image file, the processor 150 may first combine the image files into a single image file, and then cut the single image file through the splitting module 112.

On the other hand, the prior art usually cuts the image file with a fixed file size, resulting in the file size of a certain image file being different from other image files, which in turn affects subsequent restoration operations. In order to make the size of the image files consistent, the segmentation module 112 of the embodiment of the present invention first initializes the total number of cuts (for example, 50, 100, 200, etc.), and calculates the size of each image file based on the total number of cuts. The size of this image file is based on formula 2: Split_Size=Image_Size/DF... (2) Split_Size is the size of the image file, Image_Size is the size of the image file, and DF is the total number of cuts. The segmentation module 112 then determines whether the size of the image bin is greater than the maximum bin value (eg, 50, 80, 150MB, etc.). If the size of the image file is greater than this maximum file value, the segmentation module 112 will increase the total number of cuts (eg, increase by 50, 100, 150, etc.) and recalculate the size of the image file. If the size of the image file is not greater than With this maximum bin value, the segmentation module 112 sequentially cuts the image file segment by segment according to the size of the image bin.

For example, if the segmentation module 112 calculates that the size of the image bulk exceeds 50MB (ie, the maximum value of the bulk), add 100 to the DF variable (ie, the total number of cuts), and then recalculate the size of the image bulk until the image is scattered The file size is less than or equal to 50MB. Assuming that the restored image file in the restored partition is 8452MB, the total number of cuts DF=200 can be obtained by entering formula 2, which is because 8452/100, the size of the resulting image split Split_Size is greater than 50MB; and 8452/200, the derived The size of the image bulk Splize_Size is 42.26MB.

It should be noted that the maximum bin value used here is the same as the maximum bin value of the aforementioned determination whether it is a single image file, but in other embodiments, the two values may also be different. In addition, the total number of cuts used in Equation 2 can be used in Equation 1.

In addition, in an embodiment, in order to effectively use the space, when the segmentation stage is completed (that is, the number of last cuts equals the total number of cuts), the splitting module 112 may delete the original image file. However, in other embodiments, the segmentation module 112 may also retain this image file.

If the segmentation phase is completed or after step S210, it is decided not to cut the image files (ie, the number, name relationship and size of these image files meet the conditions, and these image files are regarded as image files), please refer to FIG. 3 According to an embodiment of the present invention, a fault-tolerant processing method for image files-a flowchart of the restoration stage, the segment restoration module 113 sequentially restores the image files in stages and records the stage restoration history (step S310). Specifically, during the restoration of the image file, the processor 150 records the restoration to the counter 115 through the counter 115. Which image bin is restored for each of these pair of image bins, the counter 115 will accumulate the last number of restores. For example, if the segment restoration module 113 restores the fifth image file, the counter 115 records that the last restoration number is five. The segment restoration module 113 will use the last restored number as the segment restoration history, and record the segment restoration history in the log 114.

Then, in response to the restoration abnormality (for example, a failure exception issued by the OS or the program, a power interruption, etc.), the segment restoration module 113 may successively restore the unrestored image bin according to the segment restoration process (step S350) . In this embodiment, the last restored number represents the number of sorted image bins that have been successfully restored, and the segmentation restore module 113 only needs to continue to sort the last one (ie, the order is the last restored number plus one). Just restore, no need to restore from the first image bulk again.

It should be noted that, in some embodiments, the processor 150 may determine the name of each image file according to the cutting order of the segmentation stage, so as to facilitate the ordering of the restoration order in the staged restoration stage, or the processor 150 may use the index or The parameter records the order of each image file and is accessed by the segment restoration module 113.

Table (2) is an experimental comparison of the embodiments of the present invention. Taking an 8GB image file as an example, the file splitting time (ie, the processing time of the splitting stage) takes less than one-half of the restoration time, and the normal processing time for determining the restoration partition path and restoration execution does not exceed 3 seconds.

When a problem occurs during the restoration process, the recovery time is introduced into the comparison table (3) before and after the embodiment of the present invention as follows. During the restoration of the image file, the disk will be formatted first, and then the image file will be installed on the disk. Therefore, before importing the embodiment of the present invention (ie, the prior art), if the restoration process is aborted, the image file must be reinstalled, which may take time to include the deployment of hard files such as copying the image file, loading the image file, and customizing the OS Time, so it takes a long time. After the embodiment of the present invention is introduced, the restoration process is suspended, and the time consumption is much shorter. Taking the hardware architecture of an A-brand CPU and a traditional hard disk as an example, if the restoration is aborted to 60%, the repair takes 37-37*0.6=14.8 minutes.

Based on the experimental results of the above two, the introduction of this embodiment increases the splitting time compared to the prior art, but when an abnormal situation occurs during the restoration process, since the image file does not need to be redeployed, the repair time is significantly shortened.

In summary, the computer system and the fault-tolerant processing method of the image file according to the embodiments of the present invention use segmented cutting and restoration processing on the image file, and record the history of the cutting and restoration process, so that any abnormal situation occurs. It can continue to perform cutting and restoration operations, significantly improving the restoration efficiency and success rate. In addition, the size of the image after the file is cut is the same, so that the subsequent restoration operation can be carried out smoothly.

Although the present invention has been disclosed as above with examples, it is not intended to limit the present invention. Any person with ordinary knowledge in the technical field can make some changes and modifications without departing from the spirit and scope of the present invention. The scope of protection of the present invention shall be subject to the scope defined in the appended patent application.

S210~S250: Steps

Claims (10)

A fault-tolerant processing method for image files, comprising: determining whether to cut at least one image file; if it is decided to cut the at least one image file, sequentially cutting the at least one image file in sections and recording a cutting history, wherein the cutting history is related In a final cut number, the last cut number is accumulated every time the at least one image file is cut; and in response to an abnormal cutting condition, the at least one image file is continuously cut according to the cutting process. The fault-tolerant processing method for image files as described in item 1 of the patent application scope, wherein the step of successively cutting the at least one image file according to the cutting process includes: based on the number of the last cut and the starting address of the at least one image file Determining a continuous cutting address; and cutting the at least one image file that has not been cut according to the continuous cutting address. The fault-tolerant processing method for image files as described in item 1 of the patent application scope, wherein the step of judging whether to cut the at least one image file includes: judging the at least one of the number, name relationship and size of the at least one image file Whether at least one image file is at least one image file, wherein part or all of the at least one image file constitutes a single image file; and if the at least one image file is not the at least one image file, the One image file is cut. The fault-tolerant processing method for image files as described in item 1 of the patent application scope, wherein after determining the step of cutting the at least one image file, the method further includes: calculating the size of at least one image file based on a total number of cuts, wherein the at least one The image files constitute the at least one image file; determine whether the size of the at least one image file is greater than a maximum file value; if the size of the at least one image file is greater than the maximum file value, increase the total number of cuts and restart Calculating the size of the at least one image file; and if the size of the at least one image file is not greater than the maximum file value, then the at least one image file is sequentially segmented according to the size of the at least one image file. The fault-tolerant processing method of the image file as described in item 1 of the patent application scope, wherein before the step of cutting the at least one image file is determined, the method further includes: compressing the remaining space for storing at least one image file, wherein the at least one The image file is obtained by cutting the at least one image file. The fault-tolerant processing method of the image file as described in item 1 of the patent application scope, wherein after the step of determining whether to cut the at least one image file, the method further includes: if it is decided not to cut the at least one image file, then the at least one image file It is regarded as at least one image file, and the at least one image file is restored sequentially and a segment restoration process is recorded, wherein the segment restoration process is related to a last restoration number, and the last restoration number is every Restore and accumulate one of the at least one image file; and in response to a restore abnormal situation, restore the at least one image file that has not been restored successively according to the last restored number. A computer system includes: a storage, recording at least one image file, and multiple modules; and a processor, coupled to the storage, and accessing and loading the modules recorded in the storage, The modules include: a segmentation module to determine whether to cut the at least one image file, and if it is decided to cut the at least one image file, sequentially cut the at least one image file in sections and record a cutting history, and react In an abnormal cutting situation, the at least one image file is successively cut according to the cutting history, wherein the cutting history is related to a number of last cuts, and the number of last cuts is accumulated every time the at least one image file is cut. The computer system as described in item 7 of the patent application scope, wherein the segmentation module determines a continuous cutting address based on the number of the last cut and the starting address of the at least one image file, and cuts according to the continuous cutting address The at least one image file that has not been cut. The computer system as recited in item 7 of the patent application scope, wherein the segmentation module determines whether the at least one image file is at least one image bulk based on at least one of the number, name relationship, and size of the at least one image file, Part or all of the at least one image file constitutes a single image file, if the at least one image file is not the at least one image file, the segmentation module decides to cut the at least one image file, if the at least one If the image file is the at least one image file, the partition module decides not to cut the at least one image file, and the modules further include: a segment restoration module, if the partition module decides not to at least one image File cutting, the segment restoration module sequentially restores the at least one image bulk and records a segment restoration history, wherein the segment restoration history is related to a last restoration number, and the last restoration number is Each time one of the at least one image file is restored and accumulated, the segmented restore module reacts to a restore abnormal condition, and restores the at least one image file that has not been restored successively according to the last restored number. The computer system according to item 7 of the patent application scope, wherein the segmentation module calculates the size of at least one image file based on a total number of cuts, wherein the at least one image file constitutes the at least one image file, and the segmentation module determines Whether the size of the at least one image bin is greater than a maximum bin value, if the size of the at least one image bin is greater than the maximum bin value, the segmentation module increases the total number of cuts and recalculates the at least one image bin The size of the at least one image file, if the size of the at least one image file is not greater than the maximum file value, the segmentation module sequentially cuts the at least one image file according to the size of the at least one image file.

Images