Storage Array Emulation Layer for Mixed 512N and 4K Sector Drives

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The transition from 512-byte sector drives to 4 kByte sector drives poses challenges for existing systems, particularly incompatibility with Microsoft Operating Systems up to Windows Server 2008 and many applications, leading to difficulties in migration and requiring costly and risky emulation methods to support 4 kN drives, which are error-prone and incur significant overhead.

Innovation Solution

Implementing an emulation solution within a storage array that dissociates physical sector boundary schemes from internal and logical sector boundary schemes, allowing for the simultaneous use of 512N and 4 kN drives in a RAID array, thereby supporting unaligned I/O operations with reduced costs and risks by combining RAID read-modify-write operations into a single action.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If drives with 4 k sectors are used, then capacity and overhead are improved, but compatibility with existing systems and applications deteriorates

Engineering Contradiction:
Improvedrive capacityVSAvoidsystem compatibility
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent introduces a translation layer that acts as an intermediary between the host system and the 4k native drive. This translation layer receives 512-byte sector I/O requests from legacy systems and translates them into 4k-byte sector operations on the physical drive, enabling compatibility without modifying either the host system or the drive hardware.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the sector size parameter from 512 bytes to 4096 bytes at the physical drive level while maintaining 512-byte logical sector presentation to hosts. This parameter transformation allows the system to benefit from larger physical sectors while preserving compatibility with legacy applications expecting 512-byte sectors.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If drive-based emulation is implemented, then compatibility with legacy systems is improved, but overhead and complexity increase

Engineering Contradiction:
Improvelegacy system compatibilityVSAvoidemulation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the emulation functionality from the drive firmware and relocates it to the host system software. This extraction simplifies the drive to a straightforward 4k native device while moving the translation complexity to the host, where it can be implemented as a software layer without modifying the drive hardware or firmware.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If unaligned I/O operations are supported, then flexibility and adaptability are improved, but performance and overhead worsen

Engineering Contradiction:
ImproveI/O flexibilityVSAvoidI/O performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent performs preliminary actions by pre-reading data from the drive before unaligned write operations. When a write request targets a location that doesn't align with 4k sector boundaries, the system first reads the containing sector into memory, performs the write operation on the in-memory data, and then writes back the modified sector. This preliminary read action enables flexible unaligned I/O while maintaining performance by avoiding multiple drive operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10346059B2System and method for supporting read requests and write requests for drives having different sector alignments without a RAID
Publication Date: 2019.07.09 DELL PROD LP
  • US10346059B2 patent drawing
  • US10346059B2 patent drawing
  • US10346059B2 patent drawing

AI summary

In one embodiment, a method includes receiving an input/output (I/O) request for data that starts or ends at a location other than a physical sector boundary of the device. The method further includes reading, starting at a first physical sector boundary before a beginning location specified in the I/O request and ending at a second physical sector boundary after an ending location specified in the request.