KR101461650B1 - Apparatus and method for managing file system of a computing device - Google Patents

Abstract

A file system management apparatus and method of a computing device is disclosed. A file system management apparatus according to an exemplary embodiment includes a detection unit for detecting an error occurring in a file system during booting of a computing device or an operation of a computing device to generate error information, a storage unit for storing error information received from the detection unit, A verification unit for checking whether there is error information in the storage unit at the time of booting of the computing device, and a recovery unit for correcting and restoring the error of the file system, if it is confirmed that the verification unit has stored the error information.

Description

[0001] The present invention relates to a file system management apparatus and method for a computing device,

The present invention relates to an apparatus and method for managing a file system of a computing device having a predetermined operating system (OS).

BACKGROUND OF THE INVENTION Conventional computing devices, such as desktop computers and laptop computers, as well as mobile computing devices such as smart phones and tablet computers, are made up of a variety of hardware and software. The hardware may include a central processing unit (CPU), an internal or external memory, a random access memory (RAM), a display, a camera, various sensors, an audio device, and an input / output device. The software includes an operating system (OS) program, a program for managing hardware including initialization, and an application program.

A file system collectively refers to a system for managing the memory (secondary storage) of such computing devices (including mobile computing devices) and the files (programs) stored therein. The file system may also be composed of predetermined files that are a collection of data. The type of the file system may vary depending on the type and version of the operating system (OS).

The file system basically performs functions such as access to the operating system (OS) file, connection of the internal hardware initialization file, connection of the external hardware initialization file, and connection of the application program file. Therefore, in order for the computing device to be normally booted after the power is applied, and thereafter the hardware and software must operate smoothly, it is essential that there is no error-free file system. If there is an error in the file system, the computing device can not normally perform the booting according to the contents of the error, or even if it is booted.

More specifically, in order to access a file necessary for its operation at the boot time of the computing device, a file system must be mounted. When the operating system (OS) is successfully loaded, the operating system (OS) necessary for the operation of the computing device is loaded using the operating system The connection to the related file must be made for the control of. In order for the device to boot normally, this process should be performed without any errors. If there is an error in the file system and a connection to a file necessary for such a booting process can not be made, the device may be reset due to the function of the corresponding file or the device may be reset The process will malfunction. Also, even after completing the booting, it is necessary to access a stored application file in order to execute a predetermined application by executing a predetermined application. If there is an error in the file system related to the application file, the application can not be executed, It may not be possible.

If the computing device fails to operate normally due to an error in the file system, the problem is solved by initializing the file system. In order to initialize the file system, the entire file system stored in the storage device must be deleted and a new file system must be downloaded and reinstalled. In particular, the deletion and reinstallation of such a file system is difficult for the user to carry out individually, which inconveniences the user from visiting the service center. In addition, there is a problem that user data is lost due to deletion of the existing file system and installation of the new file system (and / or replacement of the board for this purpose).

One problem to be solved by the present invention is to provide a file of a computing device that can automatically recover to a file system without errors when the computing device fails to boot due to an error in the file system, And a system management apparatus and method.

Another object of the present invention is to provide an apparatus and method for managing a file system of a computing device that can prevent user data from being lost even if a file system error is recovered.

According to an aspect of the present invention, there is provided an apparatus for managing file systems in a computing device, the apparatus comprising: a file system management unit configured to detect an error occurring in the file system during booting of the computing device or during operation of the computing device, A storage unit for storing the error information received from the detection unit, a confirmation unit for checking whether there is error information in the storage unit when the computing device is booted, and a confirmation unit for storing the error information And a restoring unit for correcting and restoring the error of the file system.

According to an embodiment of the present invention, the recovery unit may delete the error information stored in the storage unit when the file system is restored. At this time, the recovery unit may command the booting of the computing device.

