LSI manual SAS2 Integrated RAID Solution User Guide

Page 12

Chapter 2: Overview of Integrated RAID Mirrored Volumes Mirrored Volume Features

SAS2 Integrated RAID Solution User Guide

2.4.6Disk Write Caching

2.4.7NVSRAM Usage

2.4.8Background Initialization

2.4.9Consistency Check

2.4.10Make Data Consistent

By default, the Integrated RAID firmware disables disk write caching for mirrored volumes. It does this to ensure that the write journal entry stored in nonvolatile static RAM (NVSRAM) is always valid. If you enable disk write caching (not recommended), you may cause the disk write log to be invalid.

The Integrated RAID firmware requires at least a 32-KB NVSRAM to perform write journaling for mirrored volumes on LSI SAS2 controllers. The NVSRAM also preserves configuration information across reboots. The firmware uses write journaling to verify that the disks in the mirrored volume are synchronized with each other.

Background initialization (BGI) is the process of copying data from primary to secondary disks in a mirrored volume. The Integrated RAID firmware starts BGI automatically as a background task when it creates a volume. The volume remains in the Optimal state while BGI is in progress.

A consistency check is a background process that reads data from primary and secondary disks in a mirrored volume and compares it to make sure the data is identical on both disks. You can use the LSI SAS2 BIOS Configuration Utility to run a consistency check on a mirrored volume.

If it is enabled in the Integrated RAID firmware, the make data consistent (MDC) process starts automatically and runs in the background when you move a redundant volume from one SAS controller to another SAS controller. MDC compares the data on the primary and secondary disks. If MDC finds inconsistencies, it copies data from the primary disk to the secondary disk.

Page 12

LSI Corporation Confidential August 2010

Image 12
Contents SAS2 Integrated RAID Solution Revision History Table of Contents Table of Contents Introduction to the Integrated RAID Solution FeaturesOverview Enhanced RAID 1EBenefits and Features Overview of Integrated RAID Mirrored Volumes IntroductionTypes of mirrored arrays Operation of Mirrored Volumes Typical Integrated Mirroring Implementation Integrated Mirroring Enhanced with Three Disks Mirrored Volume Features SAS2 Integrated RAID Solution User Guide Creating Mirrored Volumes Mirrored VolumeConfiguration Overview Please wait, invoking SAS Configuration UtilitySelect Create RAID 1 Volume Create New Array window appearsSelect Create RAID 1E Volume Expanding an Integrated Mirroring Volume with OCE Manage Array window appears Select New Array Type window appearsArray on this adapter Following figureManage Hot Spares window appears Smart supportHot Spare status changes to Yes Press C to create the hot spare diskOther Configuration Tasks Follow these steps to activate a selected volume Currently inactivePress Enter Select RAID Properties, and then press EnterFollow these steps to select a boot disk SAS2 Bios CU, select an adapter from the Adapter ListHighlight SAS Topology, and press Enter SAS Topology window appearsBoot Device on SAS Topology Window Boot disk or as a data disk Volumes can consist of two-to-ten disksOverview of Integrated Striping Integrated Striping Description Integrated Striping ExampleCreating Integrated Striping Volumes Creating Integrated Striping VolumesSelect Create RAID 0 Volume Viewing Volume Properties Activating an Array Select Delete Array Alternate device Following figure showsSAS2 Integrated RAID Solution User Guide Using the SAS2 Integrated RAID Configuration Utility Hardware and SoftwareRequirements Interface Description Commands EFICommand to get the enclosure and slot numbers of a drive GB of capacity on the disk driveFollowing fields of IOC Page 6 specify the configuration MPI2 specification and is specific for SSD drives only VolumeName a user-specified string to identify the volume Appearing while the command is runningSas2ircu controller# delete noprompt Sas2ircu controller# display filename112 Initiator IDDrive Type Enclosure information Enclosure# Logical IDConfiguration has changed or a drive has failed Failed FLD The volume has failedMissing MIS The volume is missing Initializing Init The volume is initializingSas2ircu controller# hotspare delete EnclosureBay Sas2ircu controller# status Volume status Enabled or Disabled  Physical disk I/Os Quiesced or Not quiescedSas2ircu list NoneSas2ircu controller# constchk volumeId noprompt Sas2ircu controller# activate volumeIdSas2ircu controller# logir action filename noprompt