Abstract

One of the most critical threats to the reliability and robustness for file system is harboring bug (silent data corruption). In this research we focus on checksum mismatch since it occurs not only in the user data but also in file system. Our proposed solution has the ability to check this bug in file system of Linux. In our proposed solution there is no need to invoke or revoke checker utility, it comes as the integrated part of file system and has the ability to check upcoming updates before harboring bug make unrecoverable changes that leads significant data loses. Demonstration testing shows satisfactory results in file server and web server environments in terms of less memory consumption and avoidable delay in system’s updating.

Highlights

  • File system is the major part of computer system which must be robust, reliable and intelligent enough that can handle faults and bugs

  • In this research we focus on checksum mismatch since it occurs in the user data and in file system

  • In our proposed solution there is no need to invoke or revoke checker utility, it comes as the integrated part of file system and has the ability to check upcoming updates before harboring bug make unrecoverable changes that leads significant data loses

Read more

Summary

Introduction

File system is the major part of computer system which must be robust, reliable and intelligent enough that can handle faults and bugs. Fixed file system journaling defends the ordering of meta-data processes to maintain consistency in the occurrence of crashes. The long structured memory policy has two types of benefits that can increase the speed and clean the memory from garbage that is responsible to make latency in file read and written in primary memory. It increases the speed of the bandwidth of memory up to 6×. The fault tolerance and rapid fault discovery for both hardware and software is key structure blocks for building always accessible applications. MDS has a unique feature but can create problem when it is used for long length code so some scientist offered XI-Code in [6] to resolve this issue

Related Work
Significance of Esext3
Design and Implementation
Esext3 Performance Analysis
Meta-data operations
Limitations
Findings
Conclusion and Future Work

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.