RDF System Management Manual

Managing RDF
HP NonStop RDF System Management Manual—524388-003
5-2
Recovering From File System Errors
Recovering From File System Errors
Errors detected by the file system generate error numbers that appear within RDF
messages reported in the EMS event log. Of particular importance are the file system
errors that can cause RDF event messages 700 (modify operation), 705 (open
operation), or 739 (create operation). As an example, file system error 59 appears in
the following RDF event message 705:
10:59 \RDF05 $WU02 705 File open error 59 on $DATA07.QD004378.RFILE02
Tables 5-1, 5-2, and 5-3 list the file system error numbers and appropriate recovery
actions. In general, when any of these errors occurs, one of the following actions
results:
•
The event is reported in the EMS event log, with the error causing the process that
received it to restart from a previously set restart point.
•
The event is reported in the EMS event log, and the requested operation is
skipped.
For information about restart points, see Updater Processes in section 1.
To analyze an error, consult the appropriate table in this discussion, reading about any
corrective action specific to RDF. Then, for further information about the message (its
cause, effect, and general recovery procedures), see the file system section of the
Guardian Procedure Error and Messages Manual.
Some errors might require you to resynchronize certain files; see the EMS event log for
further information. Any error that cannot be explained should be reported to your
service provider.
For information about the causes, effects, and recovery actions for all RDF event
messages, see Appendix C, Messages. When present, file system error numbers
appear in the error# parameter of these messages.
Table 5-1 lists the file system error numbers and recovery actions for RDF event 700,
which reports file-modification failures.