HP Workstation xw4100 Adaptec SCSI RAID 2120S: Software User's Guide - Page 73

Deleting Arrays, Creating a RAID 5

Get HP Workstation xw4100 PDF manuals and user guides View all HP Workstation xw4100 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 73 highlights

Using the Command Line Interface Creating a RAID 5 When creating a RAID 5, you need to determine the stripe size that is most suitable for your environment. See Creating a RAID 0 for more information about determining the appropriate stripe size for your environment. To recreate the data of a failed disk in a RAID 5, you use a form of redundancy called parity. When you set up parity, you initialize the parity stripes by using a scrubbing switch (/scrub=TRUE). Parity is set up in the background, and the disks are available immediately. The /scrub switch is not available in UNIX/Linux. For UNIX/ Linux, the RAID 5 is always created by building. To create a RAID 5, use the container create raid5 command. In the following example, a RAID 5 is created on SCSI devices (2,1,0), (2,2,0), and (2,3,0) using 100 M of available space from each SCSI device. The /stripe_size switch specifies that each stripe is 64 K in size. AAC0> container create raid5 /stripe_size=64K ((2,1,0), 100M) (2,2,0) (2,3,0) Executing: container create raid5 /stripe_size=65,536 ((CHANNEL=2,ID=1,LUN=0),104,857,600) (CHANNEL=2,ID=2,LUN=0) (CHANNEL=2,ID=3,LUN=0) Deleting Arrays To delete an array, use the container delete command. In the following example, array 0 is deleted. AAC0> container delete 0 Executing: container delete 0 After running the container delete command, use the container list command to verify that the array was deleted. In the following example, no arrays are found on the controller. AAC0> container list Executing: container list No containers found. 4-7

  • 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
4-7
Using the Command Line Interface
Creating a RAID 5
When creating a RAID 5, you need to determine the stripe size that
is most suitable for your environment. See
Creating a RAID 0
for
more information about determining the appropriate stripe size for
your environment.
To recreate the data of a failed disk in a RAID 5, you use a form of
redundancy called parity. When you set up parity, you initialize
the parity stripes by using a scrubbing switch (
/scrub=TRUE
).
Parity is set up in the background, and the disks are available
immediately.
The
/scrub
switch is not available in UNIX/Linux. For UNIX/
Linux, the RAID 5 is always created by building.
To create a RAID 5, use the
container create raid5
command. In the following example, a RAID 5 is created on SCSI
devices
(2,1,0)
,
(2,2,0)
, and
(2,3,0)
using
100 M
of available space
from each SCSI device. The
/stripe_size
switch specifies that each
stripe is
64 K
in size.
AAC0> container create raid5
/stripe_size=64K
(
(2,1,0)
,
100M
)
(2,2,0)
(2,3,0)
Executing: container create raid5 /stripe_size=65,536
((CHANNEL=2,ID=1,LUN=0),104,857,600)
(CHANNEL=2,ID=2,LUN=0) (CHANNEL=2,ID=3,LUN=0)
Deleting Arrays
To delete an array, use the
container delete
command. In the
following example, array
0
is deleted.
AAC0> container delete
0
Executing: container delete 0
After running the
container delete
command, use the
container list
command to verify that the array was deleted.
In the following example, no arrays are found on the controller.
AAC0> container list
Executing: container list
No containers found.