| Previous | Next |
| FILTER_S_CONTENTSCAN_DELAYED | FILTER_S_NO_PROPSETS |
FILTER_S_DISK_FULL
Indexing warns that disk space is becoming exhausted
FILTER_S_DISK_FULL is HRESULT 268085 (0x00041735) from Indexing Service. AllStat describes it as “The disk is getting full.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.
In the legacy Indexing Service or IFilter pipeline, this result means that the disk is getting full. Handling of it is complete only after the caller verifies what work occurred and what remains outstanding.
Where the status is encountered
- Legacy Indexing Service catalog processing; log the exact method and object state instead of interpreting the constant outside that contract.
- IFilter text and property extraction; log the exact method and object state instead of interpreting the constant outside that contract.
- Search enumeration, scan scheduling, or catalog administration; log the exact method and object state instead of interpreting the constant outside that contract.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
What must be true before accepting it
Verify that the service can prevent catalog corruption and retain enough space for checkpoint or rollback operations. Failure to prove the boundary can make it look healthy while the intended operation remains unfinished.
Classify the operation phase reached at it before releasing objects or issuing replacement work.
Evidence and telemetry
- preserve volume free bytes and configured threshold.
- preserve catalog and temporary directory sizes.
- preserve growth rate.
- preserve current scan checkpoint.
- preserve cleanup actions and resumed generation.
Also record filter_s_disk_full_operation, filter_s_disk_full_state_before, filter_s_disk_full_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Keep it traces useful by recording object identity and timing while excluding authentication or content secrets.
Difference from nearby results
It must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.
The semantic difference represented by it should be visible in both control flow and operational metrics.
Correct handling and recovery
Throttle or pause indexing, measure catalog and temporary-file growth, free or extend storage, then resume from a verified checkpoint.
Retry it only when a documented input or state has changed. Only a meaningful state transition should cause a repeated request after it.
Practical scenario
During a full scan the catalog volume crosses its safety threshold. The service pauses new ingestion, removes obsolete catalogs, and resumes only after free-space headroom is restored.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
References
- Microsoft: Filter interface values — official Microsoft material used to interpret it.
- Microsoft: About Indexing Service filters
- Microsoft: Using custom filters
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.