File System Read-Only Access During FSCK Repair
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional file system repair methods, such as FSCK, require bringing the file system offline for an extended period, making files inaccessible to users during the repair process, which can last for hours, leading to unacceptable downtime.
Innovation Solution
Providing read-only access to the file system while running FSCK, allowing users to access files without interfering with the repair process by writing corrupted blocks to a secondary storage device, and using a bitmap to track repaired blocks for later write-back.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the file system is brought offline for FSCK repair, then data integrity is ensured, but file accessibility to users is lost
Solution Approach 1:
The patent segments the file system into two operational modes: a read-only mode for users accessing original files, and a repair mode for FSCK operations on corrupted blocks. This segmentation allows simultaneous user access and repair operations without interference, resolving the contradiction between maintaining data integrity and ensuring file accessibility.
Solution Approach 2:
The patent introduces an intermediary mechanism (the read-only mount option and block device separation) that mediates between user file access requests and FSCK repair operations. Users access files through a read-only mounted file system, while FSCK operates independently on the underlying block device, allowing both operations to coexist without conflict.
2Manufacturing precision
If the file system is brought offline for FSCK repair, then repair accuracy is improved, but downtime increases
Solution Approach 1:
The patent enables continuous useful action by allowing the file system to remain mounted in read-only mode during FSCK repair operations. Users can continue to access files without interruption while repairs are performed in the background, eliminating the downtime traditionally associated with file system repairs while maintaining repair accuracy through the read-only constraint.
Solution Approach 2:
The patent introduces dynamic operation modes for the file system: read-only mode for user access, repair mode for FSCK operations, and a transition mechanism between these modes. This dynamic approach allows the system to adapt its operational state based on whether user access or repair operations are prioritized, reducing overall downtime while maintaining repair accuracy.
3Productivity
If users can access files during repair, then availability is improved, but repair interference risk increases
Solution Approach 1:
The patent applies local quality by giving different access permissions to different parts of the file system: read-only access for user operations and read-write access for FSCK repair operations on corrupted blocks. This localized permission differentiation allows users to access available files while preventing them from interfering with the repair process on corrupted blocks.
Solution Approach 2:
The patent performs preliminary action by mounting the file system in read-only mode before FSCK repair operations begin. This preliminary read-only mounting prevents users from writing to or modifying corrupted blocks during the repair process, eliminating repair interference risk while still allowing users to read and access files that are not being repaired.
Data Source
AI summary
An improved technique involves providing read-only access to the file system while FSCK is running. After a storage processor detects corrupted data in the file system, the storage processor brings the file system offline and provides FSCK with read-only access to the file system. The storage processor then begins a repair process on the disk by starting to run FSCK, which writes corrupted blocks to a secondary storage device. Upon receiving a request from a user for access to a file in the file system, the storage processor mounts the file system with read-only access. Upon completion of FSCK, the storage processor brings the file system offline, applies the corrected blocks from secondary storage to the blocks in primary storage, and brings the file system online with full read and write access.