Adaptec 133U2 User Guide - Page 169

Stands for Self-Monitoring Analysis and Reporting Technology.

Page 169 highlights

Glossary S.M.A.R.T Stands for Self-Monitoring Analysis and Reporting Technology. Hard drives that support this technology continually analyze their performance and generate an alert if they determine that the disk is likely to fail in the next few hours. spare pool A pool of multiple disks which automatically replace failed disks on any array on the controller. stand-alone disk A disk that is not part of an array. stripe set A container made up of two or more equal-sized partitions that reside on different disks. The stripe set distributes, or stripes, data evenly across its respective disks. stripe set of mirror sets A multilevel container created from two or more equal-sized mirror sets. stripe size The size that will be used to stripe data or parity information across the disks in the array. striping, disk; striped array Spreading data over multiple disks to enhance performance. Often referred to as RAID 0, simple data striping provides no redundancy scheme, and is not technically a standardized RAID lever. subsystem The collection of software and hardware that controls storage to be managed and monitored. T target ID See SCSI ID. task An actively running process such as disk format or array verification. An operation that occurs only on the controller, asynchronous to all other operations. For example, scrub container, clear disk, and create file system are tasks done on the controller. Glossary-9

  • 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

Glossary-9
Glossary
S.M.A.R.T
Stands for Self-Monitoring Analysis and Reporting Technology.
Hard drives that support this technology continually analyze
their performance and generate an alert if they determine that
the disk is likely to fail in the next few hours.
spare pool
A pool of multiple disks which automatically replace failed
disks on
any
array on the controller.
stand-alone disk
A disk that is
not
part of an array.
stripe set
A container made up of two or more equal-sized partitions that
reside on different disks. The stripe set distributes, or stripes,
data evenly across its respective disks.
stripe set of mirror sets
A multilevel container created from two or more equal-sized
mirror sets.
stripe size
The size that will be used to stripe data or parity information
across the disks in the array.
striping, disk; striped array
Spreading data over multiple disks to enhance performance.
Often referred to as RAID 0, simple data striping provides no
redundancy scheme, and is not technically a standardized
RAID lever.
subsystem
The collection of software and hardware that controls storage
to be managed and monitored.
T
target ID
See
SCSI ID.
task
An actively running process such as disk format or array
verification.
An operation that occurs only on the controller, asynchronous
to all other operations. For example, scrub container, clear disk,
and create file system are tasks done on the controller.