According to another aspect of the present invention, the error information includes a flag field indicating whether there is an error in the file system, and the confirmation unit can determine whether there is an error by referring to the value of the flag field. In this case, the value of the flag field may be a value indicating whether there is an error in the file system or a value indicating that there is no error in the file system. Alternatively, the error information may further include an error type field indicating a type of the error, an error information field indicating a content of the error, and an error position field indicating a position where the error has occurred, The error can be corrected by referring to the information. In this case, the type of the error may include at least one of an error of the metadata of the file system, an error of the actual data, and a mismatching error of the metadata and the actual data.

According to still another aspect of the present invention, the recovery unit can correct an error of the file system by using the recovery program of the file system, and recover the error. In this case, if the file system is EXT-n, the recovery program is E2FSCK, and if the file system is a FAT (File Allocation Table), the recovery program may be FSCK.

According to another aspect of the present invention, there is provided a method of managing a file system of a computing device, the method comprising: a verification step of determining whether there is an error in a file system of the computing device when booting of the computing device; And a management step of correcting and recovering the error of the file system if the error is found in the checking step and proceeding the booting procedure of the computing device if it is confirmed that the error does not exist in the checking step.

According to an aspect of the embodiment, when the booting procedure of the computing device is performed in the management step, an error that occurs in the file system during the booting of the computing device or during the operation after the computing device finishes booting And a storage step of generating and storing error information on the detected error when an error is detected in the detecting step. At this time, in the checking step, the error information stored in the computing device may be referenced to determine whether there is an error in the file system of the computing device. The error information includes a flag field indicating whether there is an error in the file system, and in the checking step, it is possible to determine whether there is an error by referring to the value of the flag field. The value of the flag field may be a value indicating whether there is an error in the file system or a value indicating that there is no error in the file system. Alternatively, the error information may further include an error type field indicating a type of the error, an error information field indicating a content of the error, and an error position field indicating a position where the error has occurred, The error can be corrected and recovered by referring to the error information. At this time, the type of the error may include at least one of an error of the metadata of the file system, an error of the actual data, and a matching error of the metadata and the actual data.

According to another aspect of the present invention, in the management step, when the error of the file system is corrected and restored, the error information stored in the computing device can be deleted. The method may further include a booting step of booting the computing device after correcting an error of the file system in the management step and recovering the error. In this case, if the file system is EXT-n, it is restored using E2FSCK, and if the file system is a FAT (File Allocation Table), it can be restored using FSCK.

According to the embodiment of the present invention, when the computing device is booted, the stored error information is referenced to correct any errors in the file system, automatically restore the normal file system, and then reboot the computing device. At this time, the error of the file system can be corrected and recovered by using the program for restoring the file system. Therefore, even if there is an error in the file system, the user does not need to go to the service center, and there is no fear of losing user data.

1 is a block diagram illustrating a configuration of a file system management apparatus of a computing device according to an embodiment of the present invention.
2 is a diagram schematically showing the internal structure of the file system.
3 is a diagram schematically showing an example of a module structure of a file system capable of detecting an error of a file system based on the internal configuration of the file system of FIG.
4 is a block diagram showing an example of contents and format of error information.
5 is a flowchart illustrating a file system management method of a computing device according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. The terms used are terms selected in consideration of the functions in the embodiments, and the meaning of the terms may vary depending on the user, the intention or custom of the operator, and the like. Therefore, the meaning of the terms used in the following embodiments is defined according to the definition when specifically defined in this specification, and unless otherwise defined, it should be interpreted in a sense generally recognized by those skilled in the art.

The management technique of the file system according to the embodiment of the present invention described later can be applied to a computing device. The computing device may be, but is not limited to, a mobile computing device such as a smart phone or tablet computer. The computing device includes various software such as an operating system (OS) program, a program for managing hardware including initialization, an application program, and the like as well as various hardware including a central processing unit (CPU).

The computing device is provided with a file system as a means for systematically managing files constituting programs stored in a memory and providing access information therefor. Although the structure and format of the file system may vary depending on the operating system (OS), the basic role of the file system is the same. A file system typically performs functions such as accessing an operating system (OS) file, accessing an internal hardware initialization file, connecting an external hardware initialization file, and connecting an application program file.

