| Previous | Next |
| CI_E_FILTERING_DISABLED | CI_E_SHUTDOWN |
CI_E_DISK_FULL
The underlying index volume has no usable free space
CI_E_DISK_FULL is HRESULT 0x80041811 (-2147215343 signed; 2147751953 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF for these values), and code field is 0x1811. Standard HRESULT severity rules classify the value as a failure. AllStat describes the value as “The disk is full and the specified operation cannot be done.”
API stage and meaning
This result belongs to writing catalog, property-store or temporary indexing data. The decisive interpretation is that the filesystem cannot satisfy the write required by the current content-index operation. Keep the symbolic constant and method stage together in logs; its hexadecimal value alone cannot identify the owning transition or input.
The legacy content-index helper layer has explicit object, catalog and service states. In the result investigation, a generic retry can hide lifecycle, ordering or policy defects. This context narrows the responsible component without replacing the code-specific checks below.
Failure paths
- The result investigation should record the volume is physically full.
- The result investigation should record reserved space or quotas block the service.
- The result investigation should record temporary filtering data consumes the remaining capacity.
- The result investigation should record another workload fills the disk during indexing.
The useful hypothesis for it must explain both writing catalog, property-store or temporary indexing data and the documented condition. Compare the failing case with a control that preserves volume identity and free bytes and changes only quota/reservation state; this prevents unrelated environment differences from dominating the result test.
Observability checklist
- At step 1 for it, volume identity and free bytes
- At step 2 for it, quota/reservation state
- At step 3 for it, path receiving the failed write
- At step 4 for it, growth rate and largest catalog files
Capture volume identity and free bytes before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with quota/reservation state, component version, UTC timestamp and correlation ID. Bound the result telemetry to diagnostic metadata because document content, credentials and unrestricted query text may be sensitive.
How to isolate the cause
- Measure free space from the service context. Associate this observation specifically with this result.
- Identify the exact catalog or temporary path.
- Separate filesystem full from configured catalog limit.
- Check for runaway retries or orphaned temporary files. Associate this observation specifically with it.
Change one variable per it control run. Preserve the component version and target identity, then alter only the condition described as the filesystem cannot satisfy the write required by the current content-index operation. This isolates whether it is causal rather than merely repeatable.
Remediation policy
Free or extend storage and verify catalog consistency before bounded retry. Do not delete catalog files manually while the service owns them. Record whether writing catalog, property-store or temporary indexing data produced any content, update or state transition before returning. If completion remains unknown, the path must not replay non-idempotent work until the owner confirms final state.
The retry gate for it should be a concrete change in volume identity and free bytes or quota/reservation state. A timer alone cannot demonstrate that the result contract condition has changed.
Wrong conclusions to avoid
It does not mean the configured content-index size ceiling was reached. Without the call boundary for writing catalog, property-store or temporary indexing data, it also cannot identify which wrapper or configuration layer introduced the condition.
Comparison
CI_E_CONFIG_DISK_FULL is a configured limit; it reflects actual write capacity. In it telemetry, preserve neighboring constants separately because the same visible symptom may require a different caller action, owner or recovery gate.
Developer and administrator actions
- It: At the code boundary, keep volume identity and free bytes beside the returned HRESULT.
- It: In telemetry, correlate quota/reservation state with the target and component generation.
- It: For regression coverage, force the documented condition: the filesystem cannot satisfy the write required by the current content-index operation.
- It: For operations staff, expose the corrective state change rather than a generic retry button.
- It: After remediation, validate one known-good control and the original failing case.
Worked scenario
A catalog shares a volume with verbose logs that consume the final gigabytes. Volume-level telemetry identifies the external growth source. In this scenario, handling it at its real contract boundary prevents the application from collapsing a precise state into an unhelpful generic “search failed” message.
Official Microsoft references
- Microsoft: content-indexing helper-function values — official contract information relevant to it.
- Microsoft: Content-Indexing values
- Microsoft: HRESULT values
- Microsoft: Windows Search SQL syntax
Looking for a different code? Search another status or error code.