ASRock Z87 Extreme11/ac LSI Mega RAID Storage Manager Guide - Page 178

striping, subvendor ID, uncorrectable error count, vendor ID, vendor info, virtual drive, virtual

Page 178 highlights

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. striping - 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. subvendor ID - A controller property that lists additional vendor ID information about the controller. uncorrectable error count - 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. vendor ID - A controller property indicating the vendor-assigned ID number of the controller. vendor info - A drive property listing the name of the vendor of the drive. virtual drive - A storage unit created by a RAID controller from one or more drives. Although a virtual drive may 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 may retain redundant data in case of a drive failure. virtual drive state - A virtual drive property indicating the condition of the virtual drive. Examples include Optimal and Degraded. write-back - 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. write policy - See Default Write Policy. write-through - 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 178 DB09-000202-05 37857-02 Glossary Rev. F - May 2011 Copyright © 2011 by LSI Corporation. All rights reserved.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178

Page 178
Glossary
DB09-000202-05 37857-02
Rev. F - May 2011
Copyright © 2011 by LSI Corporation. All rights reserved.
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.
striping –
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.
subvendor ID –
A controller property that lists additional vendor ID information about the
controller.
uncorrectable error count –
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.
vendor ID –
A controller property indicating the vendor-assigned ID number of the controller.
vendor info –
A drive property listing the name of the vendor of the drive.
virtual drive –
A storage unit created by a RAID controller from one or more drives. Although a
virtual drive may 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 may retain redundant data in case of
a drive failure.
virtual drive state –
A virtual drive property indicating the condition of the virtual drive. Examples
include Optimal and Degraded.
write-back –
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.
write policy –
See
Default Write Policy
.
write-through –
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.