In addition, there is a recovery program in the file system that can correct the error and restore it to a normal file system. For example, in the case of the EXT-n file system, the recovery program is E2FSCK, and in the case of the FAT (File Allocation Table) file system, the recovery program is FSCK. In the method of managing a file system according to an embodiment of the present invention to be described later, if there is an error in the file system, the recovery program can be driven to remove errors in the file system and restore the file system to a normal file system.

1 is a block diagram illustrating a configuration of a file system management apparatus of a computing device according to an embodiment of the present invention. 1, the file system management apparatus 1 includes a restoring unit 10, a checking unit 20, a detecting unit 30, and a storage unit 40 . The components of the management apparatus 1 of the file system shown in Fig. 1 are logically divided according to functions only. Therefore, two or more components constituting the management apparatus 1 may be physically integrated into one unit, or one unit may be implemented as an aggregate of a plurality of subunits.

The file system management device 1 is for recovering the file system automatically when an error occurs in the file system. A faulty file system can be recovered normally by repairing the error through its own error recovery program and replacing it with a normally recovered or error-free file system. To this end, the management apparatus 1 of the file system detects an error in the file system and stores the detected error information in the case where the computing device does not properly boot due to an error of the file system, . The file system management apparatus 1 first checks whether there is an error in the file system based on the error information stored when the computing device is booted. If it is determined that there is an error in the file system, By recovering the file system by healing the error, the computing device is normally booted and can operate normally. Hereinafter, this will be described in more detail with reference to Fig.

The detection unit 30 detects an error occurring in the file system during booting or operation of the computing device and grasps the content of the error. In general, when an error occurs in the file system, the computing device fails to boot or fails to perform the normal operation and reboots. The detecting unit 30 detects an error in the file system in such a situation, As shown in FIG. At this time, the detection unit 30 can recognize as to the error contents which partitions of the file system and / or which blocks have an error, what kind of error, what kind of error, and so on. The detecting unit 30 generates error information including the detected error of the file system and transmits the error information to the storage unit 40.

According to an aspect of this embodiment, the error content of the file system recognized by the detection unit 30 can be grasped based on the internal structure of the file system. 2 is a diagram schematically showing the internal structure of the file system. Referring to FIG. 2, the file system may be divided into a meta region and a data region. The meta area is an area for storing file system meta data for managing data included in a data area, and the data area is an area for storing file system body data. The file system metadata includes information of a predefined file system and usage information for managing the data area. The usage information is linked one to one with actual data of the data area. Table 1 below shows an example of a part of the file system metadata stored in the meta area. The file system actual data includes information related to the contents of the file as well as directory information in which the file is stored.

Types of metadata Explanation Block Basic unit to store data Block Group Store information and data in the file system Super Block Main configuration information of file system is saved Group Descriptor Table Save information about Block Group Block Bitmap Save usage information of block Inode The file system's file object is stored Inode Bitmap Store usage information of Inode Inode Table Determine which Inode is assigned

The meta area and the data area of this file system are closely linked, and all errors in the file system are caused by errors in these meta areas and data areas. That is, there are three types of errors in the file system, that is, errors in the file system metadata itself, errors in the file system actual data itself, and mutual matching errors between the file system metadata and the file system actual data. Therefore, when there is an error in the file system, the detecting unit 30 can judge whether this error is an error of the metadata itself, an error of the actual data itself, and / or an error of mutual matching of the metadata and actual data have.

3 is a diagram schematically showing an example of a module structure of a file system in which the detection unit 30 can detect an error based on the internal configuration of the file system of Fig. Referring to FIG. 3, the file system includes a registration module 52 and an input / output module 54. The registration module 52 is for registering the first file system so as to grasp whether the integrity is internal or not. The input / output module 54 is for processing a connection to a file necessary for the operation of the computing device, that is, a file stored in a predetermined directory of the storage module 60.

In the module structure of the file system shown in FIG. 3, an error of the metadata can be detected by the detecting unit 30 through the registration module 52. More specifically, based on the file system registered in the registration module 52, the detecting unit 30 determines whether there is an error in the file system used at the booting, or the use information of the metadata indicating the information of the actual data, Such as whether the information in the previously defined file system is inconsistent to manage the file system.

