| Previous | Next |
| ERROR_BEGINNING_OF_MEDIA | ERROR_NO_DATA_DETECTED |
ERROR_SETMARK_DETECTED
a tape access reached the end of a set of files.
ERROR_SETMARK_DETECTED means that a tape operation encountered a setmark, a logical boundary separating a group of tape files.
Where the result appears
- backup formats that group several logical files into a set.
- tape cataloging and restore navigation.
- sequential-media verification.
- positioning operations that count setmarks.
Typical causes
- the current backup set ended as designed.
- the caller expected another file within the same set.
- the tape was positioned into the wrong backup set.
- catalog metadata does not match the recorded mark structure.
What to collect
- set identifier, expected file count, current file/block position, and catalog data.
- operation mode and whether setmarks are returned or skipped.
- drive status and bytes processed before the boundary.
- media sequence and any prior append or overwrite operation.
Handling and recovery
Advance to the next set only when the restore or catalog plan expects it. For append operations, preserve the existing set boundary semantics. Unexpected setmarks require catalog reconciliation rather than blind skipping.
Common misinterpretation
A setmark is not necessarily end of media. It is a higher-level logical separator defined by the tape format.
References
Looking for a different code? Search another status or error code.