arti/irix-657m-src
1
0
Fork 0
Code Activity

Source code upload

Browse Source
This commit is contained in:
calmsacibis995
2022-09-29 17:59:04 +03:00
parent 72fa9da3d7
commit 8fc8fa8089
33399 changed files with 11964078 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
eoe/relnotes/plexing/Makefile Normal file
View File

@@ -0,0 +1,12 @@
# Makefile for XLV Plexing release notes
# $Revision: 1.1 $
# Edit the CMM and AMM macros to contain the list of chapters and appendices
# in this book. Do not use abbreviations (i.e. ch[1-8].cmm), because the
# Makefile dependencies will not work.
CMM = ch1.cmm ch2.cmm ch3.cmm ch4.cmm ch5.cmm ch6.cmm
AMM =
RELPROD =plexing
include $(ROOT)/usr/include/make/relnotesrules

119
eoe/relnotes/plexing/ch1.cmm Normal file
View File

@@ -0,0 +1,119 @@
.nr H1 0
.H 1 "Introduction"
This document describes the features of the Disk Plexing Option.
.\"
.\" Here is some info about the s/w license agreement.
.\" It should go as near to the beginning of the introduction
.\" as you can comfortably put it.
.\"
.VL 7
.LI "\f6Note:\f1"
Packaged with your software is
a separate sheet that contains the
Software License Agreement.
This software is provided to you
solely under the terms and conditions of the
Software License Agreement.
Please take a few moments to review the Agreement.
.LE
.P
This document contains the following chapters:
.\"
.\"
.\" Delete whichever of the following do not apply.
.\"
.\"
.AL 1 +5
.LI
Introduction
.LI
Installation Information
.LI
License Activation
.LI
Known Bugs and Workarounds
.LE
.P
.\" Add the following paragraph if your release notes include
.\" man pages.
.\"
.\" The release note includes man pages only if the <PRODUCT>.
.\" does not have a user's or programmer's guide in which to
.\" place them.
.\"
.\" Delete the following paragraph if you don't need it.
.\"
.\" Appendix A lists the <PRODUCT> man pages.
.bp
.H 2 "Release Identification Information"
.P
Following is the release identification information for the Disk
Plexing Option:
.P
.KS
.TS
lfPB l .
\f3Software Option Product\f1 T{
.fi
Disk Plexing (Mirroring) Option for XFS
T}
.sp 0.5
\f3Version\f1 T{
.fi
2
T}
.sp 0.5
\f3Product Code\f1 T{
.fi
SR4-PLEX-2.0
T}
.sp 0.5
\f3System Software Requirements\f1 T{
.fi
IRIX 6.4
T}
.TE
.TE
.KE
.ps 11
.vs 13
.\" .H 2 "Hardware Requirements"
.\" Delete this section if it does not apply.
.\"
.\" List here any special hardware configurations users need to
.\" run this software product.
.\"
.H 2 "On-Line Release Notes"
After you install the online documentation for a product
(the \f2relnotes\fP subsystem),
you can view the release notes on your screen.
.P
If you have a graphics system, select ``Release Notes''
from the Tools submenu of the Toolchest. This displays
the \f2grelnotes\f1(1) graphical browser for the online release notes.
.P
Refer to the \f2grelnotes\f1(1) man page for information on options
to this command.
.P
If you do not have a graphics system, you can use the \f2relnotes\f1 command.
Refer to the \f2relnotes\f1(1) man page for accessing the online release
notes.
.VL 7
.LI "\f6Note:\f1
You can read the online release notes for most products before
installing the software.
Refer to the booklet in your CD-ROM case for more information.
.LE
.H 2 "Product Support"
Silicon Graphics, Inc., provides a comprehensive
product support maintenance program for its products.
.P
If you are in North America and would like support
for your Silicon Graphics-supported products, contact
the Technical Assistance Center at
.br
1-800-800-4SGI.
.P
If you are outside North America,
contact the Silicon Graphics subsidiary or authorized
distributor in your country.

118
eoe/relnotes/plexing/ch2.cmm Normal file
View File

