CN105302924A - File management method and device - Google Patents
File management method and device Download PDFInfo
- Publication number
- CN105302924A CN105302924A CN201510907216.0A CN201510907216A CN105302924A CN 105302924 A CN105302924 A CN 105302924A CN 201510907216 A CN201510907216 A CN 201510907216A CN 105302924 A CN105302924 A CN 105302924A
- Authority
- CN
- China
- Prior art keywords
- severity level
- file destination
- check code
- target
- file
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a file management method and device. The method comprises the steps that a file needing to be read is determined to be a target file, the target importance level of the target file is obtained, and whether the target importance level is a preset importance level or not is judged; if the target importance level is the preset importance level, a check code written into the target file in advance is utilized to check data contained in the target file, and the data contained in the target file are read after checking is conducted successfully; if the target importance level is not the preset importance level, the data contained in the target file are directly read. According to the file management method and device, after the importance level of the file is obtained, whether the importance level is the preset importance level or not is judged, if yes, the data of the file are checked, otherwise, the data are directly read, so that the logical resource is saved, and meanwhile the adverse influence caused by error checking to the read and write performance is greatly reduced.
Description
Technical field
The present invention relates to computer memory technical field, more particularly, relate to a kind of file management method and device.
Background technology
At conventional memory device, especially the data stored in Flash class memory device, may occur for a certain reason, such as shake, magnetization etc. and situation about making a mistake, therefore, in order to ensure integrality and the reliability of data, usually by carrying out error-checking to data, and then the operations such as reading or write can be completed.
But, error-checking is carried out to data and usually can cause harmful effect to the readwrite performance of system, and, memory device often stores a large amount of different types of data, these data not only comprise the data higher to its integrity demands, also the data not high to its integrity demands are comprised, and to carry out error-checking to rear class data be not necessary, therefore, the waste of logical resource can be caused to the technical scheme that the total data that memory device stores all carries out error-checking in order to ensure data integrity and reliability in prior art, harmful effect when carrying out error-checking, readwrite performance caused can be aggravated simultaneously.
In sum, the dysgenic problem that in prior art, existence waste logical resource and aggravation error-checking cause readwrite performance.
Summary of the invention
The object of this invention is to provide a kind of file management method and device, to solve the dysgenic problem that the waste logical resource that exists in prior art and aggravation error-checking cause readwrite performance.
To achieve these goals, the invention provides following technical scheme:
A kind of file management method, comprising:
Determine to need the file read to be file destination, obtain the target severity level of this file destination, and judge whether described target severity level is default severity level;
If described target severity level is described default severity level, then utilizes the check code write in advance in described file destination to verify the data comprised in described file destination, and after verification succeeds, read the data comprised in described file destination;
If described target severity level is not described default severity level, then directly read the data comprised in described file destination.
Preferably, the process in advance described check code being write described file destination comprises:
Obtain the target severity level of described file destination, and when judging that described target severity level is described default severity level, according to the method for calibration with described target severity level corresponding level, the data comprised in described file destination are calculated, generate corresponding check code, and described check code is write in described file destination.
Preferably, utilize described check code to verify the data comprised in described file destination, comprising:
The method of calibration corresponding with described check code is utilized to calculate read check code to other data in described file destination except described check code, if described read check code is consistent with the corresponding check code comprised in described file destination, then determine verification succeeds.
Preferably, obtain the target severity level of described file destination, comprising:
Inquire about the inode structure of described file destination, to obtain the level attribute indicating the severity level of this file destination in described inode structure, and when determining to be pre-created this file destination be described level attribute arrange property value be described target severity level.
Preferably, be that described level attribute sets property when being pre-created described file destination, comprise:
Obtain the target suffix name of described file destination, described target suffix name is mated with the suffix name comprised in the suffix list set up in advance, and the property value of described level attribute is set according to the matching result that coupling obtains.
Preferably, the process of establishing in advance of described suffix name list, comprising:
Obtaining its severity level is the suffix name that all files of described default severity level is corresponding, and the suffix name with identical initial is left in the same node of balanced binary tree with the form of array, determines that described balanced binary tree is described suffix name list.
A kind of document management apparatus, comprising:
Judge module, needing the file read to be file destination for determining, obtaining the target severity level of this file destination, and judging whether described target severity level is default severity level;
First execution module, if be described default severity level for described target severity level, then utilize the check code write in advance in described file destination to verify the data comprised in described file destination, and after verification succeeds, read the data comprised in described file destination;
Second execution module, if be not described default severity level for described target severity level, then directly reads the data comprised in described file destination.
Preferably, also comprise:
Writing module, for obtaining the target severity level of described file destination, and when judging that described target severity level is described default severity level, according to the method for calibration with described target severity level corresponding level, the data comprised in described file destination are calculated, generate corresponding check code, and described check code is write in described file destination.
Preferably, the first execution module comprises:
Verification unit, for utilizing the method for calibration corresponding with described check code, read check code is calculated to other data in described file destination except described check code, if described read check code is consistent with the corresponding check code comprised in described file destination, then determine verification succeeds.
Preferably, judge module comprises:
Acquiring unit, for inquiring about the inode structure of described file destination, to obtain the level attribute indicating the severity level of this file destination in described inode structure, and when determining to be pre-created this file destination be described level attribute arrange property value be described target severity level.
A kind of file management method provided by the invention and device, wherein, the method comprises: determine that the file that needs read is file destination, obtain the target severity level of this file destination, and judges whether described target severity level is default severity level; If described target severity level is described default severity level, then utilizes the check code write in advance in described file destination to verify the data comprised in described file destination, and after verification succeeds, read the data comprised in described file destination; If described target severity level is not described default severity level, then directly read the data comprised in described file destination.Compared with prior art, the application is after the severity level obtaining file, judge whether severity level is default severity level, if, then its data are verified, otherwise, then directly read data, thus, higher for severity level, data higher to its integrity demands in other words carry out errors validity, and it is lower for severity level, data lower to its integrity demands in other words then do not carry out errors validity, be different from the technical scheme of in prior art, the total data stored all being carried out to error-checking, therefore, effectively reduce the number of times carrying out error-checking, thus while saving logical resource, greatly reduce the harmful effect that error-checking causes readwrite performance.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only embodiments of the invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to the accompanying drawing provided.
The process flow diagram of a kind of file management method that Fig. 1 provides for the embodiment of the present invention;
The structural representation of the balanced binary tree of suffix name is included in a kind of file management method that Fig. 2 provides for the embodiment of the present invention;
The structural representation of a kind of document management apparatus that Fig. 3 provides for the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
Refer to Fig. 1, it illustrates the process flow diagram of a kind of file management method that the embodiment of the present invention provides, can comprise the following steps:
S11: determine to need the file read to be file destination, obtain the target severity level of this file destination.
It should be noted that, file destination can be arbitrary file needing to read, and the severity level of file destination is target severity level.Wherein, the severity level of file represents the significance level of this file, in other words, represent the height of the integrity demands to this file, if file severity level is high, illustrate its integrity demands high, now, any damage all can impact the utilization of data in file, therefore, need to carry out error-checking to it, to ensure integrality and the reliability of data; If file severity level is low, illustrate its integrity demands low, now, a small amount of damage can't cause too large impact to the utilization of data in file, therefore, without the need to carrying out error-checking to it.For example, for the multi-medium data of the audio frequency and video class comprised in file, lower to its integrity demands, and for data such as the account comprised in file, mails, higher to its integrity demands.And, usually usually less to the data volume that its integrity demands is higher, and usually larger to the data volume that its integrity demands is lower.Therefore, error-checking is not carried out to the data lower to its integrity demands, greatly can save logical resource, and greatly reduce error-checking to the harmful effect of readwrite performance.
S12: judge whether target severity level is default severity level, if so, then performs step S13, if not, then performs step S14.
Wherein, default severity level can be determined according to actual needs, and, default severity level can comprise a severity level, also multiple severity level can be comprised, as when severity level corresponding for file being divided into two kinds, can represent with 0 and 1 respectively, wherein, 0 represents that severity level is higher, be default severity level, and 1 represents that severity level is lower, namely not default severity level, when and for example severity level corresponding for file being divided into three kinds, can with 0, 1 and 2 represent, wherein, 0 and 1 represents that severity level is higher, namely default severity level is, 2 represent that severity level is lower, namely not default severity level etc., be not specifically limited at this.
S13: utilize the check code write in file destination in advance to verify the data comprised in file destination, and read the data comprised in file destination after verification succeeds.
Target severity level is for presetting severity level, illustrate that the severity level of the data stored in this file is higher, therefore, when performing write operation to file destination, any one method of calibration of the prior art can be utilized to calculate needing the data writing file destination, to obtain corresponding check code, and check code and data are together write in file destination, when needing to verify the data in file destination, utilize the integrality of data in this method of calibration and check code determination file and just determining, and in verification succeeds, namely read operation is completed when data are no problem.
S14: directly read the data comprised in file destination.
If target severity level is not for presetting severity level, illustrate that the severity level of the data stored in this file is lower, then when carrying out write operation to file destination, without the need to calculating check code to it, corresponding, when file reading, without the need to judging integrality and the correctness of its data, therefore, the data comprised in file destination can directly be read.
The application is after the severity level obtaining file, judge whether severity level is default severity level, if, then its data are verified, otherwise, then directly read data, thus, higher for severity level, data higher to its integrity demands in other words carry out errors validity, and it is lower for severity level, data lower to its integrity demands in other words then do not carry out errors validity, be different from the technical scheme of in prior art, the total data stored all being carried out to error-checking, therefore, effectively reduce the number of times carrying out error-checking, thus while saving logical resource, greatly reduce the harmful effect that error-checking causes readwrite performance.
In addition, technique scheme disclosed by the invention is applicable to the file system (file system as based on Flash) higher to the integrity demands of data, also the file system lower to the integrity demands of data is applicable to, be more suitable for and include the higher data of its integrality and the file system to the lower data of its integrity demands, namely, the such scheme that the application provides is by conjunction with the inconsistent feature of different pieces of information integrity demands in file system, realize the strategy of file management more flexibly based on file content, there is versatility.
In a kind of file management method that above-described embodiment provides, the process in advance check code being write file destination can comprise:
Obtain the target severity level of file destination, and when judging target severity level for presetting severity level, according to the method for calibration with target severity level corresponding level, the data comprised in file destination are calculated, generate corresponding check code, and check code is write in file destination.
It should be noted that, when judging the severity level of file destination for presetting severity level, illustrate and need to carry out corresponding error-correction operations to file destination, therefore, need the calculating data in file destination being carried out to check code, and also specifically can be divided into different severity levels due to default severity level, therefore, different methods of calibration can be adopted for the different severity level files meeting default severity level, namely realize classification error correction.
Specifically, importance according to meeting the data comprised in the file of default severity level is divided into different ranks through it, and when carrying out the calculating of check code to its data, need the calculating carrying out check code according to the method for calibration with its severity level corresponding level, wherein, method of calibration specifically can comprise Hamming check, parity checking, CRC (cyclic redundancy) verification etc., be classical method of calibration of the prior art, do not repeat them here, and the misdata amount that different methods of calibration can detect and the misdata amount that can correct are different, corresponding, its computation complexity, computing time and also different on the impact of file system performance, in simple terms, the verification error-correcting performance of the method for calibration that complexity is higher is better, in the file meeting default severity level, corresponding complexity method of calibration is from high to low selected to carry out error-checking to it from high to low according to file severity level, thus, can make file system again can the read or write speed of raising data of maximum possible while satisfied verification error correction (fault-tolerant) requires.
In a kind of file management method that above-described embodiment provides, utilize check code to verify the data comprised in file destination, can comprise:
Utilize the method for calibration corresponding with check code to calculate read check code to other data in file destination except check code, if read check code is consistent with the corresponding check code comprised in file destination, then determine verification succeeds.
It should be noted that, some methods of calibration can when detecting mistake automatic error-correcting, some Intelligent Measurement mistake and can not error correction, therefore, corresponding, verification succeeds in step s 13 corresponds to and the method for calibration of automatic error-correcting can refer to and detect mistake and after successful correction, and correspond to and can not the method for inspection of automatic error-correcting be worth being after not detecting mistake, the successful information of read operation is returned after verification succeeds, if verifying of correspondence is unsuccessful, directly return mistake, and stop read operation.
In a kind of file management method that above-described embodiment provides, obtain the target severity level of file destination, can comprise:
The inode structure of query aim file, to obtain the level attribute of the severity level indicating this file destination in inode structure, and when determining to be pre-created this file destination be level attribute arrange property value be target severity level.
In the inode structure of file, the property value of level attribute is the severity level of this file, wherein, inode structure is the set of a file all properties in file system, it denotes the title, size, creation-time, modification time etc. of file, be the data structure that each file must have, and all can carry out read-write operation to the inode structure of correspondence in the read-write process of file.Specifically, by adding level attribute in inode structure in the application, can represent with file_level, carrying out the severity level of markup document.
Wherein, be that level attribute sets property when being pre-created file destination, can comprise:
Obtain the target suffix name of file destination, target suffix name is mated with the suffix name comprised in the suffix list set up in advance, and according to mating the property value of the matching result degree of establishment attribute obtained.
Wherein, the suffix name of whole different severity level file can be comprised in suffix name list, target suffix name is utilized to mate with the suffix name in suffix name list, the suffix name that target suffix name is identical can be obtained, now, the severity level that this suffix name is corresponding is severity level corresponding to target suffix name, also the suffix name of a part of severity level can be comprised in suffix name list, as only included the suffix name of default severity level in suffix name list, or only include not for presetting the suffix name of severity level, now, if the suffix name identical with target suffix name can be obtained by suffix name list, then determine that the severity level of target suffix name is the severity level that the severity level corresponding with the suffix name comprised in suffix name list is identical, otherwise, then determine that the severity level of target suffix name is the severity level that not corresponding with the suffix name comprised in suffix name list severity level is identical, or carry out other settings according to actual needs, all within protection scope of the present invention.
And correspondence, when only including the suffix name of default severity level in suffix name list, the process of establishing in advance of suffix name list, can comprise:
Obtaining its severity level is the suffix name that all files of default severity level is corresponding, and leaves in the same node of balanced binary tree by the suffix name with identical initial with the form of array, as shown in Figure 2, determines that balanced binary tree is suffix name list.
In addition, the suffix name stored can be capitalization, or be lowercase, and by the mode of balanced binary tree, the node identical with target suffix name initial can be determined, and then determine the suffix name identical with this target suffix name in this node, and then determine the severity level that target suffix name is corresponding, thereby, it is possible to accelerate to utilize the suffix name of file to inquire about the matching speed of its corresponding suffix name, and then accelerate the speed determining the severity level of file.Corresponding, determine that the severity level of file can first by suffix name upper or lowercase, with consistent with the form of the suffix name stored in balanced binary tree.
Certainly, also the identical suffix name of front two letter can be put into same node, specifically can set according to actual needs, all within protection scope of the present invention.In addition; can mate according to the suffix name of file, also can mate with the zone bit list preset according to the zone bit arranged for different file, thus determine the severity level of file; specifically can determine according to actual needs, all within protection scope of the present invention.
To expand Hamming check, the process operated file is described in the embodiment of the present invention, wherein, expansion Hamming check method is encoded to the data of 32 or decode, it is made up of information code and check code, information code 26 is designated as I0-I25, check code 6 is designated as P0-P5, and common Hamming code method of calibration is that specific position in 32 bit data inserts check code, its check code and information code intersection mix, in expanded Hamming code, check code P0-P5 is placed on a high position for data, and information code is placed on the low level of data.In addition, suppose that the severity level of file is respectively 1 or 0, wherein, 0 represents that severity level is higher, and 1 represents that severity level is lower, and namely 0 for presetting severity level.Specifically, the detailed process creating new file is:
File system is called sys_open (system call) by open action and is opened the file that name is called filename, and calls by sys_open respective function to be obtained this file pathname by the process space.
Call respective function and obtain a new file object and the association attributes that this file object is set, according to pathname lookups respective file, if the mark O_CREATE of this file corresponding is 1, and do not find respective file, then call the file that document creation function creation one is new, and the inode structure of this file is set, determine the severity level of this file according to specified filename and filename, and this severity level is set to the property value of the attribute file_level in inode structure.
And the write operation of file system is the data buffer (representing with data_buf) that reception user's space passes over, and the function of writing of specifying by calling file system writes data in respective file.Wherein, the function (representing with f_op->write) of writing of file system is specified by the file operation set of file system, therefore to the improvement of file write operation mainly in f_op->write function.Specifically, to the detailed process that file carries out write operation be:
File_level attribute in file reading inode structure, to obtain its severity level, if the severity level of file is 1, then according to the IO structure iovec generated in data_buf needed for lower floor's write operation function, calls underlying function and completes write operation.If the severity level of file is 0, then apply for new data buffer data_buf_new, and the data in data_buf are split in units of 26 and the data of the hamming utilizing Hamming check method corresponding coding generation 32, be stored in data_buf_new buffer zone, change according to data volume is modified to response parameter, and discharge data_buf, by generating the IO structure iovec needed for lower floor's write operation function in data_buf_new, calling underlying function and completing write operation.
In addition, file system is read behaviour and is realized based in f_op->read function, data also pass in user buffering district data_buf by the data in the iovec structure that this function reception underlying function transmits, and specifically, the flow process of file being carried out to read operation comprises:
Request for data buffer zone data_buf_tmp, and the data in iovec lower floor returned are stored in data_buf_tmp, file_level attribute in file reading inode structure, determine its severity level, if its severity level is 1, then by the data in data_buf_tmp stored in data_buf, terminate and return to read successfully, if its severity level is 0, then the data in data_buf_tmp are split in units of 32, and the read check code of the data of reading is recalculated by Hamming check method, and the check code stored in read check code and file is contrasted, if completely the same explanation data are correct, data after segmentation are removed check code part, then by data stored in data_buf, terminate and return to read successfully, if check code is inconsistent, then according to the data bits that the rule judgment of Hamming check method is made mistakes, if only have a data to make mistakes, then judge to make mistakes the position of data bit error correction, to split further and remove the data after check code stored in data_buf, terminate and return to read successfully, if there are more than two and two to make mistakes, directly return mistake.
Corresponding with said method embodiment, a kind of document management apparatus of the embodiment of the present invention, as shown in Figure 3, can comprise:
Judge module 11, needing the file read to be file destination for determining, obtaining the target severity level of this file destination, and judging whether target severity level is default severity level;
First execution module 12, if for target severity level for presetting severity level, then utilizes the check code write in file destination in advance to verify the data comprised in file destination, and after verification succeeds, reads the data comprised in file destination;
Second execution module 13, if for target severity level not for presetting severity level, then directly read the data comprised in file destination.
The application is after the severity level obtaining file, judge whether severity level is default severity level, if, then its data are verified, otherwise, then directly read data, thus, higher for severity level, data higher to its integrity demands in other words carry out errors validity, and it is lower for severity level, data lower to its integrity demands in other words then do not carry out errors validity, be different from the technical scheme of in prior art, the total data stored all being carried out to error-checking, therefore, effectively reduce the number of times carrying out error-checking, thus while saving logical resource, greatly reduce the harmful effect that error-checking causes readwrite performance.
In a kind of document management apparatus that above-described embodiment provides, can also comprise:
Writing module, for obtaining the target severity level of file destination, and when judging target severity level for presetting severity level, according to the method for calibration with target severity level corresponding level, the data comprised in file destination are calculated, generate corresponding check code, and check code is write in file destination.
In a kind of document management apparatus that above-described embodiment provides, the first execution module can comprise:
Verification unit, for utilizing the method for calibration corresponding with check code to calculate read check code to other data in file destination except check code, if read check code is consistent with the corresponding check code comprised in file destination, then determines verification succeeds.
In a kind of document management apparatus that above-described embodiment provides, judge module can comprise:
Acquiring unit, for the inode structure of query aim file, to obtain the level attribute of the severity level indicating this file destination in inode structure, and when determining to be pre-created this file destination be level attribute arrange property value be target severity level.
In a kind of document management apparatus that above-described embodiment provides, can also comprise:
Creation module, for obtaining the target suffix name of file destination, mates target suffix name with the suffix name comprised in the suffix list set up in advance, and according to mating the property value of the matching result degree of establishment attribute obtained.
In a kind of document management apparatus that above-described embodiment provides, can also comprise:
Set up module, be the suffix name that all files of default severity level is corresponding for obtaining its severity level, and the suffix name with identical initial is left in the same node of balanced binary tree with the form of array, determine that balanced binary tree is suffix name list.
Because said apparatus embodiment is corresponding with said method embodiment, therefore, the explanation referring to corresponding part in said method embodiment is illustrated for it, does not repeat them here.
To the above-mentioned explanation of the disclosed embodiments, those skilled in the art are realized or uses the present invention.To be apparent for a person skilled in the art to the multiple amendment of these embodiments, General Principle as defined herein can without departing from the spirit or scope of the present invention, realize in other embodiments.Therefore, the present invention can not be restricted to these embodiments shown in this article, but will meet the widest scope consistent with principle disclosed herein and features of novelty.
Claims (10)
1. a file management method, is characterized in that, comprising:
Determine to need the file read to be file destination, obtain the target severity level of this file destination, and judge whether described target severity level is default severity level;
If described target severity level is described default severity level, then utilizes the check code write in advance in described file destination to verify the data comprised in described file destination, and after verification succeeds, read the data comprised in described file destination;
If described target severity level is not described default severity level, then directly read the data comprised in described file destination.
2. method according to claim 1, is characterized in that, the process in advance described check code being write described file destination comprises:
Obtain the target severity level of described file destination, and when judging that described target severity level is described default severity level, according to the method for calibration with described target severity level corresponding level, the data comprised in described file destination are calculated, generate corresponding check code, and described check code is write in described file destination.
3. method according to claim 2, is characterized in that, utilizes described check code to verify the data comprised in described file destination, comprising:
The method of calibration corresponding with described check code is utilized to calculate read check code to other data in described file destination except described check code, if described read check code is consistent with the corresponding check code comprised in described file destination, then determine verification succeeds.
4. method according to claim 1, is characterized in that, obtains the target severity level of described file destination, comprising:
Inquire about the inode structure of described file destination, to obtain the level attribute indicating the severity level of this file destination in described inode structure, and when determining to be pre-created this file destination be described level attribute arrange property value be described target severity level.
5. method according to claim 4, is characterized in that, is that described level attribute sets property, comprises when being pre-created described file destination:
Obtain the target suffix name of described file destination, described target suffix name is mated with the suffix name comprised in the suffix list set up in advance, and the property value of described level attribute is set according to the matching result that coupling obtains.
6. method according to claim 5, is characterized in that, the process of establishing in advance of described suffix name list, comprising:
Obtaining its severity level is the suffix name that all files of described default severity level is corresponding, and the suffix name with identical initial is left in the same node of balanced binary tree with the form of array, determines that described balanced binary tree is described suffix name list.
7. a document management apparatus, is characterized in that, comprising:
Judge module, needing the file read to be file destination for determining, obtaining the target severity level of this file destination, and judging whether described target severity level is default severity level;
First execution module, if be described default severity level for described target severity level, then utilize the check code write in advance in described file destination to verify the data comprised in described file destination, and after verification succeeds, read the data comprised in described file destination;
Second execution module, if be not described default severity level for described target severity level, then directly reads the data comprised in described file destination.
8. device according to claim 7, is characterized in that, also comprises:
Writing module, for obtaining the target severity level of described file destination, and when judging that described target severity level is described default severity level, according to the method for calibration with described target severity level corresponding level, the data comprised in described file destination are calculated, generate corresponding check code, and described check code is write in described file destination.
9. device according to claim 8, is characterized in that, the first execution module comprises:
Verification unit, for utilizing the method for calibration corresponding with described check code, read check code is calculated to other data in described file destination except described check code, if described read check code is consistent with the corresponding check code comprised in described file destination, then determine verification succeeds.
10. device according to claim 7, is characterized in that, judge module comprises:
Acquiring unit, for inquiring about the inode structure of described file destination, to obtain the level attribute indicating the severity level of this file destination in described inode structure, and when determining to be pre-created this file destination be described level attribute arrange property value be described target severity level.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510907216.0A CN105302924A (en) | 2015-12-09 | 2015-12-09 | File management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510907216.0A CN105302924A (en) | 2015-12-09 | 2015-12-09 | File management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105302924A true CN105302924A (en) | 2016-02-03 |
Family
ID=55200193
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510907216.0A Pending CN105302924A (en) | 2015-12-09 | 2015-12-09 | File management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105302924A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106294317A (en) * | 2016-07-29 | 2017-01-04 | 浪潮(北京)电子信息产业有限公司 | The form information method of calibration at a kind of cloud platform interface and system |
| CN106776103A (en) * | 2017-01-16 | 2017-05-31 | 湖南财政经济学院 | Internet of Things big data fast calibration method |
| CN107609027A (en) * | 2017-08-08 | 2018-01-19 | 捷开通讯(深圳)有限公司 | The anti-deleted marker position of file is set and prevents from deleting the method and device of file by mistake |
| CN108123934A (en) * | 2017-12-06 | 2018-06-05 | 深圳先进技术研究院 | A kind of data integrity verifying method towards mobile terminal |
| CN111143347A (en) * | 2019-11-15 | 2020-05-12 | 苏州浪潮智能科技有限公司 | Object storage data consistency test method, system, terminal and storage medium |
| CN114741231A (en) * | 2022-04-19 | 2022-07-12 | 深圳鲲云信息科技有限公司 | Data read-write method, device and equipment based on memory and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0430291A2 (en) * | 1989-11-30 | 1991-06-05 | Sony Corporation | A data transfer system |
| CN101458645A (en) * | 2007-12-11 | 2009-06-17 | 英业达股份有限公司 | Computer operating system, file data repairing system of software thereof and method thereof |
| CN101795402A (en) * | 2009-02-04 | 2010-08-04 | 华为技术有限公司 | Macro block dividing method and device |
| CN101957923A (en) * | 2009-07-20 | 2011-01-26 | 西门子公司 | Method and reader for reading data from tags in radio frequency identification system |
| CN102426638A (en) * | 2011-11-09 | 2012-04-25 | 松翰科技股份有限公司 | Chip reading method and encryption method |
-
2015
- 2015-12-09 CN CN201510907216.0A patent/CN105302924A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0430291A2 (en) * | 1989-11-30 | 1991-06-05 | Sony Corporation | A data transfer system |
| CN101458645A (en) * | 2007-12-11 | 2009-06-17 | 英业达股份有限公司 | Computer operating system, file data repairing system of software thereof and method thereof |
| CN101795402A (en) * | 2009-02-04 | 2010-08-04 | 华为技术有限公司 | Macro block dividing method and device |
| CN101957923A (en) * | 2009-07-20 | 2011-01-26 | 西门子公司 | Method and reader for reading data from tags in radio frequency identification system |
| CN102426638A (en) * | 2011-11-09 | 2012-04-25 | 松翰科技股份有限公司 | Chip reading method and encryption method |
Non-Patent Citations (1)
| Title |
|---|
| 刘庆华: "一种日志式闪存文件系统的分析与改进", 《中国优秀硕士学位论文全文数据库（电子期刊）信息科技辑》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106294317A (en) * | 2016-07-29 | 2017-01-04 | 浪潮(北京)电子信息产业有限公司 | The form information method of calibration at a kind of cloud platform interface and system |
| CN106776103A (en) * | 2017-01-16 | 2017-05-31 | 湖南财政经济学院 | Internet of Things big data fast calibration method |
| CN107609027A (en) * | 2017-08-08 | 2018-01-19 | 捷开通讯(深圳)有限公司 | The anti-deleted marker position of file is set and prevents from deleting the method and device of file by mistake |
| CN108123934A (en) * | 2017-12-06 | 2018-06-05 | 深圳先进技术研究院 | A kind of data integrity verifying method towards mobile terminal |
| CN111143347A (en) * | 2019-11-15 | 2020-05-12 | 苏州浪潮智能科技有限公司 | Object storage data consistency test method, system, terminal and storage medium |
| CN114741231A (en) * | 2022-04-19 | 2022-07-12 | 深圳鲲云信息科技有限公司 | Data read-write method, device and equipment based on memory and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105302924A (en) | File management method and device | |
| CN102937922B (en) | Inquiry and repair data | |
| CN105224237A (en) | A kind of date storage method and device | |
| CN110727597B (en) | Method for checking invalid code completion case based on log | |
| CN103631721A (en) | Method and system for isolating bad blocks in internal storage | |
| CN104461641A (en) | Data burning and writing method, system and equipment and target equipment | |
| CN103218271B (en) | A kind of data error-correcting method and device | |
| CN103778030A (en) | Write-in method, error tracking method and processor for blog subsystem | |
| CN110795269A (en) | Data recovery verification method, device and equipment | |
| US20140337301A1 (en) | Big data extraction system and method | |
| CN111625199A (en) | Method and device for improving reliability of data path of solid state disk, computer equipment and storage medium | |
| CN108196975B (en) | Data verification method and device based on multiple checksums and storage medium | |
| CN110765069A (en) | Data migration method, device and system | |
| CN112445639B (en) | Method for error detection | |
| CN110110463B (en) | Integrated circuit logic connection optimization method, system and medium capable of improving time sequence | |
| CN110955916B (en) | Data integrity protection method, system and related equipment | |
| CN114816832B (en) | Data management method, device and system of single chip microcomputer | |
| CN105354107A (en) | Data transmission method and system for NOR Flash | |
| WO2021139443A1 (en) | Data access control method and apparatus, and data access device and system | |
| CN111080209B (en) | BOM verification method, system, device and storage medium | |
| CN110297728B (en) | Selective data reconstruction method in file reconstruction process based on origin data | |
| CN113535470A (en) | Configuration backup method and device, electronic equipment and storage medium | |
| CN103092713A (en) | Method for storing embedded code by using NAND flash | |
| CN114253642A (en) | System information processing method, device, electronic equipment and medium | |
| CN112445761B (en) | File checking method and device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160203 |