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

Table 12 Recovery From File Creation Failures (RDF Event 739) (continued)
Recovery ActionFile System Error
Repair the device or clear the condition.60 through 66
Repair the device or clear the condition.100
Repair the device or clear the condition.103
Repair the device or clear the condition.120 through 121
Repair the device or clear the condition.130 through 139
Check file integrity.157
Repair the device or clear the condition.190
Alter the security (probably Safeguard).199
Repair the device or clear the condition.200 through 231
Handling Disk Space Problems
When creating a new image file, the receiver preallocates 16 disk extents. If there is not enough
disk space, the receiver encounters a file-system error 43 when it tries to preallocate these extents.
The receiver retries the preallocation every 5 seconds and reports the problem at approximately
60-second intervals. The receiver continues trying to preallocate the disk space indefinitely.
While the error 43 condition exists, the receiver can only:
• Provide information for STATUS RDF commands
• Respond to STOP RDF commands
The error 43 condition persists until enough disk space is available for an image file.
During an error 43 condition, the receiver may not be able to accept any more images from the
extractor if its current image trail file is completely filled.
If you free enough disk space on the image volume to clear the error 43 condition, however,
processing resumes automatically. You can do this by moving any files that might not be needed
(be sure, however, to restore them before the receiver and updaters need them). Alternatively, you
can accomplish this goal by backing up (with the BACKUP utility) an unopened image file, then
purging that file, and finally restoring it (with the RESTORE utility) when the first file-system error 11
(file not in directory) is reported for the file by an RDF process on the backup system. See the
section “Backing Up Image Trail Files” (page 144).
Because the receiver cannot accept any more images from the extractor, an error 43 condition on
the backup system causes the extractor to stop progressing through the audit trail files and RDF to
fall behind TMF (TMF, however, continues to generate audit data).
If an error 43 persists on the disk when you issue the STOP RDF command, the subsystem shuts
down successfully without requiring allocation of extents for the new file. In this case, however,
before you restart the subsystem with the START RDF command, you must make this space available
for at least two files per image trail; otherwise, the START RDF command aborts.
If the error 43 condition is cleared before it becomes necessary to stop RDF, both the primary and
backup systems continue their normal operations.
If an updater reports error 43, it stops replicating the audit until you make space available on that
disk. Like the receiver, after you make space available, the updater automatically resumes
operations.
Exceeding the Maximum Number of Concurrent File Opens
The maximum number of audited files a single updater can have concurrently open is 3,000. If
you have more than 3,000 audit files being replicated by a single updater, then it is possible that
116 Critical Operations, Special Situations, and Error Conditions