@@ -0,0 +1,118 @@
.nr H1 1
.H 1 "Installation Information"
.\"
.\" Developer
.\"
This chapter lists supplemental information to
the \f2IRIS Software Installation Guide.\f1
The information listed here is product-specific;
use it with the installation guide to install
this product.
.H 2 "Disk Plexing Option License"
The IRIX 6.4 software includes a logical volume manager
called XLV. XLV allow you to organize multiple disk drives into
a single logical volume that can be accessed as a disk. The base
XLV software allows you to concatenate and stripe disks together.
.P
The Disk Plexing Option allows you to plex (or mirror) multiple
disks together for reliability. With the Disk Plexing Option, you
can create and use volumes that maintain multiple copies of the data.
This allows you to recover from disk failures.
In addition to fault-tolerance, the Disk Plexing Option also
allows you to perform a wide range of volume reconfigurations online.
The Disk Plexing Option allows you to, for example, replace a
disk drive that is about to fail with another disk drive; and this
can be done while the logical volume is mounted and actively being
used.
..\"
.\" Each subsystem should be described in enough detail so that
.\" users can decide whether or not they need to install it.
.\" Hints such as "You need to install this subsystem if you want to use
.\" Visual System Administration Tools" or "This subsystem is useful only
.\" if you want to display Kanji characters" would be nice. For subsystems
.\" such as eoe2.sw.4Dwm that are important if you have graphics, but not
.\" important for servers and aren't marked required in the spec file (inst
.\" doesn't show + and doesn't require their installation), be sure to make
.\" this very clear in the description or in a separate list.
.\"
.\"
.\" Don't try and fix the problem where NFS_AG appears as "NFS AG".
.\" It's a bug in grelnotes and won't be fixed.
.\"
.\"
.\" The size of each subsystem should be listed so that users get an idea
.\" of the disk space requirements before they get into inst.
.\"
.H 2 "Installation Method"
.\"
.\" The installation methods are called "miniroot installation" and
.\" "IRIX installation". The specific subsystems that require Miniroot
.\" Installation should be listed, or state that the product can be
.\" installed with IRIX Installation.
.\"
.\" If some subsystems of this option must be installed using the miniroot
.\" and others can be installed using IRIX, fill in the table below:
.\"
.\" If all subsystems of this option can be installed using using IRIX,
.\" include the following paragraph. Be sure to delete the comment
.\" marks at the beginning of each line so the paragraph will print.
.\"
All of the subsystems for the Disk Plexing Option can be installed using IRIX. You
do not need to use the miniroot. Refer to the \f2IRIS Software
Installation Guide\f1 for complete installation instructions.
.\"
.H 2 "Prerequisites"
.\"
.\" Delete this section if it does not apply.
.\"
.\" Every prerequisite of every subsystem should be listed whether it's in
.\" spec file or not. Be sure to include specific release numbers when
.\" the prerequisite is a subsystem in a different product. If there are
.\" many prerequisites, you might want to list them in a table.
.\"
.\" Examples of prerequisite information are:
.\"
.\" If you want to install a.b.c, you must also install a.b.d.
.\" If you want to install a.b.c, release n.0 or later of x.y.z must be
.\" installed.
Your system must be running release IRIX 6.4 and have
XLV installed to use the Disk Plexing Option.
.\"
.\"
.\" Delete this section if it does not apply.
.\"
.\" If any of the subsystems in your product should not be simultaneously
.\" installed with other subsystems (in your product or not), or shouldn't
.\" be installed with particular releases of other subsystems, list these
.\" incompatibilities.
.\"
.\"
.\" Delete this section if it does not apply.
.\"
.\" List the configuration files in your product. Tell what their purpose
.\" is and give users some idea of how and why they might want to modify them.
.\" You should also discuss each of the changes made in each of the
.\" configuration files for this release to make the process of merging
.\" .fp 4 HD
.\" .H 2 "Files Not Listed by \f4versions\fP"
.\" .fp 4 PX
.\"
.\" Delete this section if it does not apply.
.\"
.\" If the product includes postops or exitops that create files, to the
.\" user these files are part of the product. However, the versions
.\" command won't include these files in a file listing of your product.
.\" It would be nice to include a list of these files in the Release Notes
.\" because users have no other way of knowing that these files were created
.\" during installation, are part of your product, and shouldn't be removed.
.\"
.\" .H 2 "Other Installation Information"
.\"
.\" Delete this section if it does not apply.
.\"
.\" Any other installation issues for your product.

