HEART storage.nearly-full H-04001
Storage nearly full. Storage is almost full (the system states the threshold).
| Code | HEART storage.nearly-full; inside a message "code": "storage.nearly-full" |
|---|---|
| H-number | H-04001: area 04, code 001 |
| Area | storage: Disk, memory cards, databases |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Cameras, recorders, servers, gateways, anything that stores data |
Likely causes
- Pictures, video or recordings not yet collected, such as on a camera's memory card.
- Log files that are never rotated.
- A database growing without clean-up.
- Updates or temporary files left behind.
How to fix or prevent it
- Collect or move the data you want to keep.
- Delete old logs, temporary files and old updates.
- Set log rotation and retention, so old data is removed by itself.
- Fit a larger card or disk.
What the HEART does by itself
It raises a warning at the threshold the product states, such as 10 % free. A Playbook may rotate old logs or run compact_storage, within its guards. It resolves when space is back above the threshold.
When to call service
Rarely. Only if space fills again within hours, which points to a fault that writes too much.
Related codes
storage.fullH-04002: Storage fullstorage.write-failedH-04003: Write faileddata.backup-failedH-10004: Backup failed
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)