Peer Storage Protection Information Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Peer-to-peer storage systems face challenges in implementing end-to-end data protection information, particularly during data transfers that do not involve a host or storage controller, leading to issues with missing or altered data integrity fields.
Innovation Solution
A storage system comprising peer storage devices with check code engines and comparators to calculate and verify guard tags, reference tags, and application tags using a protection information data block format, ensuring data integrity through a peer communication channel.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If peer-to-peer data transfers are implemented without host or storage controller involvement, then system autonomy and performance are improved, but data integrity verification becomes unreliable due to missing or altered protection information
Solution Approach 1:
The source storage device performs preliminary actions by calculating and attaching protection information (guard tag, application tag, reference tag) to data blocks before peer-to-peer transfer. This ensures data integrity verification capability is established in advance, allowing the destination device to verify received data without requiring host or controller involvement during the actual transfer.
Solution Approach 2:
Protection information fields act as intermediaries between source and destination storage devices during peer-to-peer transfers. These fields (guard tag with CRC, application tag, reference tag) carry verification data that enables the destination device to validate received data blocks, effectively mediating the trust relationship without requiring host or controller participation.
2Reliability
If data integrity fields are extended from 512 bytes to 520 bytes to include protection information, then end-to-end data protection is improved, but device complexity and processing overhead increase
Solution Approach 1:
The protection information is segmented into distinct functional fields: guard tag (2 bytes for CRC), application tag (2 bytes for application-level verification), and reference tag (4 bytes for block identification). This segmentation allows each component to perform its specific verification function independently, simplifying the overall processing logic despite the increased data block size to 520 bytes.
3Reliability
If peer storage devices perform autonomous data operations with full protection information verification, then data reliability is improved, but computational overhead and processing time increase
Solution Approach 1:
The verification process performs partial checking by focusing on critical fields: the guard tag CRC verification provides fundamental error detection, while reference tag verification ensures block identity correctness. This partial verification approach achieves sufficient reliability for peer-to-peer transfers without requiring exhaustive validation of all data block attributes, reducing processing time overhead.
Data Source
AI summary
Example storage systems, storage devices, and methods provide secure transfer of data between peer storage devices using protection information. Data operation commands may be received that use a protection information data block format for transferring a target data block between peer storage devices. A local data operation may operate on the target data block in a first storage device and compare at least one protection information tag value to a first data check value. At least one destination verification protection information tag value and the target data block may be transferred to a second storage device through a peer communication channel. The destination verification protection information tag value may be compared to a destination data block protection information tag value by the second storage device. The second storage device may then execute a data operation on the target data block. Protection information tag values may include guard tag values, reference tag values, and application tag values managed by the peer storage devices.