Article ID: 000057368 Content Type: Product Information & Documentation Last Reviewed: 02/22/2022

What Is RAID 5 Write Hole (RWH) Protection in Intel® Virtual RAID on CPU (Intel® VROC)?

BUILT IN - ARTICLE INTRO SECOND COMPONENT
Summary

Explains the Intel® VROC feature RWH.

Description

RAID Write Hole (RWH) is a fault scenario, related to parity-based RAID. It occurs when a power-failure/crash and a drive-failure leg strip write or complete drive crash occur at the same time or very close to each other. Unfortunately, these system crashes and disk failures are correlated events. 

Resolution

Intel® Virtual RAID on CPU (Intel® VROC) can protect RAID 5 data even when both unexpected power loss and RAID volume degradation occur at the same time. This double fault condition is, at times, referred to as the RAID 5 write hole (R5WH). Many RAID solutions have dealt with this challenge by acquiring a backup power unit. Intel VROC addresses this problem by using patent-pending journaling.

There are two available modes of Intel® VROC RAID Write Hole protection:

  1. Distributed: The RAID Write Hole journal is stored on RAID member drives and there is no need for any additional drivers. This mode provides full protection against the RAID Write Hole but introduces a performance penalty for write-intensive workloads.
  2. Journaling Drive: The RAID Write Hole journal is stored on a separate Journaling Drive. That drive cannot be used for any other purpose. The performance penalty for write-intensive workloads depends on the performance of the Journaling Drive, but typically the penalty is lower compared to the Distributed mode.
Notes
  • The Journaling Drive needs to be at least as big as the smallest drive in the RAID volume (it will dictate the maximum size of the RAID volume).
  • For RWH protection, we recommend working in Distributed mode (where the journaling information is stored across all three RAID members) and not Journaling Drive mode (where journaling information is stored on a single drive).
  • Journaling is different than parity. Journaling happens first, even before the data is committed to the RAID 5 volume, and once the RAID 5 volume is ready, the journal is no longer needed.
  • The reason the Journaling Drive should be at least as large as the smallest drive member in RAID 5 is due to endurance considerations. While journaling does not actually require so much space, it does need to be written over again and again, requiring good endurance/capacity, and is what could make distributed journaling more effective.
  • Distributed journaling utilizes the PLI functioning of the drives, which is in turn using memory on the drive to store data instead of NAND, making endurance not a factor or concern anymore for journaling.
  • The other option is to use an Intel® Optane™ SSD as a dedicated journaling device, with much lesser capacity drive with much higher endurance (as a dedicated journaling solution).
Additional information

More information on supported configurations, features, integrated caching, how to buy, and support is available in Intel® Virtual RAID on CPU (Intel® VROC).

Related articles

Intel® Virtual RAID on CPU User Guide

Related Products

This article applies to 1 products

Intel® Virtual RAID on CPU (Intel® VROC)

Need more help?

Contact support

Disclaimer

1

All postings and use of the content on this site are subject to Intel.com Terms of Use.