Lenovo ThinkServer RD330 MegaRAID SAS Software User Guide - Page 397
striping, subvendor ID, uncorrectable error count, vendor ID, vendor info, virtual drive, virtual
View all Lenovo ThinkServer RD330 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 397 highlights
MegaRAID SAS Software User Guide Appendix C: Glossary | striping subvendor ID uncorrectable error count vendor ID vendor info virtual drive virtual drive state write-back write policy write-through 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. 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. 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. 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. Page 397