---
metadata:
  - name: generator
    content: Diplodoc Platform v5.52.0
alternate:
  - https://ydb.tech/docs/en/troubleshooting/performance/hardware/disk-space.md?version=v26.1
  - https://ydb.tech/docs/ru/troubleshooting/performance/hardware/disk-space.md?version=v26.1
  - href: en/troubleshooting/performance/hardware/disk-space.md
    type: text/markdown
    title: Markdown version
  - href: ../../../llms.txt
    type: text/markdown
    title: llms.txt
sourcePath: en/core/troubleshooting/performance/hardware/disk-space.md
---
> **Documentation Index:** Fetch the complete configuration index at https://ydb.tech/docs/en/llms.txt

# Disk space

A lack of available disk space can prevent the database from storing new data, resulting in the database becoming read-only. This can also cause slowdowns as the system tries to reclaim disk space by compacting existing data more aggressively.

## Diagnostics

1. See if the **[DB overview > Storage](https://ydb.tech/docs/en/reference/observability/metrics/grafana-dashboards.md?version=v26.1#dboverview)** charts in Grafana show any spikes.

1. In [Embedded UI](https://ydb.tech/docs/en/reference/embedded-ui/index.md?version=v26.1), on the **Storage** tab, analyze the list of available storage groups and nodes and their disk usage.

    {% note tip %}

    Use the **Out of Space** filter to list only the storage groups with full disks.

    {% endnote %}

    ![](_assets/storage-groups-disk-space.png)

{% note info %}

It is also recommended to use the [Healthcheck API](https://ydb.tech/docs/en/reference/ydb-sdk/health-check-api.md?version=v26.1) to get this information.

{% endnote %}

## Recommendations

Add more [storage groups](https://ydb.tech/docs/en/concepts/glossary.md?version=v26.1#storage-group) to the database.

If the cluster doesn't have spare storage groups, configure them first. Add additional [storage nodes](https://ydb.tech/docs/en/concepts/glossary.md?version=v26.1#storage-node), if necessary.