225
eoe/relnotes/plexing/ch3.cmm Normal file
View File

@@ -0,0 +1,225 @@
.\" Tips for using this release notes chapter:
.\"
.\" o Use this chapter only if your product uses NetLS licensing.
.\" o Substitute your product's name everywhere that <<PRODUCT>> appears.
.\" o Substitute the names of all of the programs in your product that
.\" use NetLS and their manual page section numbers for <<binary1(1))>>,
.\" <<binary2(1)>>, and <<binary3(1)>>, for example, netlook(1M).
.\" o Licensing is handled in different ways for different products.
.\" Comments in this chapter include substitute paragraphs for some
.\" of the differences; you should modify this chapter as needed for
.\" your product.
.nr H1 2
.H 1 "Activating Your Disk Plexing Option License"
Your copy of the Disk Plexing Option
requires a software license in order to operate.
This chapter defines some important software licensing terms,
describes the basic procedure for obtaining, installing, and
testing a software license for the Disk Plexing Option,
and lists addresses and phone numbers that you can use to contact
Silicon Graphics License Administration.
.P
For more information about software licenses, see the
\f2FLEXlm End User Manual\f1,
which provides detailed information on obtaining, installing,
using, and administering software licenses.
It is included in the system software documentation; the online
version is in the subsystem \f2license_eoe.books.FLEXlm_EUM\f1.
.P
\f2Note that the Disk Plexing Options requires that the license be
installed in a non-standard location. This is necessary because
this software needs to run before the default licensing directories
are available.\f1
.H 2 "A Few Definitions"
A \f2software license\f1 is a collection of information that,
after installation, allows you to use a licensed software
product on one or more systems.
The software license information includes the license type,
the license expiration date, a license password, and system
identification numbers (\f2sysinfo\f1 and serial numbers).
You can get a system's sysinfo number by giving
the command \f8/etc/sysinfo\ -s\f1.
The license must be installed on the system that has the sysinfo
number included in the software license information.
If the sysinfo is ``Any,'' the software license can
be installed on any system.
.P
There are two types of software licenses, \f2node-locked\f1 and
\f2concurrent\f1, and two durations of software licenses,
\f2temporary\f1 and \f2permanent\f1:
.VL 13
.LI node-locked
A node-locked license is installed on a particular system (node)
and allows the licensed software to run on that system.
.LI concurrent
A concurrent license allows the licensed software to run on
one or more systems in the network simultaneously.
The number of systems (nodes) allowed is included
in the software license information.
The system on which a concurrent license is installed must
be configured as a Network License Server.
Any system on the same network must be
configured as a Global Location Broker.
(See the \f2Network License System Administration Guide\f1 for more
information about Network License Servers and Global Location Brokers.)
.LI temporary
A temporary license allows you to use the licensed software
for a short period, typically a week to several months.
The expiration date tells you the last date on
which you can use the licensed software.
Temporary licenses are often shipped with software so that
you can use the software before a permanent license is issued.
.LI permanent
A permanent license allows you to use this release
of the licensed software for a very long time.
For example, an expiration date in the year 2038
indicates a permanent license.
Permanent licenses are issued only for software that has been purchased.
.H 2 "Obtaining and Installing a Software License"
This section explains the procedure for obtaining and installing a
software license: checking to see if you have
received software license information,
determining if you need to install a license,
requesting software license information if you need it,
identifying the system on which you will install the license,
installing the software license information, and
verifying that the license is working.
.AL
.LI
Check to see if you have received software license information.
.P
Software license information is distributed in several ways: on labels
attached to a Software License Registration card, on sheets of paper
included with the product, or by mail, FAX, or electronic mail.
.\" For products that are shipped with two temporary licenses, add this
.\" paragraph:
.\"
.\"This product is shipped with two licenses, both temporary.
.\"One is a node-locked license and the other is a concurrent license.
.\"You can install either one.
.LI
Determine if you need to install a software license.
.P
You may or may not need to install a software license for
the Disk Plexing Option:
.BL
.LI
.\" If you are simply updating your system to this release of
.\" the Disk Plexing Option,
.\" you may not need to install a new license at this time;
.\" your already-installed license may continue to work.
.\"
.\" In situations where a new release requires a new license, substitute
.\" this paragraph (modified as appropriate) for the paragraph above:
.\"
\f2If you are updating to this release of the Disk Plexing Option
from an older release, you must install a new license BEFORE installing
the new software. If the new license is not installed, your system may
not properly restart after the installation.\f1
.LI
If you have received both a temporary license and a
permanent software license, install the permanent license;
do not install the temporary license.
.LI
If you have received a permanent license, you should install it because
it enables you to use the software that you have purchased.
.LI
If concurrent licenses are used at your site and you plan to use an
already-installed license, you can install and use the licensed software
on your system without installing a license.
.LI
If you have received a temporary software license and do not need to use the
software immediately, you may choose to wait to install a license until you
obtain the permanent license.
.LE
.LI
Request a software license if you don't have a software
license at all, or if you have a temporary
license and need a permanent license.
.P
To obtain a software license, fill out the Software License
Registration card that was included with the software (or the
replica in the \f2FLEXlm End User Manual\f1).
Send the information or the card by electronic mail (preferred), FAX, or
mail to Silicon Graphics License Administration or your local service
provider (see the next section for addresses).
After your request is received by Silicon Graphics or your local service
provider, you should receive a software license within two business days.
.LI
Identify the system on which you will install the software license.
.P
Because software license information usually must be installed
on a particular system, follow these guidelines:
.BL
.LI
If the sysinfo is a number, identify the system that returns
that number as the output of the command \f8/etc/sysinfo\ -s\f1.
(It may be easier to identify the system using the serial number,
which is included in the software license information.)
.LI
If the sysinfo is ``Any,'' you can install
the license on any system you choose.
.LI
If the sysinfo number included with the software license information
doesn't match the sysinfo number of the system on which you want to
install the license, contact Silicon Graphics License Administration.
.LE
.LI
Install the software license (temporary or permanent).
.P
The Disk Plexing Option uses a node-locked license.
The license for the Disk Plexing Option must be installed in
.IR /etc/flexlm/license.dat .
This is a nonstandard location.
.P
To install the license, log into the root account and
create or edit the
.I /etc/flexlm/license.dat
file using jot(1G) or your preferred editor. Type:
.P
\f4jot /etc/flexlm/license.dat\f1
.P
Add the license to the license file. Save the file and exit the editor.
.P
Save the license information sheet; you may need it again later,
if you need to reinstall this license.
.\" If this product includes its own license installation tool (for
.\" example nvlicense for NetVisualyzer, mention that tool here.
.LI
Verify that the software license has been successfully installed.
.P
To verify that the software license is working
after software installation, run
.IR xlv_mgr (1m)
and invoke the
.I "show config"
command.
.I xlv_mgr
will display whether or not the Disk Plexing Option is present.
.P
If you installed a temporary license and you are entitled to a
permanent license,
replace the temporary license with a permanent license as soon as possible
to ensure uninterrupted use of the Disk Plexing Option.
.H 2 "Contacting Silicon Graphics License Administration"
In the United States and Canada, Silicon Graphics License Administration
provides software license information to Silicon Graphics customers.
You can contact Silicon Graphics License Administration in these ways:
.VL 15
.LI "Electronic mail:"
license@sgi.com
.LI FAX:
(415) 390-0537
.LI Mail:
Software Licensing M/S 134
.nf
Silicon Graphics, Inc.
P.O. Box 7311
Mountain View, CA 94039-9600
.fi
.LE
In an emergency, you can telephone Silicon Graphics at (800) 800-4744.
.P
If you are not in the United States or Canada, or if you purchased the
system or software from a vendor other than Silicon Graphics, please
contact your local service provider.

