CN102955720B - A kind of method improving ext file system stability - Google Patents
A kind of method improving ext file system stability Download PDFInfo
- Publication number
- CN102955720B CN102955720B CN201110247222.XA CN201110247222A CN102955720B CN 102955720 B CN102955720 B CN 102955720B CN 201110247222 A CN201110247222 A CN 201110247222A CN 102955720 B CN102955720 B CN 102955720B
- Authority
- CN
- China
- Prior art keywords
- file system
- read
- information
- backup
- disk
- 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.)
- Expired - Fee Related
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a kind of method improving ext file system stability, the method improves the stability of ext file system in disk drive process, and described method comprises following steps: periodically or unloading disk time in this disk the information of backup disk file system; When carry disk partition, if carry procedure failure, according to the information of backup, attempt carry again, if failure again, then terminate carry flow process; Wherein, the packets of information of described file system contains: superblock, chunk and root nodal information.Described method also comprises: synchronous treatment step when carrying out read-write operation to disk file.Described synchronous treatment step is: when carrying out read-write operation to disk file system, in real time read-write requests in core buffer is issued storage medium, be sent to device driver by all data do not write in buffer area that leave in, and then be sent to memory device, complete synchronous operation; Wherein, read-write operation comprises: create file or deleted file etc.
Description
Technical field
The present invention relates to a kind of software mechanism method realizing the optimization of embedded file system, be specifically related to a kind of method improving ext file system stability.
Background technology
In the society of this high speed development, the demand of people is also more and more higher, and current video field is all towards high definition future development, although Video coding compression factor has optimization, file is increasingly inevitable, like this must by hard-disc storage; Cause various Set Top Box, industrial computer etc. more and more higher to the reliability requirement of file system like this.Current employing operating system or linux operating system, the file system of employing is generally ext file system, and as EXT2, EXT3, EXT4, wherein EXT2 does not have journal function, EXT3 and EXT4 has journal function.
But; hard disk is in long-term use procedure; often there will be the situations such as file system crash, File lose, file error; the form of expression of fault is different; for the hard disk that store significant 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 caused is a lot, and modal a kind of situation is then that system exception power-off causes, and especially when writing data, power-off is then more dangerous.
Read for dish speed relative to hard disk, the stability of the file system of hard disk seems more important.In other words, stable file system performance is the read-write prerequisite of file.Hard disk is fixed memory device; under normal circumstances in embedded system without any protection, therefore in repeatedly use procedure, there will be the phenomenon such as file system crash, loss of data unavoidably; these defect all can affect the reading of data, thus affect the use of whole product.The subject matter occurred: 1) file system crash, all loss of datas; 2) can again occur after the file power-off of deleting; 3) disappear again after the file power-off created; 4) partial document is lost, input/output error problem.
The stability of file system can be improved from software and hardware two aspects.Method conventional on hardware adds UPS or adopts single-chip microcomputer, this technology is not also very ripe, the effect of UPS is by reminding user safety shutdown Backup Data before system cut-off, the effect of single-chip microcomputer is before power-off, by electric capacity delay switching-off, notify mainboard safety shutdown Backup Data, these two kinds of method costs are all higher simultaneously.Software has plenty of adopt and carry out dual-host backup from application program level to hard disc data, what have is then adopt privately owned file system, is processed by certain verification scheme.Or by third party's instrument, as fsck, e2fsck etc., self-inspection and reparation are carried out to file system.But this instrument can cause certain destruction to file system, and repair time is very long.
Prior art is only once attempted in carry disk partition, lacks corresponding fault-tolerant processing mechanism thus causes the stability of disk file system very poor; In addition, at present based on the file system crash that the disk file system of current EXT causes due to reasons such as abnormal power-down, all loss of datas; Can again occur after the file power-off of deleting; Disappear again after the file power-off created; 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, thus providing a kind of method improving ext file system stability.
For achieving the above object, the invention provides a kind of method improving ext file system stability, the method improves the stability of ext file system in disk drive process, and described method comprises following steps:
Step 1, periodically or unloading disk time in this disk the information of backup disk file system.
Step 2, when carry disk partition, if carry procedure failure, according to the information of backup, attempts carry again, if failure again, then exits carry flow process; Wherein, the packets of information of described file system contains: superblock, chunk and root nodal information.
Optimize, described method also comprises: synchronous treatment step when carrying out read-write operation to disk file.
Optionally, described synchronous treatment step is: when carrying out read-write operation to ext file system, in real time read-write requests in core buffer is issued storage medium, is sent to device driver by all data do not write in buffer area that leave in, and then be sent to memory device, complete synchronous operation; Wherein, described read-write operation comprises: create file, deleted file, create directory, deltree, create link, delete link, file rename and catalogue rename, be flexible coupling, hard link or written document.
Further optimization, if when described disk file system is Journaling File System, it is synchronous that described synchronous process also comprises daily record, namely real-time the log information deposited in the buffer is synchronized to storage medium; And the information of described file system also comprises Journal node information.
In technique scheme, described step 2 comprises following steps further:
Step 2-1, reads the superblock of zero block group, reads successfully, enters next step; Otherwise read backup superblock information from disk partition, read and unsuccessfully exit carry flow process; If read the success of backup superblock, backup superblock is returned to the superblock position of zero block group, again read the superblock of zero block group, read successfully, enter next step, otherwise exit carry flow process;
Step 2-2, reads the group descriptor of zero block group, reads and successfully enters next step; If unsuccessfully read backup group descriptor information, read and unsuccessfully exit carry flow process; Successful then backup group descriptor is returned in zero block group, and again read the group descriptor of zero block group, read and successfully enter next step, otherwise exit carry flow process;
Step 2-3, reads the root nodal information of zero block group, if successfully enter next step; Otherwise judge to there is backup root nodal information, do not exist, exit carry flow process; If exist, then backup root nodal information is returned to the corresponding root nodal information position of zero block group; Read the root nodal information of zero block group, read and successfully enter next step, otherwise exit carry flow process.
Optimize, if file system is Journaling File System, then, between above-mentioned steps 2-2 and step 2-3, comprise following steps further: the Journal node information reading zero block group, if successfully enter next step; If failure, judges whether to there is backup log nodal information, does not exist and exit; Exist and then backup log nodal information is returned in zero block group, read the Journal node information of zero block group, read and successfully enter next step, otherwise exit carry flow process.
In 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, relative to strategy on the hardware that prior art adopts, cost is low, and realize simple, the time is short; And relative to the method that other solves from software, the present invention does not need the application program that bespoke is new, mechanism is simple, does not need complicated verification scheme, only needs on the basis of original disk driver, slightly adjust the stability that just can improve disk file system; Meanwhile, also there is larger versatility, can apply on different platforms (comprising ext2 and ext3, ext4); This mechanism greatly reduces the difficulty of exploitation.In sum, the invention provides the implementation method optimizing ext file system, comprise file system important data backup mechanism, also can normal carry during disk crash, and update in disk to the I/O operation of file system, ensure that the up-to-date of data in disk, and it is very little to affect magnetic disc i/o performance, provides the complete scheme of the stability improving embedded file system.Overcome existing EXT file system and easily occur file system crash, File lose, corrupted data phenomenon, realize file system and stablize, this software level of slave driver improves the scheme of Ext file system stability.
Accompanying drawing explanation
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 of the present invention operation and synchronous operation;
Fig. 3 is the process flow diagram of the flow process of linux ext3 file system of the present invention unloading hard disk and the process of backup 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 realizing ext document system optimization, comprise the steps:
1), during carry disk partition, if can normal carry, then return carry success, exit carry flow process; If first time carry failure, then recover superblock, chunk information, root nodal information and Journal node information from backup region, then carry out carry, carry success, exits carry flow process, returns carry success; Otherwise return carry failure, stop again carry to attempt;
2) I/O of file operation is added synchronously process operation;
3) timing or unloading hard disk time backup superblock, chunk information, root nodal information, Journal node information, this step is described step 1) first time report the loss and lose time carry out again carry attempt needed for information.
In such scheme, described step 1) and step 3) there is positive connection.In step 3) in carry out backup operation, can in step 1) in, when there is mistake, restore.
The implementation method of the raising ext file system stability that the present embodiment provides, comprising: the fault-tolerant processing mechanism in carry disk partition process, and this mechanism further based on during to timing or unloading disk, carries out back-up processing strategy to information such as disk superblocks again; Synchronous processor system when read-write operation carries out to disk file.
For ext file system, fdisk is divided into block one by one, and each block in an 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 is determined when establishment ext file system, and it can be specified by system manager, also by the size of the creation procedure of file system according to fdisk, automatically can select one and be more reasonably worth.The 1024bytes that subregion starts deposits boot boot, ensuing 1024bytes deposits superblock (super block), group describing word (group descriptors) originates in a new block, and take separately a block space, afterwards all pieces are organized into block group, and block group is only the place of real storing documents.Superblock (super block) some global parameters containing whole file system, as: file label, Globally Unique Identifier, state, block size, total block data, often group 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 for most important file system.Refer to following form:
Carry disk partition is exactly that driver operates disk partition, i.e. common block device driver read requests operation, the normal read operation of the ext file system with daily record specifically comprises: (1) reads superblock information, authenticating documents system type; (2) read and verify that group descriptor information (3) reads and checking journal inode; (4) read and verify root inode.
In technique scheme 1) in, further, each step may be failed, if failure, then processes respectively.Ext file system is that superblock has reserved backup region, generally in first piece of the 1st, 3,5,7,9 piece of group.The present invention adopts the set of tiles (block group) in above reserved backup region.The numbering of block group is from 0, and namely first piece of group is the 0th block group.
Be the 3rd block group for backup address below, composition graphs 1 is specifically described.
Embodiment 1
Step 11, reads the superblock of the 0th block group, reads successfully, enter next step; Otherwise read backup superblock (first piece of the 3rd block group), read backup superblock and unsuccessfully exit carry flow process; If read the success of backup superblock, backup superblock is returned to the superblock position of the 0th block group, again read the superblock of the 0th block group, read and successfully enter next step, otherwise exit carry flow process.
Step 12, reads the group descriptor of the 0th block group, is proved to be successful and enters next step; If unsuccessfully read backup group descriptor information (second block of the 3rd block group), authentication failed exits carry flow process; Be proved to be successful, backup group descriptor returned in the 0th block group, and again read the group descriptor of the 0th block group, read and successfully enter next step, otherwise exit carry flow process;
Step 13, reads the root nodal information of the 0th block group, if successfully enter next step; Otherwise judge backup mark, see whether backup root nodal information exists, and does not exist, exits carry flow process; If exist, then backup root nodal information is returned to the corresponding root nodal information position of the 0th block group.Read the root nodal information of the 0th block group, read and successfully enter next step, otherwise exit carry flow process.
Wherein, if adopt file system to be ext3 or ext4, these two file system are Journaling File System, so between above-mentioned steps 12 and step 13, comprise following steps further:
Read the Journal node information of the 0th block group, if successfully enter next step; If failure, judge backup mark, see whether there is backup log nodal information, do not exist and exit; Exist and then backup log nodal information is returned in the 0th block group, read the Journal node information of the 0th block group, read and successfully enter next step, otherwise exit carry flow process.
The specific implementation of the back-up processing mechanism of the superblock described in above-described embodiment, chunk, Journal node information, root nodal information is operating as: backup superblock, chunk information, root nodal information, Journal node information when timing or unloading (do_mount) hard disk, also can normal extension dish when guaranteeing disk crash.Backup address can be Ext file system is the disk management space that keeper retains.As in embodiment 1 the 3rd block group position mentioning, just can as backup region.
Specific implementation is as shown in Figure 3:
Step 31 backs up the corresponding root nodal information storeroom of root inode to the 3rd block group, and juxtaposition one mark, as " Intellix-root ", indicates and whether backed up root inode.
Step 32 backup group descriptor is to the group descriptor storeroom of the 3rd block group.
Step 33 backs up superblock to first piece of the 3rd block group.
Technique scheme 3) in, if adopt file system to be ext3 or ext4, these two file system are Journaling File System, so between above-mentioned steps 31 and step 32, comprise following steps further
Backup journal inode is to the corresponding Journal node information storeroom of the 3rd block group, and juxtaposition one mark, as " Intellix-journal ", indicates and whether backed up journal inode.
Embodiment 2
Because 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 realizes, for user's space provides unified file operation interface.Each file system realizes derivation one group of general-purpose interface, for VFS.Buffer zone is used for cache file system and the request therebetween of related blocks equipment.Namely can be transmitted 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 buffer zone is not performed, by abnormal power-down, just likely there will be 1) file system crash, all loss of datas; 2) can again occur after the file power-off of deleting; 3) disappear again after the file power-off created; 4) partial document is lost, the problems such as input/output error.For avoiding the problems referred to above, when write operation is carried out to disk, namely revise superblock, chunk, block bitmap, inode bitmap, during the metadata such as inode table, just need to do synchronous operation to internal memory, in time request in buffer zone is issued storage medium, to reduce 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 operation such as hard link, written document
Sync order is that the request in buffer cache is sent to medium, forces all data do not write to be sent to device driver, and then is sent to memory device, can reach synchronous object.
For ext3 and ext4 file system, there is journal function, because also using buffering to the operation of daily record, so need to carry out synchronous operation, log information is synchronized to disk from buffer area in time.Synchronous object can be reached to synchronous mark position (S_SYNC) set of the i_flags parameter in node structure body.
Specific implementation combines and creaties directory as example illustrates.As shown in Figure 2:
Step 21, user application will create directory (mkdir) on disk, just will call core system entrance (sys_mkdir), call virtual file system interface (vfs_mkdir) again, find the function that creaties directory (ext3_mkdir) of concrete file system.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 record can be lost.This just needs the journal system in ext3 to do synchronous operation.As (the dir-> i_flags|=S_SYNC) operation in Fig. 2 has come,
Step 22, after exiting daily record atomic operation, is synchronized to disk (sync) in time by the request of buffer zone.
First, above-described embodiment 2 can be implemented with embodiment 1 simultaneously, and namely those skilled in the art can improve disk file system stability further by the backup information of embodiment 1 with based on the synchronization policy that the application of policies of backup carry disk partition adopts embodiment 2 to mention again 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 of existing disk file system.
It should be noted that, embodiment of the present invention of above introduction and and unrestricted.It will be understood by those of skill in the art that any amendment to technical solution of the present invention or the equivalent alternative spirit and scope not departing from technical solution of the present invention, it all should be encompassed in right of the present invention.
Claims (5)
1., for improving a method for the ext file system stability of embedded system, the method improves the stability of embedded ext file system in disk drive process in disk drive process, and described method comprises following steps:
Step 1, periodically or unloading disk time in this disk the information of backup disk file system;
Step 2, when carry disk partition, if carry procedure failure, according to the information of backup, attempts carry again, if failure again, then exits carry flow process; Wherein, the packets of information of described file system contains: superblock, chunk and root nodal information;
Described step 2 comprises following steps further:
Step 2-1, reads the superblock of zero block group, reads successfully, enters next step; Otherwise read backup superblock information from disk partition, read and unsuccessfully exit carry flow process; If read the success of backup superblock, backup superblock is returned to the superblock position of zero block group, again read the superblock of zero block group, read successfully, enter next step, otherwise exit carry flow process;
Step 2-2, reads the group descriptor of zero block group, is proved to be successful and enters next step; If unsuccessfully read backup group descriptor information, read and unsuccessfully exit carry flow process; Successful then backup group descriptor is returned in zero block group, and again read the group descriptor of zero block group, read and successfully enter next step, otherwise exit carry flow process;
Step 2-3, reads the root nodal information of zero block group, if successfully enter next step; Otherwise judge backup mark, see whether backup root nodal information exists, and does not exist, exits carry flow process; If exist, then backup root nodal information is returned to the corresponding root nodal information position of zero block group; Read the root nodal information of zero block group, read and successfully enter next step, otherwise exit carry flow process;
Wherein, if file system is Journaling File System, then, between above-mentioned steps 2-2 and step 2-3, following steps are comprised further:
Read the Journal node information of zero block group, if successfully enter next step; If failure, judge backup mark, see whether backup log nodal information exists, do not exist and exit; Exist and then backup log nodal information is returned in zero block group, read the Journal node information of zero block group, read and successfully enter next step, otherwise exit carry flow process;
The backup of described superblock information, group descriptor information, root nodal information is in the headspace of disk.
2. the method for the ext file system stability for improving embedded system according to claim 1, it is characterized in that, described method also comprises: synchronous treatment step when carrying out read-write operation to disk file.
3. the method for the ext file system stability for improving embedded system according to claim 2, it is characterized in that, described synchronous treatment step is: when carrying out read-write operation to ext file system, in real time read-write requests in core buffer is issued storage medium, device driver is sent to by all data do not write in buffer area that leave in, and then be sent to memory device, complete synchronous operation;
Wherein, described read-write operation comprises: create file, deleted file, create directory, deltree, create link, delete link, file rename and catalogue rename, be flexible coupling, hard link or written document.
4. the method for the ext file system stability for improving embedded system according to Claims 2 or 3, it is characterized in that, if when described disk file system is Journaling File System, it is synchronous that described synchronous process also comprises daily record, namely real-time the log information deposited in the buffer is synchronized to storage medium.
5. the method for the ext file system stability for improving embedded system according to claim 1,2 or 3, it is characterized in that, if described disk file system is Journaling File System, the information of described file system also comprises Journal node information.
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 CN102955720A (en) | 2013-03-06 |
| CN102955720B true 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) |
Families Citing this family (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 |
| CN105068889B (en) * | 2015-08-03 | 2018-05-25 | 四川效率源信息安全技术股份有限公司 | Recover the method for complete deletion file in Ext3/Ext4 |
| 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 |
| CN105956172B (en) * | 2016-05-23 | 2019-08-13 | 深圳市硅格半导体有限公司 | The storage method and device of log information |
| 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 |
| 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 |
| CN108089818B (en) * | 2017-12-12 | 2021-09-07 | 腾讯科技（深圳）有限公司 | Data processing method, device and storage medium |
| 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 |
| 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 |
| CN110941515B (en) * | 2019-12-04 | 2022-05-24 | 深圳市科力锐科技有限公司 | Host backup reconstruction method, device, server and storage medium |
| CN113419897B (en) * | 2021-01-19 | 2023-12-22 | 阿里巴巴集团控股有限公司 | File processing method and device, electronic equipment and storage medium thereof |
| CN113778753B (en) * | 2021-09-14 | 2024-05-03 | 杭州沃趣科技股份有限公司 | Method, device, equipment and medium for automatically correcting database after storage recovery |
| CN115048046B (en) * | 2022-05-26 | 2022-11-25 | 北京华昱卓程软件有限公司 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102955720A (en) | 2013-03-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102955720B (en) | A kind of method improving ext file system stability | |
| CN102891849B (en) | Service data synchronization method, data recovery method, data recovery device and network device | |
| US9690823B2 (en) | Synchronizing copies of an extent in an append-only storage system | |
| US9588858B2 (en) | Periodic data replication | |
| CN102012851B (en) | Continuous data protection method and server | |
| US9910592B2 (en) | System and method for replicating data stored on non-volatile storage media using a volatile memory as a memory buffer | |
| CN101453489B (en) | Network additive storage device, data backup and data restoration method thereof | |
| CN102033786B (en) | Method for repairing consistency of copies in object storage system | |
| US9772783B2 (en) | Constructing an index to facilitate accessing a closed extent in an append-only storage system | |
| US7853571B2 (en) | Techniques for file system recovery | |
| CN104077380B (en) | A kind of data de-duplication method, apparatus and system | |
| CN102207897B (en) | Incremental backup method | |
| US7487385B2 (en) | Apparatus and method for recovering destroyed data volumes | |
| CN105426427A (en) | MPP database cluster replica realization method based on RAID 0 storage | |
| CN103516549B (en) | A kind of file system metadata log mechanism based on shared object storage | |
| KR101922044B1 (en) | Recovery technique of data intergrity with non-stop database server redundancy | |
| US9720607B2 (en) | Append-only storage system supporting open and closed extents | |
| CN102314503A (en) | Indexing method | |
| CN110196818A (en) | Data cached method, buffer memory device and storage system | |
| CN109684338A (en) | A kind of data-updating method of storage system | |
| US10642508B2 (en) | Method to limit impact of partial media failure of disk drive and detect/report the loss of data for objects due to partial failure of media | |
| CN113885809B (en) | Data management system and method | |
| CN102385624B (en) | DFS (distributed file system)-oriented log data organization method | |
| CN114020686A (en) | File snapshot synchronization method, system, device and medium based on difference log | |
| CN104991739A (en) | Method and system for refining primary execution semantics during metadata server failure substitution |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150909 Termination date: 20190825 |