mirror of https://github.com/tLDP/LDP
switching all sect4 to sect2 (sect4 cannot be direct child of sect1)
This commit is contained in:
parent
6803385e51
commit
047c5460c4
|
@ -142,7 +142,7 @@ RAID-linear is a simple concatenation of drives to create a larger virtual
|
|||
drive. It is handy if you have a number small drives, and wish to create a
|
||||
single, large drive. This concatenation offers no redundancy, and in fact decreases
|
||||
the overall reliability: if any one drive fails, the combined drive will fail.
|
||||
<sect4>SUMMARY
|
||||
<sect2>SUMMARY
|
||||
<p>
|
||||
<itemize>
|
||||
<item>Enables construction of a large virtual drive from a number of smaller
|
||||
|
@ -161,7 +161,7 @@ Also referred to as &dquot;mirroring&dquot;. Two (or more) drives, all
|
|||
up between several drives. Unfortunately, mirroring is also one of the least
|
||||
efficient in terms of storage: two mirrored drives can store no more data than
|
||||
a single drive.
|
||||
<sect4>SUMMARY
|
||||
<sect2>SUMMARY
|
||||
<p>
|
||||
<itemize>
|
||||
<item>Good read/write performance
|
||||
|
@ -188,7 +188,7 @@ Similar to RAID-linear, except that the component drives are divided into
|
|||
decreases overall reliability: a single drive failure will knock out the whole
|
||||
thing. However, the 5070 hardware RAID 0 is the fastest of any of the schemes
|
||||
listed here.
|
||||
<sect4>SUMMARY:
|
||||
<sect2>SUMMARY:
|
||||
<p>
|
||||
<itemize>
|
||||
<item>Use RAID 0 to combine smaller drives into one large virtual drive.
|
||||
|
@ -206,7 +206,7 @@ RAID-2 is seldom used anymore, and to some degree has been made obsolete
|
|||
greater data consistency if power is lost during a write; however, battery
|
||||
backup and a clean shutdown can offer the same benefits. RAID-3 is similar
|
||||
to RAID-4, except that it uses the smallest possible stripe size.
|
||||
<sect4>SUMMARY
|
||||
<sect2>SUMMARY
|
||||
<p>
|
||||
<itemize>
|
||||
<item>RAID 2 is largely obsolete
|
||||
|
@ -232,7 +232,7 @@ RAID-4 interleaves stripes like RAID-0, but it requires an additional drive
|
|||
before the new parity can be calculated and written out. In an environment
|
||||
with lots of writes, the parity disk can become a bottleneck, as each write
|
||||
must access the parity disk.
|
||||
<sect4>SUMMARY
|
||||
<sect2>SUMMARY
|
||||
<p>
|
||||
<itemize>
|
||||
<item>Similar to RAID 0
|
||||
|
@ -252,7 +252,7 @@ RAID-5 avoids the write-bottleneck of RAID-4 by alternately storing the
|
|||
principle advantage over mirroring is that it offers redundancy and protection
|
||||
against single-drive failure, while offering far more storage capacity when
|
||||
used with three or more drives.
|
||||
<sect4>SUMMARY
|
||||
<sect2>SUMMARY
|
||||
<p>
|
||||
<itemize>
|
||||
<item>Use RAID 5 if you need to make the best use of your available storage space
|
||||
|
@ -276,21 +276,21 @@ The 5070 / Linux 2.2 combination was tested on SPARCstation (5, 10, &
|
|||
<p>
|
||||
|
||||
If your system is already up and running, you must halt the operating system.
|
||||
<sect4>GNOME:
|
||||
<sect2>GNOME:
|
||||
<p>
|
||||
<enum>
|
||||
<item>From the login screen right click the &dquot;Options&dquot; button.
|
||||
<item>On the popup menu select System -> Halt.
|
||||
<item>Click &dquot;Yes&dquot; when the verification box appears
|
||||
</enum>
|
||||
<sect4>KDE:
|
||||
<sect2>KDE:
|
||||
<p>
|
||||
<enum>
|
||||
<item>From the login screen right click shutdown.
|
||||
<item>On the popup menu select shutdown by right clicking its radio button.
|
||||
<item>Click OK
|
||||
</enum>
|
||||
<sect4>XDM:
|
||||
<sect2>XDM:
|
||||
<p>
|
||||
<enum>
|
||||
<item>login as root
|
||||
|
@ -298,13 +298,13 @@ If your system is already up and running, you must halt the operating system.
|
|||
<item>select &dquot;New Shell&dquot;
|
||||
<item>When the shell opens type &dquot;halt&dquot; at the prompt and press return
|
||||
</enum>
|
||||
<sect4>Console Login (systems without X windows):
|
||||
<sect2>Console Login (systems without X windows):
|
||||
<p>
|
||||
<enum>
|
||||
<item>Login as root
|
||||
<item>Type &dquot;halt&dquot;
|
||||
</enum>
|
||||
<sect4>All Systems:
|
||||
<sect2>All Systems:
|
||||
<p>
|
||||
|
||||
Wait for the message &dquot;power down&dquot; or &dquot;system halted&dquot;
|
||||
|
@ -315,7 +315,7 @@ Wait for the message &dquot;power down&dquot; or &dquot;system halted&dquot;
|
|||
is not lit and that the fans inside the system are not running. Do not disconnect
|
||||
the system power cord.
|
||||
|
||||
<sect4>SPARCstation 4, 5, 10, 20 & UltraSPARC Systems:
|
||||
<sect2>SPARCstation 4, 5, 10, 20 & UltraSPARC Systems:
|
||||
<p>
|
||||
<enum>
|
||||
<item>Remove the top cover on the CPU enclosure. On a SPARCstation 10, this is
|
||||
|
@ -341,7 +341,7 @@ Wait for the message &dquot;power down&dquot; or &dquot;system halted&dquot;
|
|||
the plastic tab in back snaps into place. Tighten the captive screw on the
|
||||
upper right corner.
|
||||
</enum>
|
||||
<sect4>Ultra Enterprise Servers, SPARCserver 1000 &amp; 2000 Systems, SPARCserver
|
||||
<sect2>Ultra Enterprise Servers, SPARCserver 1000 &amp; 2000 Systems, SPARCserver
|
||||
6XO MP Series:
|
||||
<p>
|
||||
<enum>
|
||||
|
@ -367,7 +367,7 @@ Wait for the message &dquot;power down&dquot; or &dquot;system halted&dquot;
|
|||
<item>Re-insert the CPU board into the CPU enclosure and re-install the Allen-head
|
||||
retaining screws that secure the CPU board.
|
||||
</enum>
|
||||
<sect4>All Systems:
|
||||
<sect2>All Systems:
|
||||
<p>
|
||||
<enum>
|
||||
<item>Mate the external cable adapter box to the 5070 RAIDium and gently tighten
|
||||
|
@ -385,7 +385,7 @@ Wait for the message &dquot;power down&dquot; or &dquot;system halted&dquot;
|
|||
all SCSI buses are properly terminated. This means a terminator is installed
|
||||
only at each end of each SCSI bus daisy chain.
|
||||
</enum>
|
||||
<sect4>Verifying the Hardware Installation:
|
||||
<sect2>Verifying the Hardware Installation:
|
||||
<p>
|
||||
|
||||
These steps are optional but recommended. First, power-on your system and
|
||||
|
@ -545,7 +545,7 @@ When agui starts, it reads the configuration of the RaidRunner and probes
|
|||
is displayed in the bottom left corner of the screen.
|
||||
<sect1>Main Screen Options
|
||||
<p>
|
||||
<sect4><Figure 1: Main Screen>
|
||||
<sect2><Figure 1: Main Screen>
|
||||
|
||||
<p>
|
||||
|
||||
|
@ -593,7 +593,7 @@ These selections are described in detail below.
|
|||
Exit the agui main screen and return to the husky ( :raid; ) prompt.
|
||||
<sect1>[R]aidSets:
|
||||
<p>
|
||||
<sect4><Figure 2: RAIDSet Configuration Screen>
|
||||
<sect2><Figure 2: RAIDSet Configuration Screen>
|
||||
|
||||
<p>
|
||||
|
||||
|
@ -660,7 +660,7 @@ The Raid Set Configuration screen displays a Raid Set in the data area
|
|||
</itemize>
|
||||
<sect1>[H]ostports:
|
||||
<p>
|
||||
<sect4><Figure 3: Host Port Configuration Screen>
|
||||
<sect2><Figure 3: Host Port Configuration Screen>
|
||||
|
||||
<p>
|
||||
|
||||
|
@ -694,7 +694,7 @@ The Host Port Configuration screen displays for each controller, each host
|
|||
</itemize>
|
||||
<sect1>[S]pares:
|
||||
<p>
|
||||
<sect4><Figure 4: Spare Device Configuration Screen>
|
||||
<sect2><Figure 4: Spare Device Configuration Screen>
|
||||
|
||||
<p>
|
||||
|
||||
|
@ -745,7 +745,7 @@ The Spare Device Configuration screen displays all configured spare devices
|
|||
</itemize>
|
||||
<sect1>[M]onitor:
|
||||
<p>
|
||||
<sect4><Figure 5: SCSI Monitor Screen>
|
||||
<sect2><Figure 5: SCSI Monitor Screen>
|
||||
|
||||
<p>
|
||||
|
||||
|
@ -778,7 +778,7 @@ The SCSI Monitor Configuration screen displays a table of SCSI monitors
|
|||
</itemize>
|
||||
<sect1>[G]eneral:
|
||||
<p>
|
||||
<sect4><Figure 6: General Screen>
|
||||
<sect2><Figure 6: General Screen>
|
||||
|
||||
<p>
|
||||
|
||||
|
|
Loading…
Reference in New Issue