docs/kb/disk-utilization.rst
Topic: nodetool snapshot and disk space
Learn: understand how nodetool snapshot utilizes disk space
Audience: ScyllaDB administrators
When you create a snapshot using :doc:nodetool snapshot </operating-scylla/nodetool-commands/snapshot> command, ScyllaDB is not going to copy existing SStables to the snapshot directory as one could have expected. Instead, it is going to create hard links to them. While this may seem trivial, what should be noted is the following:
In this example, a snapshot was created. As you can see, its True size value is 0 bytes:
.. code-block:: none
nodetool listsnapshots Snapshot Details:
Snapshot name Keyspace name Column family name True size Size on disk 1574708464997 ks3 standard1 0 bytes 2.23 GB
Total TrueDiskSpaceUsed: 0 bytes
After time, you can see its True size is the same as the space it utilizes on disk:
.. code-block:: none
nodetool compact ks3 nodetool listsnapshots
Snapshot Details: Snapshot name Keyspace name Column family name True size Size on disk 1574708464997 ks3 standard1 2.23 GB 2.23 GB
Total TrueDiskSpaceUsed: 2.23 GiB
.. note:: A major compaction makes the true snapshot size jump to the data size immediately as the old SSTables are being deleted.
Nodetool Snapshoot </operating-scylla/nodetool-commands/snapshot>