CN102955720A - Method for improving stability of EXT (extended) file system - Google Patents
Method for improving stability of EXT (extended) file system Download PDFInfo
- Publication number
- CN102955720A CN102955720A CN201110247222XA CN201110247222A CN102955720A CN 102955720 A CN102955720 A CN 102955720A CN 201110247222X A CN201110247222X A CN 201110247222XA CN 201110247222 A CN201110247222 A CN 201110247222A CN 102955720 A CN102955720 A CN 102955720A
- Authority
- CN
- China
- Prior art keywords
- file system
- read
- disk
- backup
- information
- 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.)
- Granted
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method for improving stability of an EXT (extended) file system. Stability of the EXT file system is improved during disk driving by the method. The method includes the steps of backing up information of a disk file system during a period or when a disk is uninstalled; if mounting of disk partitions fails, trying to mount one more time according to the backup information; and if mounting fails again, ending the mounting process. The information of the file system includes super blocks, chunking and root node information. The method further includes: synchronously processing read-write operations to disk files. The synchronous processing includes: when read-write operations are performed to the disk file system, transmitting a read-write request in a memory buffer to a storage medium, namely transmitting all unwritten data stored in the buffer to a device driver and transmitting the data to a storage device to complete synchronization. The read-write operations include file creating or file deleting and the like.
Description
Technical field
The present invention relates to a kind of software mechanism method that realizes the optimization of embedded file system, be specifically related to a kind of method of the ext of raising file system stability.
Background technology
In the society of this high speed development, people's demand is also more and more higher, and video field is all towards the high definition future development at present, although the Video coding compression factor has optimization, file is increasingly inevitable, like this must be by hard-disc storage; Cause so various set-top box, industrial computer etc. more and more higher to the reliability requirement of file system.Adopt at present operating system or linux operating system, the file system of employing generally is the ext file system, and such as EXT2, EXT3, EXT4, wherein EXT2 does not have journal function, and EXT3 and EXT4 have journal function.
Yet; hard disk is in long-term use procedure; often the situations such as file system collapse, File lose, file error can appear; the form of expression of fault is different; for the hard disk of storing important data; then show as and must reform hard disk or artificially recover hard disc data, this has had a strong impact on the reliability of product quality.The reason that causes is a lot, and modal a kind of situation then is that system exception outage causes, especially in the situation that to write the data outage then more dangerous.
For hard disk was read dish speed, the stability of the file system of hard disk seemed more important.In other words, stable file system performance is the read-write prerequisite of file.Hard disk is fixed memory device; generally on embedded system without any protection, therefore in use procedure repeatedly, the phenomenons such as file system collapse, loss of data can appear unavoidably; these defect all can affect reading of data, thereby affect the use of whole product.The subject matter that occurs: 1) file system collapse, all loss of datas; 2) can again occur after the outage of the file of deletion; 3) disappear again after the file outage that creates; 4) partial document is lost, input/output error problem.
The stability of file system can be improved from two aspects of software and hardware.Method commonly used is to add UPS or adopt single-chip microcomputer on the hardware, this technology also is not very ripe, the effect of UPS is with reminding user safety shutdown Backup Data before the system cut-off, the effect of single-chip microcomputer is before outage, by the electric capacity delay switching-off, notify simultaneously mainboard safety shutdown Backup Data, these two kinds of method costs are all higher.Have plenty of on the software to adopt and from the application program level hard disc data is carried out dual-host backup, what have then is to adopt privately owned file system, processes by certain verification scheme.Perhaps by third party's instrument, such as fsck, e2fsck etc., file system is carried out self check and reparation.But this instrument can cause certain destruction to file system, and repair time is very long.
Prior art is only once attempted in the carry disk partition, causes the stable very poor of disk file system thereby lack corresponding fault-tolerant processing mechanism; In addition, the present file system collapse that causes owing to reasons such as abnormal power-down based on the disk file system of present EXT, all loss of datas; Can again occur after the file outage of deletion; Disappear again after the file outage that creates; Partial document is lost, and the problems such as input and output also occur again and again.
Summary of the invention
The object of the invention is to, for overcoming the problems referred to above, thereby provide a kind of method of the ext of raising file system stability.
For achieving the above object, the invention provides a kind of method of the ext of raising file system stability, the method improves the stability of ext file system in the disk drive process, and described method comprises following steps:
Step 1, periodically or during the unloading disk in this disk the information of backup disk file system.
Step 2 is when the carry disk partition, if the carry procedure failure according to the information of backup, is attempted carry again, if the carry flow process is then withdrawed from again failure; Wherein, the information of described file system comprises: superblock, chunk and root nodal information.
Optimize, described method also comprises: the synchronous treatment step when disk file is carried out read-write operation.
Optionally, described synchronous treatment step is: when the ext file system is carried out read-write operation, in real time read-write requests in the core buffer is issued storage medium, soon all leave the data of not writing in the buffer area in and send to device driver, and then send to memory device, finish synchronous operation; Wherein, described read-write operation comprises: create file, deleted file, create directory, deltree, create link, Remove Links, file rename and catalogue rename, be flexible coupling, hard link or written document.
Further optimize, if when described disk file system is Journaling File System, it is synchronous that described synchronous processing also comprises daily record, and the log information that namely will leave in the buffer zone in real time is synchronized to storage medium; And the information of described file system also comprises the daily record nodal information.
In the technique scheme, described step 2 further comprises following steps:
Step 2-1 reads the superblock of zero piece group, reads successfully, enters next step; Otherwise read backup superblock information from disk partition, read failure and withdraw from the carry flow process; If read the success of backup superblock, the backup superblock is returned to the superblock position of zero piece group, again read the superblock of zero piece group, read successfully, enter next step, otherwise withdraw from the carry flow process;
Step 2-2 reads the group descriptor of zero piece group, reads and successfully enters next step; If unsuccessfully read the backup group descriptor information, read failure and withdraw from the carry flow process; Successful then the backup group descriptor is returned in the zero piece group, and again read the group descriptor of zero piece group, read and successfully enter next step, otherwise withdraw from the carry flow process;
Step 2-3 reads the root nodal information of zero piece group, if successfully enter next step; Otherwise judge to have backup root nodal information, do not exist and then withdraw from the carry flow process; If exist, then will back up the corresponding root nodal information position that the root nodal information returns to zero piece group; Read the root nodal information of zero piece group, read and successfully enter next step, otherwise withdraw from the carry flow process.
Optimize, if file system is Journaling File System, then between above-mentioned steps 2-2 and step 2-3, further comprise following steps: read the daily record nodal information of zero piece group, if successfully enter next step; If failure judges whether to exist the backup log nodal information, do not exist and withdraw from; Exist then the backup log nodal information to be returned in the zero piece group, read the daily record nodal information of zero piece group, read and successfully enter next step, otherwise withdraw from the carry flow process.
In the technique scheme, the backup of described superblock information, group descriptor, root nodal information is in the headspace of disk.
The invention has the advantages that, in order to improve the stability of disk file system, with respect to strategy on the hardware of prior art employing, cost is low, realizes that simply the time is short; And with respect to other solution from the software, the present invention does not need to write specially new application program, mechanism is simple, does not need complicated verification scheme, only need to slightly adjust the stability that just can improve disk file system on the basis of original disk driver; Simultaneously, also have larger versatility, can be applied on the different platforms and (comprise ext2 and ext3, ext4); This mechanism greatly reduces the difficulty of exploitation.In sum, the invention provides the implementation method of optimizing the ext file system, comprise file system important data backup mechanism, also normal carry during disk crash, the I/O operation that reaches file system updates in the disk, guaranteed the up-to-date of data in the disk, and to affect the magnetic disc i/o performance very little, and the complete scheme that improves the stability of embedded file system is provided.Overcome existing EXT file system and the file system collapse easily occurred, File lose, the corrupted data phenomenon realizes that file system is stable, this software level of slave driver improves the scheme of Ext file system stability.
Description of drawings
Fig. 1 is the flow process fault-tolerant processing process flow diagram of the file system mounted hard disk of linux ext3 of the present invention;
Fig. 2 is the flow process of linux ext3 file system I/O operation of the present invention and synchronous operation;
Fig. 3 is the flow process of linux ext3 file system unloading hard disk of the present invention and the process flow diagram that backs up the processing of significant data.
Embodiment
Below in conjunction with the drawings and specific embodiments the present invention is described in further detail:
The invention provides a kind of method of the ext of realization document system optimization, comprise the steps:
1) during the carry disk partition, if normal carry then returns the carry success, withdraws from the carry flow process; If for the first time carry failure then recovers superblock, chunk information, root nodal information and daily record nodal information from backing up the zone, carry out again carry, the carry flow process is withdrawed from the carry success, returns the carry success; Otherwise return the carry failure, stop again carry and attempt;
2) the I/O operation of file added synchronously processing operation;
3) backup superblock, chunk information, root nodal information, daily record nodal information regularly or during the unloading hard disk, this step is to be described step 1) carry out again carry when losing and attempt required information reporting the loss for the first time.
In the such scheme, described step 1) and step 3) positive connection arranged.In step 3) in carry out backup operation, can be in step 1) in, occur restoring when wrong.
The implementation method of the raising ext file system stability that the present embodiment provides comprises: fault-tolerant processing in carry disk partition process mechanism, this mechanism further based on to regularly or during the unloading disk, are carried out the back-up processing strategy to information such as disk superblocks again; Synchronous processor system when disk file is carried out read-write operation.
For the ext file system, fdisk is divided into block one by one, and each block on ext file system is of a size, but for different ext file system, the size of block can be had any different.Typical block size is 1024bytes or 4096bytes.This size determined when creating the ext file system, and it can be specified by the system manager, also can by the creation procedure of the file system size according to fdisk, automatically select a more reasonably value.The 1024bytes that subregion begins deposits boot boot, ensuing 1024bytes deposits superblock (super block), group describing word (group descriptors) originates in a new piece, and take separately a block space, all pieces afterwards are organized into the piece group, and the piece group is only the place of real storing documents.Superblock (super block) contains some global parameters of whole file system, as: file label, Globally Unique Identifier, state, block size, total block data, every group of inode number, total i nodes, every chunk number etc., super block is read into internal memory when file mount, until be released during umount, superblock is most important for file system.See following form for details:
The carry disk partition is exactly that driver operates disk partition, i.e. common block device driver read requests operation, and specifically comprise with the normal read operation of the ext file system of daily record: (1) reads superblock information, the authenticating documents system type; (2) read and verify that group descriptor information (3) reads and verify journal inode; (4) read and verify root inode.
In technique scheme 1) in, further, each step may be failed, if failure is then processed respectively.The Ext file system is that superblock has been reserved the backup zone, and is general in first of the 1st, 3,5,7,9 group.The present invention adopts the set of tiles (block group) in the above reservation backup zone.The numbering of piece group is since 0, and namely first group is the 0th piece group.
The below is specifically described in conjunction with Fig. 1 take backup address as the 3rd piece group as example.
Embodiment 1
Step 11 reads the superblock of the 0th piece group, reads successfully, enters next step; Otherwise read backup superblock (the 3rd piece group first), read the backup superblock and unsuccessfully withdraw from the carry flow process; If read the success of backup superblock, the backup superblock is returned to the superblock position of the 0th piece group, again read the superblock of the 0th piece group, read and successfully enter next step, otherwise withdraw from the carry flow process.
Step 12 reads the group descriptor of the 0th piece group, is proved to be successful and enters next step; If unsuccessfully read backup group descriptor information (second piece of the 3rd piece group), authentication failed withdraws from the carry flow process; Be proved to be successful then and the backup group descriptor returned in the 0th the piece group, and again read the group descriptor of the 0th piece group, read and successfully enter next step, otherwise withdraw from the carry flow process;
Step 13 reads the root nodal information of the 0th piece group, if successfully enter next step; Otherwise judge the backup sign, see that whether backup root nodal information exists, and does not exist and then withdraws from the carry flow process; If exist, then will back up the corresponding root nodal information position that the root nodal information returns to the 0th piece group.Read the root nodal information of the 0th piece group, read and successfully enter next step, otherwise withdraw from the carry flow process.
Wherein, if the file system that adopts is ext3 or ext4, these two file system are Journaling File System, so between above-mentioned steps 12 and step 13, further comprise following steps:
Read the daily record nodal information of the 0th piece group, if successfully enter next step; If the backup sign is judged in failure, see whether there is the backup log nodal information, do not exist and withdraw from; Exist then the backup log nodal information to be returned in the 0th the piece group, read the daily record nodal information of the 0th piece group, read and successfully enter next step, otherwise withdraw from the carry flow process.
The specific implementation of the back-up processing mechanism of the superblock described in above-described embodiment, chunk, daily record nodal information, root nodal information is operating as: backup superblock, chunk information, root nodal information, daily record nodal information regularly or during unloading (do_mount) hard disk, also normal extension dish when guaranteeing disk crash.Backup address can be the disk management space that the Ext file system keeps for the keeper.Such as the 3rd the piece group position of mentioning among the embodiment 1, just can be used as the backup zone.
Specific implementation is as shown in Figure 3:
The corresponding root nodal information storeroom of three piece groups of step 31 backup root inode to the, sign of juxtaposition such as " Intellix-root ", indicates and whether backed up root inode.
The group descriptor storeroom of three piece groups of step 32 backup group descriptor to the.
Step 33 backs up first of three piece groups of superblock to the.
Technique scheme 3) in, if the file system that adopts is ext3 or ext4, these two file system are Journaling File System, so between above-mentioned steps 31 and step 32, further comprise following steps
The corresponding daily record nodal information storeroom of three piece groups of backup journal inode to the, sign of juxtaposition such as " Intellix-journal ", indicates and whether backed up journal inode.
Embodiment 2
Because the Linux file system is built as medium by Virtual File System.Virtual File System VFS (virtual file system) is a kind of framework that inner nuclear layer is realized, for user's space provides unified file operation interface.Each file system realizes deriving one group of general-purpose interface, for VFS.Buffer zone is used for the request between the two of cache file system and related blocks equipment.Namely can transmit by buffer cache the read-write requests of underlying device driver, to reduce the number of times of access physical equipment, accelerate access speed.If the read-write requests in the buffer zone is not performed, by abnormal power-down, just might occur 1) the file system collapse, all loss of datas; 2) can again occur after the outage of the file of deletion; 3) disappear again after the file outage that creates; 4) partial document is lost, the problems such as input/output error.For avoiding the problems referred to above, when disk is carried out write operation, namely revise superblock, chunk, block bitmap, inode bitmap is during the metadata such as inode table, just need to do synchronous operation to internal memory, in time storage medium be issued in request in the buffer zone, to reduce the problem probability of occurrence.Disk write operation comprises: create directory, deltree, create file, deleted file, catalogue rename, file rename, establishment and deletion and be flexible coupling, create and delete the operations such as hard link, written document
The Sync order is that the request in the buffer cache is sent to medium, and the data that force all not write send to device driver, and then send to memory device, can reach synchronous purpose.
For ext3 and ext4 file system, have journal function, because buffering has also been used in the operation of daily record, so need to carry out synchronous operation, log information in time is synchronized to disk from buffer area.Synchronous mark position (S_SYNC) set to the i_flags parameter in the node structure body can reach synchronous purpose.
Specific implementation is the example explanation in conjunction with createing directory.As shown in Figure 2:
Step 21, user application will create directory at disk (mkdir), just will call kernel system entry (sys_mkdir), call again Virtual File System interface (vfs_mkdir), find the function that creaties directory (ext3_mkdir) of concrete file system.The ext3 file system has journal function.A complete I/O operation is an atomic operation.Because the journal system of ext3/ext4 has also used buffering, if there is powering-off state, also can lose record.This just need to the journal system in ext3 do synchronous operation.As among Fig. 2 (operation of dir-＞i_flags|=S_SYNC) is finished,
Step 22 withdraws from after the daily record atomic operation, and the request of buffer zone in time is synchronized to disk (sync).
At first, above-described embodiment 2 can implement simultaneously with embodiment 1, and namely those skilled in the art can further improve disk file system stability with the backup information of embodiment 1 and the synchronization policy that adopts again embodiment 2 to mention based on the application of policies that backs up the carry disk partition on the basis of prior art.
Secondly, those skilled in the art can adopt separately the strategy of embodiments of the invention 1 to improve the stability of disk file system, or adopt separately the synchronization policy of embodiment 2 to improve the stability that has disk file system now.
Need to prove, embodiment of the present invention of above introduction and and unrestricted.It will be understood by those of skill in the art that any modification to technical solution of the present invention or be equal to substitute the spirit and scope that do not break away from technical solution of the present invention, it all should be encompassed in the claim scope of the present invention.
Claims (8)
1. method that improves ext file system stability, the method improves the stability of ext file system in the disk drive process, and described method comprises following steps:
Step 1, periodically or during the unloading disk in this disk the information of backup disk file system;
Step 2 is when the carry disk partition, if the carry procedure failure according to the information of backup, is attempted carry again, if the carry flow process is then withdrawed from again failure; Wherein, the information of described file system comprises: superblock, chunk and root nodal information.
2. the method for raising ext file system stability according to claim 1 is characterized in that, described method also comprises: the synchronous treatment step when disk file is carried out read-write operation.
3. the method for raising according to claim 2 ext file system stability, it is characterized in that, described synchronous treatment step is: when the ext file system is carried out read-write operation, in real time read-write requests in the core buffer is issued storage medium, soon all leave the data of not writing in the buffer area in and send to device driver, and then send to memory device, finish synchronous operation;
Wherein, described read-write operation comprises: create file, deleted file, create directory, deltree, create link, Remove Links, file rename and catalogue rename, be flexible coupling, hard link or written document.
4. according to claim 2 or the methods of 3 described raising ext file system stability, it is characterized in that, when if described disk file system is Journaling File System, it is synchronous that described synchronous processing also comprises daily record, and the log information that namely will leave in the buffer zone in real time is synchronized to storage medium.
5. according to claim 1, the methods of 2 or 3 described raising ext file system stability, it is characterized in that, if described disk file system is Journaling File System, the information of described file system also comprises the daily record nodal information.
6. according to claim 1, the methods of 2 or 3 described raising ext file system stability, it is characterized in that, described step 2 further comprises following steps:
Step 2-1 reads the superblock of zero piece group, reads successfully, enters next step; Otherwise read backup superblock information from disk partition, read failure and withdraw from the carry flow process; If read the success of backup superblock, the backup superblock is returned to the superblock position of zero piece group, again read the superblock of zero piece group, read successfully, enter next step, otherwise withdraw from the carry flow process;
Step 2-2 reads the group descriptor of zero piece group, is proved to be successful and enters next step; If unsuccessfully read the backup group descriptor information, read failure and withdraw from the carry flow process; Successful then the backup group descriptor is returned in the zero piece group, and again read the group descriptor of zero piece group, read and successfully enter next step, otherwise withdraw from the carry flow process;
Step 2-3 reads the root nodal information of zero piece group, if successfully enter next step; Otherwise judge the backup sign, see whether backup root nodal information exists,, do not exist and then withdraw from the carry flow process; If exist, then will back up the corresponding root nodal information position that the root nodal information returns to zero piece group; Read the root nodal information of zero piece group, read and successfully enter next step, otherwise withdraw from the carry flow process.
7. the method for raising ext file system stability according to claim 6 is characterized in that, if file system is Journaling File System, then between above-mentioned steps 2-2 and step 2-3, further comprises following steps:
Read the daily record nodal information of zero piece group, if successfully enter next step; If the backup sign is judged in failure, see that whether the backup log nodal information exists, and does not exist and withdraws from; Exist then the backup log nodal information to be returned in the zero piece group, read the daily record nodal information of zero piece group, read and successfully enter next step, otherwise withdraw from the carry flow process.
8. according to claim 1, the methods of 2,3 or 7 described raising ext file system stability, it is characterized in that, the backup of described superblock information, group descriptor, root nodal information is in the headspace of disk.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110247222.XA CN102955720B (en) | 2011-08-25 | 2011-08-25 | A kind of method improving ext file system stability |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110247222.XA CN102955720B (en) | 2011-08-25 | 2011-08-25 | A kind of method improving ext file system stability |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102955720A true CN102955720A (en) | 2013-03-06 |
| CN102955720B CN102955720B (en) | 2015-09-09 |
Family
ID=47764547
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110247222.XA Expired - Fee Related CN102955720B (en) | 2011-08-25 | 2011-08-25 | A kind of method improving ext file system stability |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102955720B (en) |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103853827A (en) * | 2014-03-07 | 2014-06-11 | 浪潮电子信息产业股份有限公司 | Database backup method capable of guaranteeing data consistency |
| CN104991926A (en) * | 2015-06-29 | 2015-10-21 | 浪潮(北京)电子信息产业有限公司 | File system recovery method and system |
| CN105068889A (en) * | 2015-08-03 | 2015-11-18 | 四川效率源信息安全技术有限责任公司 | Method for recovering completely deleted files in Ext3/Ext4 |
| CN105095026A (en) * | 2015-08-31 | 2015-11-25 | 小米科技有限责任公司 | Superblock repair method and apparatus for EXT file system and intelligent device |
| CN105204959A (en) * | 2015-08-28 | 2015-12-30 | 小米科技有限责任公司 | Method and device for restoring deleted files in ext file system |
| CN105956172A (en) * | 2016-05-23 | 2016-09-21 | 深圳市硅格半导体股份有限公司 | Log information storage method and apparatus |
| CN106021031A (en) * | 2016-05-30 | 2016-10-12 | 厦门市美亚柏科信息股份有限公司 | Deleted data restoration method and device of BTRFS file system |
| CN106126272A (en) * | 2016-06-15 | 2016-11-16 | 北京小米移动软件有限公司 | File system discharging method and device |
| CN106126382A (en) * | 2016-06-29 | 2016-11-16 | 北京小米移动软件有限公司 | Identify the method and device of file system error |
| CN107220342A (en) * | 2017-05-26 | 2017-09-29 | 郑州云海信息技术有限公司 | The control method and system of a kind of distributed data base |
| CN107451014A (en) * | 2017-08-01 | 2017-12-08 | 郑州云海信息技术有限公司 | A kind of data reconstruction method and device |
| CN107704618A (en) * | 2017-10-27 | 2018-02-16 | 北京航空航天大学 | A kind of heat based on aufs file system migrates method and system |
| CN108038024A (en) * | 2018-01-04 | 2018-05-15 | 西安锐益达风电技术有限公司 | A kind of reliable static programming file system towards NandFlash |
| CN108089818A (en) * | 2017-12-12 | 2018-05-29 | 腾讯科技（深圳）有限公司 | Data processing method, device and storage medium |
| CN109101611A (en) * | 2018-08-06 | 2018-12-28 | 郑州云海信息技术有限公司 | File system directories maximize test method, device, terminal and storage medium |
| CN110222019A (en) * | 2019-05-08 | 2019-09-10 | 安克创新科技股份有限公司 | The method of adjustment and device that file system is taken up space |
| CN110874285A (en) * | 2019-11-19 | 2020-03-10 | 厦门市美亚柏科信息股份有限公司 | Method for realizing reducible write operation of EXT file system |
| CN110941515A (en) * | 2019-12-04 | 2020-03-31 | 深圳市科力锐科技有限公司 | Host backup reconstruction method, device, server and storage medium |
| CN113419897A (en) * | 2021-01-19 | 2021-09-21 | 阿里巴巴集团控股有限公司 | File processing method and device, electronic equipment and storage medium thereof |
| CN113778753A (en) * | 2021-09-14 | 2021-12-10 | 杭州沃趣科技股份有限公司 | Method, device, equipment and medium for automatically correcting database after storage recovery |
| CN115048046A (en) * | 2022-05-26 | 2022-09-13 | 北京华昱卓程软件有限公司 | Log file system and data management method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1707440A (en) * | 2004-12-21 | 2005-12-14 | 西安三茗科技有限责任公司 | Data backup recovery and authority control method for hard disk linux document system |
| CN101256524A (en) * | 2007-12-17 | 2008-09-03 | 浪潮电子信息产业股份有限公司 | Method for maintaining file system caching compatibility |
| CN101364218A (en) * | 2007-08-10 | 2009-02-11 | 深圳市锐明视讯技术有限公司 | Hard disk video recorder file systems and checking method thereof |
| CN101944043A (en) * | 2010-09-27 | 2011-01-12 | 公安部第三研究所 | File access method of Linux virtual machine disk under Windows platform |
| CN102129435A (en) * | 2010-01-13 | 2011-07-20 | ***通信集团公司 | Data storage service control method and system |
-
2011
- 2011-08-25 CN CN201110247222.XA patent/CN102955720B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1707440A (en) * | 2004-12-21 | 2005-12-14 | 西安三茗科技有限责任公司 | Data backup recovery and authority control method for hard disk linux document system |
| CN101364218A (en) * | 2007-08-10 | 2009-02-11 | 深圳市锐明视讯技术有限公司 | Hard disk video recorder file systems and checking method thereof |
| CN101256524A (en) * | 2007-12-17 | 2008-09-03 | 浪潮电子信息产业股份有限公司 | Method for maintaining file system caching compatibility |
| CN102129435A (en) * | 2010-01-13 | 2011-07-20 | ***通信集团公司 | Data storage service control method and system |
| CN101944043A (en) * | 2010-09-27 | 2011-01-12 | 公安部第三研究所 | File access method of Linux virtual machine disk under Windows platform |
Cited By (33)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103853827A (en) * | 2014-03-07 | 2014-06-11 | 浪潮电子信息产业股份有限公司 | Database backup method capable of guaranteeing data consistency |
| CN104991926A (en) * | 2015-06-29 | 2015-10-21 | 浪潮(北京)电子信息产业有限公司 | File system recovery method and system |
| CN105068889B (en) * | 2015-08-03 | 2018-05-25 | 四川效率源信息安全技术股份有限公司 | Recover the method for complete deletion file in Ext3/Ext4 |
| CN105068889A (en) * | 2015-08-03 | 2015-11-18 | 四川效率源信息安全技术有限责任公司 | Method for recovering completely deleted files in Ext3/Ext4 |
| CN105204959A (en) * | 2015-08-28 | 2015-12-30 | 小米科技有限责任公司 | Method and device for restoring deleted files in ext file system |
| CN105204959B (en) * | 2015-08-28 | 2018-11-30 | 小米科技有限责任公司 | Restore the method and device of deleted document in ext file system |
| CN105095026A (en) * | 2015-08-31 | 2015-11-25 | 小米科技有限责任公司 | Superblock repair method and apparatus for EXT file system and intelligent device |
| CN105956172A (en) * | 2016-05-23 | 2016-09-21 | 深圳市硅格半导体股份有限公司 | Log information storage method and apparatus |
| CN105956172B (en) * | 2016-05-23 | 2019-08-13 | 深圳市硅格半导体有限公司 | The storage method and device of log information |
| CN106021031A (en) * | 2016-05-30 | 2016-10-12 | 厦门市美亚柏科信息股份有限公司 | Deleted data restoration method and device of BTRFS file system |
| CN106021031B (en) * | 2016-05-30 | 2018-09-28 | 厦门市美亚柏科信息股份有限公司 | A kind of the deletion data reconstruction method and device of BTRFS file system |
| CN106126272A (en) * | 2016-06-15 | 2016-11-16 | 北京小米移动软件有限公司 | File system discharging method and device |
| CN106126382A (en) * | 2016-06-29 | 2016-11-16 | 北京小米移动软件有限公司 | Identify the method and device of file system error |
| CN106126382B (en) * | 2016-06-29 | 2019-11-15 | 北京小米移动软件有限公司 | Identify the method and device of file system error |
| CN107220342A (en) * | 2017-05-26 | 2017-09-29 | 郑州云海信息技术有限公司 | The control method and system of a kind of distributed data base |
| CN107451014A (en) * | 2017-08-01 | 2017-12-08 | 郑州云海信息技术有限公司 | A kind of data reconstruction method and device |
| CN107704618B (en) * | 2017-10-27 | 2020-09-25 | 北京航空航天大学 | Thermal migration method and system based on aufs file system |
| CN107704618A (en) * | 2017-10-27 | 2018-02-16 | 北京航空航天大学 | A kind of heat based on aufs file system migrates method and system |
| CN108089818A (en) * | 2017-12-12 | 2018-05-29 | 腾讯科技（深圳）有限公司 | Data processing method, device and storage medium |
| CN108038024A (en) * | 2018-01-04 | 2018-05-15 | 西安锐益达风电技术有限公司 | A kind of reliable static programming file system towards NandFlash |
| CN108038024B (en) * | 2018-01-04 | 2021-03-02 | 西安锐益达风电技术有限公司 | Reliable static planning file system for NandFlash |
| CN109101611A (en) * | 2018-08-06 | 2018-12-28 | 郑州云海信息技术有限公司 | File system directories maximize test method, device, terminal and storage medium |
| CN110222019A (en) * | 2019-05-08 | 2019-09-10 | 安克创新科技股份有限公司 | The method of adjustment and device that file system is taken up space |
| CN110222019B (en) * | 2019-05-08 | 2023-12-19 | 安克创新科技股份有限公司 | Method and device for adjusting space occupied by file system |
| CN110874285B (en) * | 2019-11-19 | 2022-06-21 | 厦门市美亚柏科信息股份有限公司 | Method for realizing reducible write operation of EXT file system |
| CN110874285A (en) * | 2019-11-19 | 2020-03-10 | 厦门市美亚柏科信息股份有限公司 | Method for realizing reducible write operation of EXT file system |
| CN110941515A (en) * | 2019-12-04 | 2020-03-31 | 深圳市科力锐科技有限公司 | Host backup reconstruction method, device, server and storage medium |
| CN110941515B (en) * | 2019-12-04 | 2022-05-24 | 深圳市科力锐科技有限公司 | Host backup reconstruction method, device, server and storage medium |
| CN113419897A (en) * | 2021-01-19 | 2021-09-21 | 阿里巴巴集团控股有限公司 | File processing method and device, electronic equipment and storage medium thereof |
| CN113419897B (en) * | 2021-01-19 | 2023-12-22 | 阿里巴巴集团控股有限公司 | File processing method and device, electronic equipment and storage medium thereof |
| CN113778753A (en) * | 2021-09-14 | 2021-12-10 | 杭州沃趣科技股份有限公司 | Method, device, equipment and medium for automatically correcting database after storage recovery |
| CN113778753B (en) * | 2021-09-14 | 2024-05-03 | 杭州沃趣科技股份有限公司 | Method, device, equipment and medium for automatically correcting database after storage recovery |
| CN115048046A (en) * | 2022-05-26 | 2022-09-13 | 北京华昱卓程软件有限公司 | Log file system and data management method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102955720B (en) | 2015-09-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102955720B (en) | A kind of method improving ext file system stability | |
| US10503616B2 (en) | Periodic data replication | |
| CN102891849B (en) | Service data synchronization method, data recovery method, data recovery device and network device | |
| CN102024016B (en) | Rapid data restoration method for distributed file system (DFS) | |
| CN101888405B (en) | Cloud computing file system and data processing method | |
| CN102033786B (en) | Method for repairing consistency of copies in object storage system | |
| US7844643B2 (en) | Storage management system with integrated continuous data protection and remote copy | |
| KR101352959B1 (en) | Apparatus and method for database management in active and standby nodes of main memory database management system | |
| US20150213100A1 (en) | Data synchronization method and system | |
| US20090292947A1 (en) | Cascading index compression | |
| CN101453489B (en) | Network additive storage device, data backup and data restoration method thereof | |
| US7853571B2 (en) | Techniques for file system recovery | |
| WO2018098972A1 (en) | Log recovery method, storage device and storage node | |
| CN102207897B (en) | Incremental backup method | |
| EP2590078B1 (en) | Shadow paging based log segment directory | |
| US7487385B2 (en) | Apparatus and method for recovering destroyed data volumes | |
| CN111078667B (en) | Data migration method and related device | |
| KR20150130496A (en) | Fast crash recovery for distributed database systems | |
| CN103516736A (en) | Data recovery method of distributed cache system and a data recovery device of distributed cache system | |
| CN102314503A (en) | Indexing method | |
| CN105426427A (en) | MPP database cluster replica realization method based on RAID 0 storage | |
| CN105302667A (en) | Cluster architecture based high-reliability data backup and recovery method | |
| CN109684338A (en) | A kind of data-updating method of storage system | |
| CN103516549A (en) | File system metadata log mechanism based on shared object storage | |
| US7000083B2 (en) | Resynchronization of count key data with its corresponding meta data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150909 Termination date: 20190825 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |