RDF System Management Manual for J-series and H-series RVUs (RDF Update 13)

Effect
The command fails.
Recovery
Scan the EMS event log to determine why the command could not be performed. Correct the
error condition, if possible, and request the update operation again.
VOLUME device is NOT a disk volume
device
is the non-disk device assigned to the updater.
Cause
The RDF configuration file is invalid.
Effect
RDF will not start.
Recovery
Change the RDF configuration to reflect a valid disk volume.
VOLUME device UPDATEVOLUME is NOT a disk volume
device
is the non-disk device assigned for the UPDATEVOLUME.
Cause
The RDF configuration file is invalid.
Effect
RDF will not start.
Recovery
Change the RDF configuration to reflect a valid disk volume.
VOLUME Record exists, use ALTER VOLUME volume
Cause
An ADD VOLUME command was issued when the configuration file already contained an updater
record for the volume.
Effect
The RDF command fails.
Recovery
No recovery is required if you want to use the existing updater process as it is configured. If
you want to change any of the updater’s configuration options, however, enter an ALTER VOLUME
command that specifies those changes.
VOLUME volume contains too many physical volumes The SMF pool cannot
contain more than 21 volumes
volume
is the offending SMF virtual disk
Cause
The updater is configured to a virtual SMF disk that consists of more than 21 physical disks. This
configuration is not supported by the RDF product.
Effect
RDF will not start.
Recovery
Reset your RDF configurations and/or your SMF configuration so that the updaters are either
assigned to physical volumes, or your SMF virtual disks map to 21 or fewer physical volumes.
480 Messages