Lenovo ThinkServer RD650 User Manual page 414

12Gb/s MegaRAID SAS Software User Guide
March 2014
Stripe size
Striping
Subvendor ID
Temperature
Uncorrectable error
count
Vendor ID
Vendor info
Virtual drive
Virtual drive state
Write-back
Write policy
Write-through
A virtual drive property indicating the length of the interleaved data segments that the
RAID controller writes across multiple drives, not including parity drives. For example,
consider a stripe that contains 64 KB of drive space and has 16 KB of data residing on each
drive in the stripe. In this case, the stripe size is 64 KB and the strip size is 16 KB. The user
can select the stripe size.
A technique used to write data across all drives in a virtual drive.
Each stripe consists of consecutive virtual drive data addresses that are mapped in
fixed-size units to each drive in the virtual drive using a sequential pattern. For example, if
the virtual drive includes five drives, the stripe writes data to drives one through five
without repeating any of the drives. The amount of space consumed by a stripe is the
same on each drive. Striping by itself does not provide data redundancy. Striping in
combination with parity does provide data redundancy.
A controller property that lists additional vendor ID information about the controller.
T
Temperature of the battery pack, measured in Celsius.
U
A controller property that lists the number of uncorrectable errors detected on drives
connected to the controller. If the error count reaches a certain level, a drive will be
marked as failed.
V
A controller property indicating the vendor-assigned ID number of the controller.
A drive property listing the name of the vendor of the drive.
A storage unit created by a RAID controller from one or more drives. Although a virtual
drive can be created from several drives, it is seen by the operating system as a single
drive. Depending on the RAID level used, the virtual drive can retain redundant data in
case of a drive failure.
A virtual drive property indicating the condition of the virtual drive. Examples include
Optimal and Degraded.
W
In Write-Back Caching mode, the controller sends a data transfer completion signal to the
host when the controller cache has received all of the data in a drive write transaction.
Data is written to the drive subsystem in accordance with policies set up by the controller.
These policies include the amount of dirty/clean cache lines, the number of cache lines
available, and elapsed time from the last cache flush.
See Default Write Policy.
In Write-Through Caching mode, the controller sends a data transfer completion signal to
the host when the drive subsystem has received all of the data and has completed the
write transaction to the drive.
LSI Corporation
- 414 -
Glossary