3Ware 7506-8 User Guide - Page 75

To build Enterprise module, type, To build Bigmem module, The file created is 3w-xxxx.big

Page 75 highlights

Red Hat Linux Installation make smp -f Makefile.rh The file created is 3w-xxxx.smp To build Enterprise module, type: make ent -f Makefile.rh The file created is 3w-xxxx.ent To build Bigmem module, type: (This is for when you have more than 4 GBytes of system RAM and you are using the BigMem kernel.) make big -f Makefile.rh The file created is 3w-xxxx.big To build Boot module (this is used when creating a driver for the boot diskette), type: make bot -f Makefile.rh The file created is 3w-xxxx.bot 5 Copy the module as follows: For 2.4 kernels, copy module to: /lib/modules//kernel/drivers/scsi/3w-xxxx.o RAID array initialization RAID 0 arrays do not need to be initialized and are immediately available for use with full performance when created. RAID 1 and 10 arrays are not initialized when created and are immediately available for use with full performance when created. The first time the array is verified (via the BIOS or 3ware 3DM), the array is initialized. Initialization results in data from one disk (the disk on the lower channel number) being copied to the other drive. In RAID 10 arrays, data from one half of the array is copied to the other half. After the initial verification, subsequent verifies to a RAID 1 or 10 array result in the data from one drive (or set of drives) being compared to the other drive (or set of drives). RAID 5 arrays are immediately initialized after being created in the BIOS by writing zeroes to all array members. The user can reboot the system before this is complete in order to use the RAID 5 array immediately. Once booted to the operating system, the RAID 5 array goes into initialization mode after a delay of up to ten minutes. The advantage of this procedure is that the RAID 5 array can be used immediately, but it will not be fault tolerant until the initialization is complete. The disadvantage of this is that it takes longer for the array to become fully redundant, because it takes longer to initialize an array than it does to write zeroes to the array. www.3ware.com 67

  • 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

Red Hat Linux Installation
www.3ware.com
67
make smp -f Makefile.rh
The file created is
3w-xxxx.smp
To build Enterprise module, type:
make ent -f Makefile.rh
The file created is
3w-xxxx.ent
To build Bigmem module, type:
(This is for when you have more than 4 GBytes of system RAM and
you are using the BigMem kernel.)
make big -f Makefile.rh
The file created is 3w-xxxx.big
To build Boot module
(this is used when creating a driver for the boot diskette), type:
make bot -f Makefile.rh
The file created is 3w-xxxx.bot
5
Copy the module as follows:
For 2.4 kernels, copy module to:
/lib/modules/
<kernel string>
/kernel/drivers/scsi/3w-xxxx.o
RAID array initialization
RAID 0 arrays do not need to be initialized and are immediately available for
use with full performance when created.
RAID 1 and 10 arrays are not initialized when created and are immediately
available for use with full performance when created. The first time the array
is verified (via the BIOS or 3ware 3DM), the array is initialized. Initialization
results in data from one disk (the disk on the lower channel number) being
copied to the other drive. In RAID 10 arrays, data from one half of the array is
copied to the other half. After the initial verification, subsequent verifies to a
RAID 1 or 10 array result in the data from one drive (or set of drives) being
compared to the other drive (or set of drives).
RAID 5 arrays are immediately initialized after being created in the BIOS by
writing zeroes to all array members. The user can reboot the system before
this is complete in order to use the RAID 5 array immediately. Once booted to
the operating system, the RAID 5 array goes into initialization mode after a
delay of up to ten minutes. The advantage of this procedure is that the RAID 5
array can be used immediately, but it will not be fault tolerant until the initial-
ization is complete. The disadvantage of this is that it takes longer for the
array to become fully redundant, because it takes longer to initialize an array
than it does to write zeroes to the array.