mirror of https://github.com/tLDP/LDP
fix minor typos in Antares-RAID-sparcLinux-HOWTO.sgml
This commit is contained in:
parent
8aab927c90
commit
a42b636a90
|
@ -485,7 +485,7 @@ Choosing the brand and capacity of the drives that will form the hard drive
|
|||
|
||||
Before diving into the RAID configuration I need to define a few terms.
|
||||
<itemize>
|
||||
<item>&dquot;RaidRunner&dquot; is the name given to the the 5070 controller board.
|
||||
<item>&dquot;RaidRunner&dquot; is the name given to the 5070 controller board.
|
||||
<item>&dquot;Husky&dquot; is the name given to the shell which produces the &dquot;:raid;&dquot;
|
||||
command prompt. It is a command language interpreter that executes commands
|
||||
read from the standard input or from a file. Husky is a scaled down model of
|
||||
|
@ -1004,7 +1004,7 @@ Q
|
|||
<Figure 12: The RaidSets
|
||||
screen of the GUI showing the newly configured RAID 5>
|
||||
|
||||
<item>Press Q to exit the RaidSet screen and return to the the Main screen
|
||||
<item>Press Q to exit the RaidSet screen and return to the Main screen
|
||||
<item>Press Q to [Q]uit agui and exit to the husky prompt.
|
||||
<item>type &dquot;reboot&dquot; then press enter. This will reboot the RaidRunner
|
||||
(not the host machine.)
|
||||
|
@ -1226,7 +1226,7 @@ This is the easiest way to install the RAID since the RedHat installer
|
|||
IMPORTANT NOTE: you may see a small SCSI
|
||||
drive ( usually ˜128 MB) on the list of available drives. DO NOT select
|
||||
this drive for use. It is the SMON communication channel NOT a drive. If setup
|
||||
tries to use it it will hang the installer.
|
||||
tries to use it the installer will hang.
|
||||
<item>Thats it, the installation program takes care of everything else !!
|
||||
</enum>
|
||||
<sect>Maintenance
|
||||
|
@ -1318,7 +1318,7 @@ After you have replaced the bad drive you must re-integrate it into the
|
|||
Where <name> is whatever you named the raid set and <backend>
|
||||
is the ID of the backend that is being re-integrated into the RAID. If a spare
|
||||
was in use it will be automatically returned to the spares pool. Be patient,
|
||||
reconstruction can take a few minutes minutes to several hours depending on
|
||||
reconstruction can take a few minutes to several hours depending on
|
||||
the RAID level and the size. Fortunately, you can use the RAID as you normally
|
||||
would during this process.
|
||||
|
||||
|
@ -1496,7 +1496,7 @@ This device reconstruction will take anywhere from 10 minutes to one and
|
|||
During device reconstruction, pairs of numbers will be printed indicating
|
||||
each 10% of data reconstructed. The pairs of numbers are separated
|
||||
by a slash character, the first number being the number of blocks reconstructed
|
||||
so far and the second being the number number of blocks to be reconstructed.
|
||||
so far and the second being the number of blocks to be reconstructed.
|
||||
Further status about the rebuild can be gained from running rebuild.
|
||||
|
||||
|
||||
|
@ -2207,7 +2207,7 @@ echo $k
|
|||
and bind_point/ctl are the data and control channels for the fifo. Data written
|
||||
to the bind_point/data file is available for reading from the same file in
|
||||
a first-in first-out basis. A write of x bytes to the bind_point/data file
|
||||
will either complete and and transfer all the data, or will transfer sufficient
|
||||
will either complete and transfer all the data, or will transfer sufficient
|
||||
bytes until the fifo buffer is full then block until data is removed from the
|
||||
fifo buffer by reading. A read of x bytes from the bind_point/data file will
|
||||
transfer the lessor of the current amount of data in the fifo buffer or x bytes.
|
||||
|
@ -3400,7 +3400,7 @@ mstargd performs its monitoring
|
|||
<item>3, LOGICAL UNIT HAS NOT SELF-CONFIGURED YET, 0x3e, 0x00
|
||||
<item>4, LOGICAL UNIT HAS FAILED SELF-CONFIGURATION, 0x4c, 0x00
|
||||
<item>stargd's spin state is used to describe the condition of the tar get
|
||||
whilst is is NOT READY. When stargd is not ready to accept SCSI-2 medium
|
||||
whilst it is NOT READY. When stargd is not ready to accept SCSI-2 medium
|
||||
access commands it returns a CHECK CONDITION status to all medium access
|
||||
commands, sets the mode sense key to NOT READY and the additional mode sense
|
||||
code and code qualifier to values depending in the spin state value.
|
||||
|
@ -3428,7 +3428,7 @@ mstargd performs its monitoring
|
|||
<itemize>
|
||||
<item>pid: This is the process identifier of the K9 process whose run-queue
|
||||
priority is to change.
|
||||
<item>priority: This the the priority to set. Priorities range from 0 (lowest)
|
||||
<item>priority: This is the priority to set. Priorities range from 0 (lowest)
|
||||
to 9 (highest).
|
||||
</itemize>
|
||||
<item>SEE ALSO: K9setpriority
|
||||
|
@ -5369,7 +5369,7 @@ This device reconstruction will take anywhere from 10 minutes to one and
|
|||
amount of activity the host is generating. During device reconstruction, pairs
|
||||
of numbers will be printed indicating each 10% of data reconstructed.
|
||||
The pairs of numbers are separated by a slash character, the first number being
|
||||
the number of blocks reconstructed so far and the second being the number number
|
||||
the number of blocks reconstructed so far and the second being the number
|
||||
of blocks to be reconstructed. Further status about the rebuild can be gained
|
||||
from running rebuild. Checks are made to ensure that the raid set is running,
|
||||
the spare works, and that there is no failure of the spare during reconstruction.
|
||||
|
@ -5405,7 +5405,7 @@ This device reconstruction will take anywhere from 10 minutes to one and
|
|||
device reconstruction, pairs of numbers will be printed indicating each 10%
|
||||
of data reconstructed. The pairs of numbers are separated by a slash character,
|
||||
the first number being the number of blocks reconstructed so far and the second
|
||||
being the number number of blocks to be reconstructed. Further status about
|
||||
being the number of blocks to be reconstructed. Further status about
|
||||
the rebuild can be gained from running rebuild. Checks are made to ensure that
|
||||
the raid set is running, the backend works, and that there is no failure of
|
||||
the backend during reconstruction.
|
||||
|
@ -6024,7 +6024,7 @@ The following two examples show the transfer of the raid binary and the
|
|||
a serial number. A serial number may only be set once, there after any attempt
|
||||
to set another one will be ignored and the current serial number printed.
|
||||
If the serial number has to be re-set then the flashram needs to be reblown
|
||||
as if it were brand new. Note that when setting the the serial number for
|
||||
as if it were brand new. Note that when setting the serial number for
|
||||
the first time, the exact format of the command is very important. There
|
||||
will be exactly one space after the the command 'Sno', after which the next
|
||||
12 printable characters are taken as the serial number. If there are less
|
||||
|
@ -6925,7 +6925,7 @@ ranklist a comma separated list of rank id's (scsi id's) for which the
|
|||
read the host operating system will allow. In this case, the host operating
|
||||
system will break the application's read up into smaller reads. stargd can
|
||||
trigger on a certain discontinuous read (by specifying a size in blocks - nread)
|
||||
and will prefetch prefetch the rest of the application read (nrlen). For
|
||||
and will prefetch the rest of the application read (nrlen). For
|
||||
example, if an application performs a read of 304 blocks on a host operating
|
||||
system which has a maximum read size of 128 blocks, then you could set the
|
||||
-nr arguments nread:nrlen to 128:304 which will cause stargd to, when it sees
|
||||
|
|
Loading…
Reference in New Issue