In the module structure of the file system shown in FIG. 3, an error of actual data can be detected by the detection unit 30 through the input / output module 54 after the integrity of the file system is verified by the registration module 52. More specifically, the detection unit 30 can detect whether there is an error in the actual data by monitoring whether or not the connection to the file stored in the storage module 60 is normally performed by the input / output module 54. If an access to an erroneous file is made by the input / output module 54, the detection unit 30 may determine that there is an error in the actual data providing the access information for the file.

In addition, in the module structure of the file system shown in FIG. 3, the matching error between the meta data and the actual data can be detected by the detection unit 30 through the registration module 52 and the input / output module 54. A mutual match error corresponds to a case where the metadata of the file system does not match the actual data. For example, the metadata representing the information of the data to be written at the time of writing data is written in the metadata area of the file system, but the actual data of the data written due to the momentary power-off or reset, In this case, the detecting unit 30 may determine that there is a mutual matching error through the registration module 52 and the input / output module 54 .

1, the storage unit 40 writes error information received from the detection unit 30 into a memory and stores the information. The type of the memory in which the error information is stored is not particularly limited, and may be stored in, for example, a RAM or a flash memory provided in a computing device, or a rewritable ROM. The error information is preferably stored in a predetermined area defined in advance in the memory.

The error information stored in the storage unit 40 notifies the confirmation unit 20 that there is at least an error in the file system. In addition, the error information can also provide the recovery unit 10 with information necessary for the recovery program to recover the error in the file system. Therefore, the error information should include at least the information necessary to perform this role. For example, the error information may include information about which partitions of the file system and / or which blocks have failed, what kind of error is, what the error is, and so on. There is no particular limitation on the format of the error information, and the format of error information may vary depending on the type of the file system.

4 is a block diagram showing an example of the content and format of error information stored in the storage unit 40. As shown in FIG. Referring to FIG. 4, the error information 70 includes a flag field 72, an error type field 74, an error information field 76, field, 78). In Table 2, explanations and size of each field constituting the error information 70 are illustratively shown.

Field Descriptions Size Flag 0: normal, 1: error 1 byte Error Type The type of error (e.g., metadata error, actual data error, inter-matching error) 1 byte Error Info. Detailed information about each error type 16 bytes Error Location Location with errors 4Byte

Referring to FIG. 4 and Table 2, information indicating whether or not an error exists in the file system may be written in the flag field 72. FIG. For example, if there is no error in the file system, '0' is displayed in the flag field 72, and '1' may be displayed if there is an error in the file system. By using the data displayed in the flag field 72, the checking unit 20 can easily check whether or not there is an error in the file system.

In the error type field 74, information indicating the type of error can be written. If there are a plurality of errors in the file system, the error type field 74 may be filled with information indicating each type. For example, the type of error can indicate whether it is an error in the metadata, an error in the actual data, or an error in matching the metadata with the actual data. In the error information field 76, detailed information on each of the error types written in the error type field 74 can be written. In the error position field 78, the position of the errored file system, that is, Or information indicating the position of the block can be written.

1, the verification unit 20 confirms whether there is an error in the file system at the time of booting or rebooting the computing device. According to the embodiment of the present invention, the confirmation unit 20 does not directly check the existence of an error by directly examining the file system, and communicates with the storage unit 40 to check whether or not there is an error in the file system in advance have. More specifically, the verification unit 20 can confirm the presence or absence of an error in the file system by referring to the information of the flag field in the error information having the format shown in Fig. 4 more specifically than the error information stored in the storage unit 40 .

If it is confirmed that the file system has no error, the booting or rebooting can be normally performed and the booting is completed and the computing device can normally operate. In this case, as described above, the detection unit 30 continuously monitors whether or not an error occurs in the file system during the booting process or the operation process of the computing device. If the error of the file system is detected, error information is generated To the storage unit 40. On the other hand, if it is confirmed that the file system has an error as a result of the confirmation by the verification unit 20, booting can not proceed normally and a process of healing an error of the file system proceeds.

