Why deleting a large folder may not return the space

Why storage keeps apparently deleted data

Deleting a file usually removes the ordinary reference to it. Many storage systems also maintain a recycle bin, older file versions or snapshots that still point to the same data. Those protections are useful precisely because they make it possible to undo mistakes. The price is that deletion in the file manager does not always mean immediate reclaimed capacity.

You could disable those protections and get space back more directly, but then a mistaken deletion or unwanted change becomes harder to reverse. A better choice is often to set sensible retention periods and plan enough free space for normal growth. If storage is already critically full, investigate what is retaining data before discarding old versions that might be your easiest route back.

This is especially relevant on a NAS serving several programs: each application may see its own folders while the storage system accounts for snapshots and hidden retention elsewhere. One free-space number rarely explains which of those jobs is holding the bytes.

The simple expectation

Imagine a NAS running low on free space. Its owner removes a large folder that seems unnecessary and expects the available-capacity number to jump.

The folder disappears, but the capacity number barely moves. This is the point where deleting additional files becomes tempting. The system looks full, the intended cleanup seems ineffective and the quickest visible action is to remove more.

That would have been the wrong response. Deletion from the ordinary file view is only one stage in a storage system that may also have recycle bins, snapshots, retained versions and background cleanup work.

Deleted does not always mean unreferenced

A file can disappear from the shared folder while its data remains referenced somewhere else. A recycle bin may keep it available for recovery. A snapshot may preserve the earlier state of the folder. A backup or synchronization tool may maintain another copy by design.

From the user's perspective, the file was deleted. From the storage system's perspective, at least one feature may still be doing exactly what it was asked to do: retain the ability to recover that file.

This is not the NAS stealing space through malice. It is a collision between two reasonable goals—recover deleted data and reclaim capacity immediately. The interface could occasionally explain the argument more clearly.

Before deleting more data, find out which feature is still retaining the first deletion.

Recycle bins are the first place to look

Synology shared folders can have recycle bins. When enabled, deleted files move into a hidden recovery area instead of being removed immediately. That can rescue an accidental deletion, but it also means the space remains occupied until the recycle bin is emptied or cleaned by a schedule.

The important detail is scope. Emptying the computer's desktop recycle bin does not necessarily empty the NAS recycle bin. The shared folder has its own retention behaviour managed by the NAS.

Before emptying anything, confirm that the retained data is genuinely no longer needed. A cleanup carried out under capacity pressure is exactly when a safety feature earns its keep, even if it is also the reason the capacity number has not changed yet.

Snapshots preserve earlier versions

A snapshot records the state of supported storage at a point in time. It can make recovery from deletion or unwanted change much faster because the system retains the earlier data blocks needed to represent that state.

That means deleting a large file from the current view may not release all of its space while snapshots still refer to the older state. The exact amount depends on what changed and how the storage system manages those blocks.

Snapshots are valuable, so the answer is not to disable them reflexively. The answer is to review the schedule and retention policy. Keeping more history than the recovery need justifies turns a safety feature into a slow capacity leak wearing respectable clothes.

Space may return gradually

Even after the relevant retained copies are removed, the free-space number may not update instantly. Background cleanup, snapshot removal and storage accounting can take time, especially after a large change.

If the available space begins increasing gradually after cleanup, that trend can indicate that background work is proceeding. It is a reason to wait and verify before removing more data, not proof that every possible retention layer has been checked.

Watching the trend was more informative than refreshing the same screen every few seconds. Storage systems do not work faster because someone is staring at them, although they should consider the motivational opportunity.

Checks before deleting anything else

Start by confirming what was removed and whether the active folder size changed. Then review the shared-folder recycle bin, snapshot use, backup jobs and any package that keeps versions or replicas.

Also check whether the volume is genuinely full or whether one application is reporting a stale value. A scheduled storage report is better for identifying growth than relying on memory, especially when several services write to the same NAS.

• Confirm the intended folder or copy was removed.
• Check the NAS recycle bin for that shared folder.
• Review snapshot schedules and retained history.
• Check backup, synchronization and versioning tools.
• Allow background cleanup time after a large deletion.
• Watch the free-space trend before removing additional data.
• Document which folders are protected and why.

What to change afterward

Review any protection that duplicates data beyond what the recovery goal requires. Removing one unnecessary retained copy is different from deciding that shared data does not matter. Verify what can be recovered before changing a retention setting.

A scheduled storage report can make capacity easier to manage as a trend over weeks instead of an urgent red warning after the volume is already crowded.

The larger lesson was to understand each retention layer. Recycle bins, snapshots and backups solve different problems. Leaving all of them enabled indefinitely without a retention policy does not create infinite safety. It creates a very well-protected full disk.

A calmer capacity policy

Separate unique data, replaceable data and temporary data. Unique data deserves stronger protection. Replaceable data may justify less duplication. Temporary data should not quietly acquire permanent residence because nobody reviewed it.

The policy also includes leaving enough free space for routine operation and maintenance. A storage pool should not have to conduct every cleanup while standing on the last available floor tile.

When space drops unexpectedly, investigate growth and retention before launching a deletion campaign. Capacity problems are usually easier to solve when the first action preserves evidence rather than erasing it.