Slice Consistency Check via Majority Voting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional slice consistency checks in data storage systems do not adequately consider filesystem ownership, leading to potential failures if ownership is incorrectly determined, and both slice maps and marks can contain mistaken data due to shared management.
Innovation Solution
Implementing a majority voting algorithm that gives one vote to the filesystem management layer, one vote to the sparse metavolume management layer (combining slice map and slice marks views), and one vote to the slice management layer to determine slice ownership.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional slice consistency check is performed without filesystem ownership verification, then the check process is simpler and faster, but the accuracy of slice ownership determination deteriorates leading to potential filesystem failures
Solution Approach 1:
The slice consistency check is divided into multiple independent voting sources: filesystem manager vote, slice map vote, and slice marks vote. Each source independently determines slice ownership, and their results are combined through majority voting to achieve reliable ownership determination without requiring a single complex verification mechanism.
Solution Approach 2:
The system implements a feedback mechanism where the results from multiple voting sources (filesystem manager, slice map, slice marks) are collected and processed to determine the final slice ownership. The majority voting algorithm provides feedback validation, ensuring that ownership assignment is consistent across all management layers before finalizing the assignment.
2Measurement precision
If slice map and slice marks are managed by the same software layer, then management is simpler, but the accuracy of ownership information deteriorates as both can contain the same mistaken data
Solution Approach 1:
The management of slice ownership information is segmented into separate functional components: the slice map managed by the sparse metavolume management layer and the slice marks managed by the filesystem management layer. This segmentation ensures that errors in one component do not propagate to the other, improving the accuracy of ownership determination through diversified data sources.
3Reliability
If filesystem management layer perspective is not included in slice consistency check, then the check process is simpler, but the correctness of slice ownership assignment deteriorates
Solution Approach 1:
The ownership determination results from multiple independent sources (filesystem manager, slice map, slice marks) are merged through a majority voting algorithm. This combining approach integrates the filesystem management layer perspective with other management layers, ensuring correct slice ownership assignment by requiring consensus among multiple sources rather than relying on a single perspective.
Data Source
AI summary
A slice consistency check method is presented including, for each slice of a plurality of slices (a) obtaining a first vote for ownership of that slice according to a filesystem manager configured to manage a set of filesystems stored on a set of sparse metavolumes, (b) obtaining a second vote for the ownership of that slice according to a first driver, the first driver being independent of the filesystem manager, (c) obtaining a third vote for the ownership of that slice according to a second driver, the second driver being independent of the filesystem manager and the first driver, and (d) assigning ownership of that slice based on a majority vote of the first vote for the ownership of that slice, the second vote for the ownership of that slice, and the third vote for the ownership of that slice.