LSI 9361-8i RAID卡OptRom选项解释_RAIDLevel_CreateRAID

RAID Level：

Level	Description
RAID 0	Uses data striping on two or more drives to provide high data throughput, especially for large files in an environment that requires no data redundancy.
RAID 1	Uses data mirroring on pairs of drives so that data written to one drive is simultaneously written to the other drive. RAID 1 works well for small databases or other small applications that require complete data redundancy.
RAID 5	Uses data striping and parity data across three or more drives (distributed parity) to provide high data throughput and data redundancy, especially for applications that require random access.
RAID 6	Uses data striping and parity data across three or more drives (distributed parity) to provide high data throughput and data redundancy, especially for applications that require random access. RAID 6 can survive the failure of two drives.
RAID 00	Is a spanned drive group that creates a striped set from a series of RAID 0 drive groups to provide high data throughput, especially for large files.

RAID 10	A combination of RAID 0 and RAID 1 that uses data striping across two mirrored drive groups. It provides high data throughput and complete data redundancy.
RAID 50	A combination of RAID 0 and RAID 5 that uses data striping across two drive groups with parity data. It provides high data throughput and complete data redundancy.
RAID 60	A combination of RAID 0 and RAID 6 that uses data striping across two drive groups with parity data. It provides high data throughput and complete data redundancy. RAID 60 can survive the failure of two drives in each RAID set in the spanned drive group.

2.Create RAID：

This section describes the following additional virtual drive properties that you can select while you create virtual drives. Change these parameters only if you have a specific reason for doing so. It is usually best to keep them at their default settings.
 Strip Size – The strip size is the portion of the stripe that resides on a single virtual drive in the drive group. Strip sizes of 64 KB, 128 KB, 256 KB, 512 KB, or 1 MB are supported.
NOTE The Integrated MegaRAID controller supports only64 KB stripe size.
 Read Policy – A virtual drive property that indicates whether the default read policy is Always Read Ahead or No Read Ahead:
— Always Read Ahead – Permits the controller to read sequentially ahead of the requested data and allows the controller to store the additional data in the cache memory. Here, the controller anticipates that the data is required frequently. Even though Always Read Ahead policy speeds up the reads for sequential data, but little
improvement is seen when accessing the random data.
— No Read Ahead – Disables the Always Read Ahead capability of the controller.
 Write Policy – Select one of the following options to specify the write policy for this virtual drive:
— Write Back – In this mode, the controller sends a data transfer completion signal to the host when the controller cache receives all of the data in a transaction. If you select the Write Back policy and the battery is absent, the firmware disables the Write Back policy and defaults to the Write Through policy.
— Write Through – In this mode, the controller sends a data transfer completion signal to the host when the drive subsystem receives all the data in a transaction. 

— Always Write Back – In this mode, the controller sends a data transfer completion signal to the host when the controller cache receives all the data in a transaction. If you select the Always Write Back policy and the battery is absent, the firmware is forced to use the Write Back policy.

 I/O Policy – The I/O policy applies to reads on a specific virtual drive. It does not affect the read ahead cache.
— Cached – In this mode, all reads are buffered in cache memory. Cached I/O provides faster processing.
— Direct – In this mode, reads are not buffered in cache memory. Data is transferred to the cache and the host concurrently. If the same data block is read again, it comes from cache memory. Direct I/O makes sure that the cache and the host contain the same data.
 Disk cache policy – Select a cache setting for this virtual drive:
— Enable – Enable the drive cache.
— Disable – Disable the drive cache.
— Unchanged – Updating the drive cache policy to Unchanged may enable /disable the drive cache based on the WCE (Write Cache Policy) bit of the save mode page of the drive.
 Emulation – Lets you to set the emulation type on a virtual drive to default or none. The force option forces the emulation to be set on a controller even when MFC settings do not support it. The possible options are Default, Disabled, or Forced.
 Initialize – Select to initialize the virtual drive. Initialization prepares the storage medium for use. Fast initialization will be performed on the virtual drive.
 Configure Hot Spare – Select to configure physical drives as hot spares for the newly created virtual drive. This option is enabled only if there are additional drives and if they are eligible to be configured as hot spares. This option is not applicable for RAID 0 or RAID 00. If you select this option and after the Virtual drive is created, a dialog appears. The dialog asks you to choose the physical drives that you want to configure as hot spares.
 Provide shared access– Select this option if you want the virtual drive to be shared between the servers in a cluster. This option appears only if the controller supports High Availability DAS.