When there is an error in the file system as a result of the confirmation by the confirmation unit 20, the recovery unit 10 heals the error of the file system and restores the file system to a normal state. At this time, the recovery unit 10 can partially restore the file system or recover the file system as a whole. There is no particular limitation on the specific method by which the restoring unit 10 restores the file system in this embodiment. For example, the recovery unit 10 can recover a file system in error by using a program for recovery of the file system. Alternatively, the recovery unit 10 may drive another file system recovery means provided in the computing device to recover a file system with an error.

When the restoring unit 10 restores the file system, it may refer to the error information stored in the storage unit 40. More specifically, the recovery unit 10 refers to the location information, the error type information, and / or the error information included in the error information to determine where the error is and also what error, You can heal. If the error of the file system is recovered by the recovery unit 10 and restored to the normal file system, the computing device can be booted again.

The recovery unit 10 may delete the error information stored in the storage unit 40 when the file system is normally restored. For example, the recovery unit 10 may transmit a deletion request signal of the error information to the storage unit 40, and the storage unit 40 may delete the error information according to the deletion request signal. This is to indicate that there is no error in the file system in the confirmation process by the confirmation unit 20 when the file system is normally restored by the recovery unit 10 and the computing device is rebooted.

As described above, the file system management apparatus according to the embodiment of the present invention monitors whether there is an error in the file system during the booting of the computing device or during normal operation, and records the error information when the error of the file system is detected do. Then, the file system management device checks whether there is an error in the file system at the time of booting the computing device by using the stored error information. If there is an error in the file system, the file system management device heals it and automatically restores it to the normal file system Reboot the computing device.

5 is a flowchart illustrating a file system management method of a computing device according to an embodiment of the present invention. The file system management method illustrated in FIG. 5 may be implemented using the file system management described above with reference to FIGS. Therefore, the file system management method will be briefly described in this embodiment, and the matters described above with reference to FIG. 1 to FIG. 4 can be equally applied to matters not specifically described here.

Referring to FIG. 5, booting of the computing device is initiated (101). In this embodiment, there is no particular limitation as to why the computing device is booted. For example, the computing device may be booted by the user's intention or may be booted by its own mechanism of the computing device. In this case, the computing device may be booted after a previously successful termination, or may be rebooted after a previous problem has been forcibly shut down.

When booting is started, it is checked whether there is an error in the file system (S102). In the present embodiment, there is no particular limitation on a method for confirming the presence or absence of error in the file system. In the case of the file system management apparatus 1 (see Fig. 1), the confirmation unit 20 can check whether the error information is stored in the storage unit 40, thereby confirming the error condition. In addition, any method can be used in this step (S102) if it is possible to confirm that the file system previously had an error and that the computing device has not booted normally or has not operated normally after booting.

If it is determined in step S102 that there is no error in the file system, the computing device normally proceeds with the booting process, and when the booting is completed, the computing device normally performs operation (S103). At this time, during booting or during normal operation, the computing device determines whether an error in the file system is detected (S104). For example, the computing device can detect an error in the file system by monitoring whether the boot normally proceeds due to an error in the file system or if there is a problem in the operation due to an error in the file system.

If it is determined in step S104 that no error in the file system is detected, the procedure ends. On the other hand, if it is determined in step S104 that an error in the file system is detected, error information on the file system is generated and stored (S105). The errors of the file system can be roughly classified into three kinds of errors: errors of the file system metadata itself, errors of the file system real data itself, and mutual matching errors of the file system metadata and the file system actual data, . The error information of the file system may vary depending on the type of the operating system of the computing device, but there is no particular limitation on the format. However, the error information of the file system may include information such as which partition of the file system and / or which block has caused the error, what kind of error, and what the error is.

When the error information of the file system is stored, the rebooting process of the computing device is restarted, and the process of step S101 and subsequent steps is repeatedly performed. The error information stored in step S105 may be used in the process of checking whether the error information exists in step S102 have. That is, if the process after step S101 is performed again after step S105, it is determined that error information of the file system exists in step S102, and the process proceeds to step S106.

