Shared Content Mappings for Synchronous Storage Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage systems face inefficiencies in managing data storage and retrieval operations, particularly in flash storage systems where lower-level processes are often involved, leading to unnecessary write operations and reduced reliability.
Innovation Solution
Implementing a direct-mapped flash storage system where higher-level operating systems manage data blocks directly, eliminating the need for address translation by lower-level storage controllers, and utilizing non-volatile random access memory (NVRAM) for faster data buffering and power loss protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If lower-level storage controllers perform address translation and data management, then data retrieval is possible, but redundant write operations occur and reliability decreases
Solution Approach 1:
The patent extracts the address translation function from the storage controller and relocates it to the operating system. The storage controller is reduced to a simple interface that only handles raw data transfer, while the OS manages the mapping between logical block addresses and physical flash memory locations. This eliminates redundant write operations caused by controller-level address translation and improves reliability.
Solution Approach 2:
The operating system performs self-service by directly managing flash memory operations including wear leveling, bad block management, and address translation. This removes the need for complex lower-level storage controllers to perform these functions, reducing redundant writes and improving system reliability while maintaining necessary functionality.
2Speed
If traditional storage controllers manage data blocks, then data storage is possible, but write operations are redundant and latency increases
Solution Approach 1:
The patent extracts data block management responsibilities from the storage controller and assigns them to the operating system. This eliminates multiple layers of indirection and redundant write operations, directly reducing latency and improving data access speed.
Solution Approach 2:
The operating system performs preliminary actions by pre-managing flash memory wear leveling and bad block relocation before actual write operations occur. This prevents redundant writes during normal operation, reducing latency and improving overall write speed.
3Reliability
If non-volatile memory is used for buffering, then power loss protection is improved, but memory capacity is reduced
Solution Approach 1:
The patent transitions from using volatile RAM for buffering to using non-volatile flash memory for the same purpose. This dimensional change in memory type provides power loss protection while maintaining sufficient buffering capacity through the OS-managed mapping system that efficiently utilizes available non-volatile memory space.
Solution Approach 2:
The operating system changes the parameter of memory volatility by implementing a file system and block management layer that operates on non-volatile memory. This provides power loss protection while the OS manages the effective capacity and allocation of non-volatile memory buffers to maintain adequate buffering capability.
Data Source
AI summary
Synchronizing metadata among storage systems synchronously replicating a dataset, where synchronizing the metadata includes: receiving, at a first storage system of the storage systems, an I/O operation directed to the dataset; determining, in dependence upon the I/O operation, a metadata update describing a mapping of segments of content to a virtual address within a storage object, wherein the storage object includes the dataset; and synchronizing metadata on a second storage system of the storage systems by sending the metadata update to the second storage system to update a metadata representation on the second storage system in accordance with the metadata update.