Flash Memory Boot Partitioning for Wear Reduction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Flash memory devices have limitations in write-erase cycles, making them unsuitable for supporting complex systems, especially in virtualized environments where many virtual computing devices share a host platform, as they can only guarantee about 100,000 write-erase cycles, which is insufficient for long-term use.

Innovation Solution

A flash memory device is designed with a virtualization engine that manages writes transparently to the operating system, using a RAM-based file system to optimize system robustness within the write constraints of the flash device, with a read-only partition for the operating system and a read/write partition for storing deltas, minimizing writes by tracking changes and archiving them periodically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If flash memory is used as persistent storage for computing devices, then speed, noise reduction, power consumption, and durability are improved, but write-erase cycle limitations reduce the device lifespan and reliability

Engineering Contradiction:

Improveboot speedVSAvoiddevice lifespan

Core Design Contradiction:

SpeedVSDuration of action of stationary object

Solution Approach 1:

The flash memory device is divided into multiple partitions: a first partition containing an operating system and a second partition containing a file system. This segmentation allows the system to boot from the first partition while performing file operations on the second partition, thereby reducing write operations to the boot partition and extending its lifespan.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements a read-only file system mode during boot operations, where the file system is mounted as read-only to prevent any write operations to the flash memory during the boot process. This preliminary action ensures that the boot partition undergoes minimal wear while maintaining fast boot speeds.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If flash memory supports complex systems like operating systems and virtualized environments, then system functionality is improved, but the number of write operations increases beyond the 100,000 write-erase cycle guarantee

Engineering Contradiction:

Improvesystem compatibilityVSAvoidwrite cycle guarantee

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a dynamic file system that can switch between read-only and read-write modes. During normal operation, the file system operates in read-write mode to support complex systems and applications. However, during boot operations and when not in use, it switches to read-only mode, dynamically adjusting its behavior to minimize wear while maintaining full functionality when needed.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent changes the operational parameters of the file system by mounting it as read-only during boot operations and switching to read-write mode during normal operation. This parameter change allows the system to support complex applications while minimizing the frequency and intensity of write operations to the flash memory, thereby maintaining reliability within the write cycle guarantee.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If the entire file system is mounted as read-write to support system operations, then system robustness is improved, but wear on the flash memory increases

Engineering Contradiction:

Improvesystem robustnessVSAvoidmemory wear

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements periodic mounting of the file system as read-write only when necessary for specific operations, rather than maintaining it in read-write mode continuously. This periodic action allows the system to maintain robustness when needed while minimizing the cumulative wear on the flash memory by keeping the file system in read-only mode during boot and idle periods.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS8510542B2Flash memory device having memory partitions and including an embedded general purpose operating system for booting a computing device

Publication Date: 2013.08.13 ORACLE INT CORP

AI summary

Methods and apparatus involve booting a computing device from a flash device. The flash device has memory partitions, including a read-only and a read/write partition. The read-only includes an operating system for use by the computing device and defines an initial system state. The read/write is configured to store a delta from the initial system state. Upon booting the computing device subsequent to an initial boot, the delta and the initial system state together define the whole system state. In other features, a write engine from the read-only partition tracks changes to the initial system state and writes some, but not all of the changes back to the read/write partition thereby minimizing a number of writes to the flash memory. In this manner, the speed of the flash memory can be used to quickly boot/reboot a computing device, while avoiding the wear limits associated with writing to flash devices.