| 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. In this case, the decisive context is backup formats that group several logical files into a set, together with set identifier, expected file count, current file/block position, and catalog data.
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.
Evidence 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.
For this condition, begin the investigation with set identifier, expected file count, current file/block position, and catalog data. Correlate it with operation mode and whether setmarks are returned or skipped and check whether the current backup set ended as designed. Capture the original this result immediately after the failing call so later cleanup does not replace the thread-local error value.
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.
Any retry policy for it should be tied to evidence that the caller expected another file within the same set has changed. Before another attempt, verify drive status and bytes processed before the boundary. If catalog metadata does not match the recorded mark structure still applies, stop the retry sequence and preserve the first diagnostic event.
Common misinterpretation
A setmark is not necessarily end of media. It is a higher-level logical separator defined by the tape format.
Guidance for developers
When surfacing this result through another layer, retain its Win32 domain, numeric value, and the operation described by tape cataloging and restore navigation. A useful telemetry record also includes media sequence and any prior append or overwrite operation. For a-related handling, decisions must use the numeric value and documented API contract rather than localized wording.
A focused test should reproduce the condition in which the tape was positioned into the wrong backup set, assert this result, and confirm that the program releases resources associated with sequential-media verification. The recovery test should also verify that set identifier, expected file count, current file/block position, and catalog data is refreshed before the operation resumes.
References
Looking for a different code? Search another status or error code.