rdup(8) rdup(8)
NAME
rdup - establishing the mount capability of RAID systems (PXRC, PXRE,
EMC-SYMMETRIX) when booting
SYNOPSIS
rdup [init | start | stop]
DESCRIPTION
rdup is a startup script used to establish the operability (mount
capability) of RAID systems (PXRC, PXRE, EMC-SYMMETRIX) at boot time.
Since it generally takes longer to boot RAID systems (particularly
EMC-SYMMETRIX) than to boot the host, these RAID systems must be
operational for the purpose of synchronizing the mount activities
(Definition: a RAID system is operational if it is entered in the
autoconf tree).
To safeguard this synchronization, the RAID startup check (rdup start)
uses an RC2 S01rdup script to cyclically compare the RAID controllers
in the autoconf tree with the target configuration predefined and
expected in a RAID configuration file (/etc/rdstartup).
A reprobe [see reinitdev(8)] is carried out on the affected SCSI port
(sport) for each outstanding RAID controller. The RAID startup check
is terminated when all RAID controllers have been found in the auto-
conf tree; the DRAID draidd(1M) daemon, assuming it is active, is res-
tarted to take account of the current configuration.
If all controllers are not found in the autoconf tree, the RAID
startup check ends after 60 minutes with a timeout; moreover, the sys-
tem administrator can abort the RAID startup check at any time with
<CR> plus confirmation. A switch is made to single user mode in both
cases to give the system administrator the opportunity to make correc-
tions. Any RAID controllers still outstanding are logged in /dev/osm.
The RAID /etc/rdstartup configuration file must be created by the sys-
tem administrator using the rdup init command from an up-to-date auto-
conf tree. If there is no configuration file available, the RAID
startup check assumes that there are no RAIDs configured on this sys-
tem.
Notes:
- Since S01rdup is started after S01MOUNT0FSYS, Level-0 file systems
must not be mounted on RAID systems!
- You need root rights to use rdup.
Page 1 Reliant UNIX 5.44 Printed 11/98
rdup(8) rdup(8)
OPTIONS
init The system administrator can/must use the rdup init command to
create the /etc/rdstartup RAID configuration file. The exist-
ing autoconf tree is used here. At boot time (rdup start),
this configuration file is compared cyclically with the
respective autoconf status.
The configuration file contains the RAID ports (sports) with
the associated controllers, for example:
# cat /etc/rdstartup
sport06 sraid060 # EMC-SYMMETRIX
sport06 sraid061 # PXRE-F
sport07 sraid070 # PXRC
.....
If no RAID systems are found in the autoconf tree, no confi-
guration file will be created.
init always terminates with exit status 0.
Important:
- rdup init must be invoked manually by the system adminis-
trator both after the first installation and after every
configuration change in RAID systems.
- The system administrator must ensure that all RAID systems
are entered in the autoconf tree at this time.
- The system administrator can edit the configuration file
for the purpose of selecting the relevant RAID systems for
monitoring.
start rdup start is executed as an RC2 S01rdup script (RAID startup
check) when the system boots.
rdup start cyclically compares (every 30 seconds) the RAID
controllers available (= operational) in the current autoconf
tree with the RAID controllers entered in the configuration
file. If no configuration file exists, the exit status 0 is
returned immediately.
Provided there are still RAID controllers missing in the auto-
conf tree, a reprobe [see reinitdev(8)] will be carried out on
the associated ports (sports).
As soon as the autoconf configuration complies with the confi-
guration file, the RAID startup check terminates with exit
status 0; moreover, the DRAID draidd(1M) daemon is restarted,
assuming it is active, to take account of the current RAID
status.
Page 2 Reliant UNIX 5.44 Printed 11/98
rdup(8) rdup(8)
Termination with a timeout:
If a controller is not found, a timeout occurs after 60
minutes. The user can also abort the RAID startup check at any
time by hitting <CR> (plus positive acknowledgement). In both
cases, exit status 100 forces a switch to single user mode to
give the system administrator the opportunity to make correc-
tions; the outstanding RAID systems are logged in /dev/osm.
stop Dummy option with exit status 0, to comply with the RC script
conventions.
FILES
/dev/autoconf
This device node contains the currently operational RAID systems,
for example.
/etc/rdstartup
RAID configuration created with rdup init; it contains the RAID
configuration that is compared at boot time (rdup start) with the
current autoconf status. The configuration file contains the RAID
ports (sports) with the associated controllers, e. g.:
# cat /etc/rdstartup
sport06 sraid060 # EMC-SYMMETRIX
sport06 sraid061 # PXRE-F
sport07 sraid070 # PXRC
....
Notes:
- In theory, you can connect various RAID systems to a sport
port; this is taken into account when the configuration file
is set up.
- Using an editor, users can select the RAID systems (to be mon-
itored) that are relevant for them.
/dev/osm
When the RAID startup check is aborted by a timeout or by the
user, the overdue RAID systems are logged in /dev/osm for poster-
ity.
An entry is also logged in /dev/osm if there are more RAID sys-
tems in the autoconf tree than are entered in the configuration
file; this may happen if the configuration file is not up to date
or has been modified.
Page 3 Reliant UNIX 5.44 Printed 11/98
rdup(8) rdup(8)
EXIT STATUS
0 Normal termination:
- All RAID systems are to be booted according to the configura-
tion file or
- no /etc/rdstartup configuration file is available, i. e. no
RAID systems are connected.
- rdup init is always accompanied by exit status 0; if a confi-
guration file has not been created, no RAID systems are con-
figured or exist in the autoconf tree.
100 Abnormal termination (exit status 100 forces single user mode)
with a
- timeout after 60 minutes or
- abort of the startup check by a user prompt.
The RAID systems that are still outstanding at this time are
logged in /dev/osm.
SEE ALSO
draidd(1M), autoconf(8), reinitdev(8).
Page 4 Reliant UNIX 5.44 Printed 11/98