48
eoe/relnotes/plexing/ch4.cmm Normal file
View File

@@ -0,0 +1,48 @@
.nr H1 3
.H 1 "Bug Fixes"
.\"
.\"What bugs have been fixed in <product> since its last release?
.\"
This chapter lists the bug fixes in Disk Plexing Option since
the last release (IRIX 6.2). Some descriptions include
a Silicon Graphics bug report number in the form \f2XXXX\f1 or \f2XXXXXX\f1.
.BL
.LI
xlv_labd(1m) is automatically started if a plex revive request is issued
and the xlv_labd does not exist.
.LI
Losing a disk drive that is part of a root volume can sometimes
cause the system to hang.
(bug #392195)
.LI
A plexed root drive could be corrupted if one plex was detached/attached,
and the system was then cleanly shutdown and rebooted.
(bug #422798)
.LI
Xlv_mgr(1m) core dumps detaching a NULL volume element from a standalone plex.
(bug #426966)
.LI
Only mark the target disk online after a revive if no errors occured.
.LI
Xlv_assemble(1m) won't gratuitously initiate a plex revive for a
triple-plexed volume element when the volume element was cleanly shutdown.
(bug #341023)
.LI
Xlv_mgr(1m) "detach" command has a new -force option so a missing
plex or volume element can be removed. This allows broken disks to be
easily replaced.
.LI
Xlv_mgr(1m) "show kernel" command displays plex revive progress.
The mapping of the subvolume open_flag value has been corrected.
A volume name can be specified so that only information pertaining
to that kernel volume is displayed.
.LI
Fixes a kernel panic if plexing software is not installed
and an I/O error occurs on a RAID device.
(bug #363121)
.LI
Fail over to an alternate controller on a dual controller SGI RAID device
only works on lun 0.
Luns other than 0 were not properly switched over to the alternate path.
(bug #370878)
.LE

93
eoe/relnotes/plexing/ch5.cmm Normal file
View File

@@ -0,0 +1,93 @@
.nr H1 4
.H 1 "Known Problems and Workarounds"
This chapter describes the known problems in release 2 of
the Disk Plexing Option.
See the IRIX Release 6.4 release notes for non-plexing
related problems with the XLV subsystem.
.\"
.\" Known problem with <product> and ways to work around them.
.\"
.\"
.BL
.LI
XLV allows you to mirror the root disk. However, the root volume can only
be plexed. It cannot be striped or concatenated.
.\"
.\" .LI
.\" When you are converting an
.\" .IR LV (7M)
.\" volume to XLV, make sure that you edit
.\" .I /etc/fstab
.\" so that the same disks are not simultaneously mounted as both an LV
.\" and an XLV volume. Doing so can cause data corruption.
.\" (Note that
.\" .IR xlv_make (1M)
.\" normally prevents you from including an LV partition in an XLV
.\" volume. This check, however, is turned off when you run
.\" .IR lv_to_xlv (1M)
.\" since you are explicitly doing a conversion in this case.
.\" .LI
.\" An XLV logical volume does not have a disk volume header (see
.\" .IR vh (7M)).
.\" For example, if you have a volume named
.\" .IR /dev/dsk/xlv/xlv_root ,
.\" there is no corresponding
.\" .I /dev/rdsk/xlv/xlv_root_vh
.\" device. This can cause problems when your root filesystem is a
.\" logical volume and you are installing software (such as
.\" .I stand
.\" and
.\" .IR ide )
.\" that are normally copied into the volume header of the root disk.
.\" .P
.\" When this happens, you will get a "Can't access /dev/rdsk/xlv_*vh" message from
.\" .IR inst (1M).
.\" The workaround is to go into the shell and create a symbolic link to the
.\" volume header of the first physical disk that make up the volume. For example,
.\" you can use: \f2ln -s /dev/rdsk/dks0d1vh /dev/rdsk/xlv_root_vh\f1.
.\"
.\" .LI
.\" If your root volume is plexed, you should manually copy
.\" .I stand
.\" from the original volume header to all the other plexes. This can be done via
.\" .IR dvhtool (1M).
.\" You need to have copies of
.\" .I stand
.\" so that you can boot off one of the
.\" other plexes if the plex that you normally boot from fails.
.LI
The license for the XLV plexing capabilities (Disk Plexing Option) is
installed in
.I /etc/flexlm/license.dat
instead of
.IR /usr/var/flexlm/license.dat .
This is necessary because
.I /usr
may be on a logical volume and XLV needs to check the license before
assembling any logical volumes.
.\"
.\" Bug 249296 xlv_assemble needs to mark one plex from a brand new
.\" subvolume element
.\"
.LI
When a new volume is created, all volume elements in
each plex are initialized to the
.I empty
state. Volume elements in a mirrored volume
are transitioned to the
.I active
state after a plex revive operation is done on them.
When a plex revive operation is in progress,
the volume element cannot be changed by
.IR xlv_mgr (1M).
The duration of a plex revive operation depends on the size
of the volume element. If administration
is desired before the plex revive can be completed, use
.IR xlv_set_primary (1M)
to set all the volume elements in a plex
.IR active .
But this can be dangerous if the wrong plex is chosen to be the
active plex.
.\"
.LE
.Ee

344
eoe/relnotes/plexing/ch6.cmm Normal file
View File

@@ -0,0 +1,344 @@
.nr H1 5
.H 1 "Documentation Errors"
.\"
.\"List of errors in the product's user's/programmer's guides.
.\"
.\"
The following are some additional information about using the
Disk Plexing Option.
.H 2 "Creating a plexed root volume"
You can put your root filesystem on a plexed volume for greater
reliability. A plexed root volume allows your system to continue
running even if one of the root disks fail.
.P
A root volume can contain only a data subvolume. This subvolume can
be plexed. However, each plex can contain only a single disk.
The root filesystem can be either an EFS filesystem or an XFS
filesystem with an internal log.
.P
The following is the procedure for creating a plexed root volume:
.AL
.LI
We assume that we are starting with a system disk that already has
a filesystem and the right software installed.
If not, prepare the system disk by running
.I mkfs
and installing all the necessary software.
.LI
Make the root disk into an XLV volume. For this example, assume
that
.I /dev/dsk/dks0d1s0
is the root disk.
.P
.Ex
\f7xfs4 5# \f8xlv_make\f7
xlv_make> \f8vol xlv_root\f7
xlv_root
xlv_make> \f8data\f7
xlv_root.data
xlv_make> \f8ve -force /dev/dsk/dks0d1s0\f7
xlv_root.data.0.0
xlv_make> \f8end\f7
Object specification completed
xlv_make> exit
Newly created objects will be written to disk.
Is this what you want?(yes) \f8yes\f7
Invoking xlv_assemble
xfs4 6#
.Ee
.P
The result is that we have an XLV volume named
.I xlv_root
that contains
the root disk. Since XLV preserves the data in the user partitions,
the contents of the root disk are preserved.
Note that we used the
.I -force
option in
.IR xlv_make (1m)
because we are making a mounted disk partition into an XLV volume.
.LI
Prepare the second plex. This involves creating the plex in XLV and
also copying
.I sash
into the volume header in that plex. (We need to have a copy of
.I sash
on the alternate plex so we can boot off the alternate plex should
the primary plex fail.)
.Ex
\f7xfs4 7# \f8xlv_make\f7
xlv_make> \f8show\f7
Completed Objects
(1) vol xlv_root
ve xlv_root.data.0.0 [active]
start=0, end=1992629, (cat)grp_size=1
/dev/dsk/dks0d1s0 (1992630 blks)
xlv_make> \f8plex plex1\f7
plex1
xlv_make> \f8ve /dev/dsk/dks0d2s0\f7
plex1.0
xlv_make> \f8end\f7
Object specification completed
xlv_make> \f8exit\f7
Newly created objects will be written to disk.
Is this what you want?(yes) \f8yes\f7
Invoking xlv_assemble
.Ee
.P
Now we update the volume header of the second plex with
.IR sash .
Since
.I sash
is normally installed in the volume header of the root disk,
we can use
.IR dvhtool (1m)
to do so.
.Ex
\f7xfs4 3# \f8dvhtool -v get sash /tmp/sash /dev/rdsk/dks0d1vh\f7
xfs4 4# \f8dvhtool -v add /tmp/sash sash /dev/rdsk/dks0d2vh\f7
xfs4 5#
.Ee
.P
If they exist in the volume header of the root disk, you may also wish to
copy over
.I symmon
and
.I ide
into the volume header of the second plex using the same procedure.
.LI
At this point, you have a root volume that consists of a single
plex and a standalone plex of the same size. You can now attach the
plex to the volume using
.IR xlv_mgr (1m).
.Ex
\f7xfs4 9# \f8xlv_mgr\f7
xlv_mgr> \f8attach plex plex1 xlv_root.data\f7
xlv_mgr>
.Ee
.LI
You can make sure that the disk labels are updated correctly
by running
.I xlv_assemble
.IR -n .
The
.I -n
option tells
.IR xlv_assemble (1m)
to just read the disk labels but not make the volume active.
.Ex
\f7xfs4 10# \f8xlv_assemble -n\f7
VOL xlv_root flags=0x1, [complete]
DATA flags=0x0() open_flag=0x0() device=(192, 4)
PLEX flags=0x0
VE [active]
start=0, end=1992629, (cat)grp_size=1
/dev/dsk/dks0d1s0 (1992630 blks)
PLEX flags=0x0
VE [empty]
start=0, end=1992629, (cat)grp_size=1
/dev/dsk/dks0d2s0 (1992630 blks)
.Ee
Note how the root volume
.I xlv_root
now has two plexes. At this point,
you should see disk activity because XLV will start a plex revive
operation which will copy the contents of the original plex to the newly added plex.
.LI
At this point, we've created our plexed root volume. However,
the system is still running directly off the original boot disk,
.IR /dev/dsk/dks0d1s0 .
We now need to reboot the system so that it will
run on the XLV volume instead. Note that you do not need for the plex
revive to finish because revive will be restarted when the system
comes back up.
.P
.IR Warning ,
you should not mount the root volume at this time. This is because the
one of the underlying physical disks
.I /dev/dsk/dks0d1s0
is still
mounted as the root filesystem. Mounting the same set of disks at two
different mount points simultaneously can corrupt your filesystem.
.Ex
\f7xfs4 12# \f8init 6\f7
xfs4 13#
INIT: New run level: 6
The system is shutting down.
Please wait.
Unmounting cache file systems:
Removing swap areas.
Unmounting filesystems:
Starting up the system...
IRIX Release 5.3-xfs IP22 Version 11221102 System V
Copyright 1987-1994 Silicon Graphics, Inc.
All Rights Reserved.
WD95A SCSI controller 4 - differential external, rev 0, min xfer period 100ns
WD95A SCSI controller 5 - differential external, rev 0, min xfer period 100ns
xpi0: missing from slot 1
xpi0: missing from slot 0
xpi0: not an FDDI board in slot 2
gtr0: missing
gtr0: missing
The system is coming up.
rootfs=/dev/dsk/xlv_root
Starting XLV:
XLV Volume "xlv_root" [complete]
The system is coming up.
Mounting filesystems:
Configuring ec0 as xfs4
...
Mounting cache file systems:
The system is ready.
xfs4 login: \f8root\f7
IRIX Release 5.3-xfs IP22 xfs4
Copyright 1987-1994 Silicon Graphics, Inc. All Rights Reserved.
Last login: Wed Nov 23 12:16:13 PST 1994 on ttyd1
Welcome to xfs4
TERM = (iris-ansi)
.Ee
.P
At this point, we are running off the
.I xlv_root
volume. You can verify this by looking at
.IR /dev/root .
Note how its device number
.I (192,0)
matches that displayed by
.IR xlv_assemble (1m):
.Ex
\f7xfs4 1# \f8ls -l\f7
brw------- 2 root sys 192, 0 Oct 31 17:58 /dev/root
xfs4 2# \f8xlv_assemble -n\f7
VOL xlv_root flags=0x1, [complete]
DATA flags=0x0() open_flag=0x0() device=(192, 0)
PLEX flags=0x0
VE [active]
start=0, end=1992629, (cat)grp_size=1
/dev/dsk/dks0d1s0 (1992630 blks)
PLEX flags=0x0
VE [stale]
start=0, end=1992629, (cat)grp_size=1
/dev/dsk/dks0d2s0 (1992630 blks)
.Ee
.LI
At this point, we are running off both plexes. However, XLV
is still copying the data from the original plex to the newly
created plex. You can tell that a plex copy is in progress by typing:
.Ex
\f7xfs4 3# \f8ls -ef | grep xlv_plexd\f7
root 881 27 0 14:06:58 ? 0:00 xlv_plexd -v 2 -n root_vol.data -d 50331648 -b 128 -w 0 0 1992629
.Ee
The command line arguments to the xlv_plexd shows the volume being
revived. The revive is done when that daemon exits.
.H 2 "Booting off an alternate plex"
Once you have a plexed XLV root volume, you can boot off a secondary
plex if the primary plex became unavailable. Note that you should
do this only after the secondary plex has become active. (You can
see its state by running
.I xlv_mgr
or by running
.I xlv_assemble
.IR -n .)
.P
Since the boot prom does not understand logical volumes, you need
manually reconfigure the system to use an alternate disk. In this
case, you need to specify the disk that makes up the alternate plex
that you want to boot off.
This is how you do it for a Challenge S system:
.Ex
System Maintenance Menu
1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor
\f7Option? \f85\f7
Command Monitor. Type "exit" to return to the menu.
>> \f8printenv\f7
SystemPartition=dksc(0,1,8)
OSLoadPartition=dksc(0,1,0)
OSLoader=sash
OSLoadFilename=/unix
AutoLoad=No
rbaud=9600
TimeZone=PST8PDT
console=d
...
ConsoleIn=serial(0)
cpufreq=150
>> \f8setenv SystemPartition dksc(0,2,8)\f7
>> \f8setenv OSLoadPartition dksc(0,2,0)\f7
>> \f8boot\f7
84032+11488+3024+331696+26176d+4088+6240 entry: 0x89f97610
Standalone Shell SGI Version 5.3 ARCS Nov 18, 1994 (BE)
sash: boot
2922736+845584+212992 entry: 0x88062950
IRIX Release 5.3-xfs IP22 Version 11221102 System V
Copyright 1987-1994 Silicon Graphics, Inc.
All Rights Reserved.
WD95A SCSI controller 4 - differential external, rev 0, min xfer period 100ns
WD95A SCSI controller 5 - differential external, rev 0, min xfer period 100ns
xpi0: missing from slot 1
xpi0: missing from slot 0
xpi0: not an FDDI board in slot 2
gtr0: missing
gtr0: missing
rootfs=/dev/dsk/xlv_root
Starting XLV:
XLV Volume "xlv_root" [complete]
The system is coming up.
Mounting filesystems:
Configuring ec0 as xfs4
...
Mounting cache file systems:
The system is ready.
xfs4 login: \f8root\f7
IRIX Release 5.3-xfs IP22 xfs4
Copyright 1987-1994 Silicon Graphics, Inc. All Rights Reserved.
Last login: Sat Nov 26 07:40:05 PST 1994 on ttyd1
Welcome to xfs4 -- XFS group's test system
17-Nov-94 -- Running 5.3+xfs, bitbucket:/e/dist/XFS.oct17h
TERM = (iris-ansi)
.Ee

39
eoe/relnotes/plexing/front.x Normal file
View File

@@ -0,0 +1,39 @@
.nr TY 2
.\" This file is the source file for the cover and credits pages included
.\" in printed release notes.
.\"
.\" The lines below should be editted to match your product by replacing
.\" the words in angle brackets (<>) with your text.
.\" The document part number should be obtained from the Tech Pubs folks, if you
.\" do not know it. It normally changes from release to release.
.\"
.\" NOTE: there must be *no* white space at the ends of lines in this file,
.\" or punctuation will be incorrect in the resulting copy.
.\"
.\" first line of Release Notes title (<= 4.25 inches long)
.ds TI Disk Plexing Option Release Notes
.\" second line of Release Notes title
.\".ds TJ
.\".ds TK
.\" document part number (xxx-xxxx-xxx)
.ds DN xxx-xxxx-xxx
.\" list of names after "Written by" on the credits page
.\" (separate names by commas and let the line wrap if it is very long)
.ds WB Wei Hu, James Leong
.\" name(s) after "Editted by" (names are comma-separated)
.\".ds EB <names>
.\" name(s) after "Illustrated by" (names are comma-separated)
.\".ds IB <names>
.\" name(s) after "Production by" (names are comma-separated)
.\".ds PB Diane Wilford
.\" list of names after "Engineering contributions by"
.\" (separate names by commas and let the line wrap if it is very long)
.ds EG Wei Hu, James Leong, Terrie Carver
.\" copyright year for the credits page (e.g. 1992)
.ds YR 1994
.\" trademark information (use as many lines as you need)
.de TR
Silicon Graphics and IRIS are registered trademarks and IRIX is a trademark
of Silicon Graphics, Inc.
UNIX is a registered trademark of UNIX System Laboratories, Inc.
..