If it is determined in step S102 that there is an error in the file system, the process of correcting the error in the file system and restoring the normal file system is performed (S106). Errors in the file system can be corrected using an error recovery program included in the file system or can be corrected using other means. At this time, the file system may partially recover from the error only part, or the entire file system may be replaced with the new file system. In the case of restoring the file system, the error information of the file system stored in step S105 may be deleted in step S106.

The above description is only an example of the present invention, and the technical idea of the present invention should not be interpreted as being limited by this embodiment. The technical idea of the present invention should be specified only by the invention described in the claims. Therefore, it is apparent to those skilled in the art that the above-described embodiments may be modified and embodied in various forms without departing from the technical spirit of the present invention.

1: File system management device
10:
20:
30:
40:
52: Registration module
54: I / O module
60: storage module

Claims (20)

A detecting unit for detecting an error occurring in the file system during booting of the computing device or during operation of the computing device to generate error information;
A storage unit for storing the error information received from the detection unit;
A confirmation unit for checking whether there is error information in the storage unit when the computing device is booted; And
And a recovery unit for correcting and recovering an error of the file system when the confirmation unit confirms that the error information is stored. The method according to claim 1,
Wherein the recovery unit deletes the error information stored in the storage unit when the file system is restored. 3. The method of claim 2,
Wherein the recovery unit instructs booting of the computing device. The method according to claim 1,
Wherein the error information includes a flag field indicating whether there is an error in the file system,
Wherein the checking unit determines whether there is an error by referring to the value of the flag field. 5. The method of claim 4,
Wherein the value of the flag field is a value indicating whether there is an error in the file system and a value indicating that there is no error in the file system. 5. The method of claim 4,
Wherein the error information further includes an error type field indicating a type of the error, an error information field indicating a content of the error, and an error position field indicating a position where the error occurs,
Wherein the recovery unit corrects the error by referring to the error information. The method according to claim 6,
Wherein the type of the error is at least one of an error of the metadata of the file system, an error of actual data, and an error of mutual matching of the metadata and the actual data. The method according to claim 1,
Wherein the recovery unit corrects an error of the file system using a program for restoring the file system. 9. The method of claim 8,
Wherein the recovery program is E2FSCK when the file system is EXT-n, and the recovery program is FSCK when the file system is a FAT (File Allocation Table). A verification step of, when the booting of the computing device is started, determining whether there is an error in the file system of the computing device; And
And a management step of correcting and recovering the error of the file system if the error is found in the checking step and proceeding to booting the computing device if it is confirmed that the error does not exist in the checking step,
If the booting procedure of the computing device is performed in the management step,
A detecting step of detecting an error occurring in the file system during a booting of the computing device or during an operation after the computing device has completed booting; And
Further comprising a storing step of generating and storing error information on the detected error when an error is detected in the detecting step,
Wherein the determining step determines whether there is an error in the file system of the computing device by referring to the error information stored in the computing device. delete delete 11. The method of claim 10,
Wherein the error information includes a flag field indicating whether there is an error in the file system,
Wherein the checking step determines whether there is an error by referring to the value of the flag field. 14. The method of claim 13,
Wherein the value of the flag field is a value indicating whether there is an error in the file system or a value indicating that there is no error in the file system. 14. The method of claim 13,
Wherein the error information further includes an error type field indicating a type of the error, an error information field indicating a content of the error, and an error position field indicating a position where the error occurs,
And in the management step, the error is corrected by referring to the error information. 16. The method of claim 15,
Wherein the type of the error is at least one of an error of the metadata of the file system, an error of the actual data, and a matching error of the metadata and the actual data. 11. The method of claim 10,
And the error information stored in the computing device is deleted when the error of the file system is corrected and restored in the managing step. 18. The method of claim 17,
Further comprising a booting step of booting the computing device after correcting the error of the file system in the management step and recovering the error. 18. The method of claim 17,
Wherein the file system is restored by using E2FSCK when the file system is EXT-n, and is restored by using FSCK when the file system is a FAT (File Allocation Table). A computing device comprising a file system management device as recited in any one of claims 1 to 9.

Images