Creating A Unit Through 3Dm - 3Ware 9550SXU-16ML User Manual

Stripe size, if appropriate for the RAID level
In general, smaller stripe sizes are better for sequential I/O, such as video, and
larger stripe sizes are better for random I/O (such as databases).
Striping size is not applicable for RAID 1, because it is a mirrored array
without striping.
Using the default stripe size of 64KB usually gives you the best performance
for mixed I/Os. If your application has some specific I/O pattern (purely
sequential or purely random), you might want to experiment with smaller or
larger stripe size.
Unit policies
Several unit policies are set when you create a new unit:
Write Cache (enabled, by default)
Drive Queuing (enabled, by default) (9550SX controllers only)
Auto-Verify (disabled, by default)
Continue on Source Error When Rebuild (disabled, by default)
Does not apply to 9550SX controllers, as this feature is integrated into the
StorSave Profile.
StorSave Profile (Protection, by default) (9550SX controllers only)
The particular policies that you can adjust when you create the unit vary,
depending on which program you are using: 3DM, 3BM, or the CLI.
In 3DM and using the CLI, you can enable/disable write cache, enable
Auto-Verify, and specify whether to continue on source error
In 3BM, you can specify all policies except Auto-Verify
You can change all of these policies after the unit has been created.
For a summary of what these policies do, see the discussion under "Unit
Policies" on page 93 in the section "Controller Settings Page". For how to
adjust each one, see the procedures later in this chapter.

Creating a Unit through 3DM

In 3DM, configuration starts from the Maintenance page (Figure 51), where
you can configure a new unit, designate an available drive as a hot spare,
delete a unit, and remove units or drives. You can also have 3DM rescan the
controller, if you have added drives or units.
For information about working in 3DM, see "3ware Disk Manager (3DM 2)"
on page 65.
www.3ware.com
Creating a New Unit
127