S3-compatible storage per TB · no API fees · encrypt before upload · pay in BTC, USDT, USDC, ETH, SOL, LTC, XMR
Get storage

Help · checked 17 November 2026

What do I do when my PrivateS3 bucket is full?

Last updated: · 4 min read

Quick answer

Why does my PrivateS3 bucket refuse uploads?

Because the bucket reached its plan size. On PrivateS3 the plan is a hard quota: an upload that would pass it fails with a QuotaExceeded error, and nothing is billed on top. Free space with restic forget --prune or by expiring old versions, or move to a bigger plan, such as Bay 5 at $27 a month.

In brief
  • The error: QuotaExceeded on upload; reads, listings and deletes keep working.
  • No surprise bill: PrivateS3 never charges for going over; it refuses the upload.
  • Hidden users of space: old object versions count toward the quota; unfinished multipart uploads can hold space too.
  • Two ways out: delete or prune, or buy a bigger plan; the bucket keeps its data and keys.

What fills a bucket, and how do you free it?

Common causes of a full PrivateS3 bucket and the fix for each
CauseHow to spot itFix
Too many restic or Kopia snapshotsrestic snapshots lists months of historyrestic forget with a keep policy, then prune
Old object versionsVersioning is on; list-object-versions shows many noncurrent versionsA lifecycle rule with NoncurrentVersionExpiration
Unfinished multipart uploadsInterrupted large uploadsA lifecycle rule with AbortIncompleteMultipartUpload
Data simply grewRepository size near the plan size after pruningMove to a bigger plan

What does a full bucket do to my backups?

New uploads fail, but nothing already stored is touched. The plan size is a hard quota: an upload that would pass it is refused with a QuotaExceeded error, nothing is billed on top. A backup tool reports the failed upload and stops. Reads, listings and deletes still work, so you can restore and clean up at once.

This is the other side of a fixed price. A pay-per-GB seller would bill the extra; PrivateS3 stops at the size you paid for. According to PrivateS3's survey of 17 November 2026, Backblaze B2 and Wasabi both bill whatever is stored, with no ceiling. Plans and sizes are on the pricing page.

How do I free space with restic?

Forget old snapshots, then prune the data only they used. restic's documentation explains the two steps: forget removes snapshots, prune removes the data left behind, and forget --prune runs both when snapshots were removed.

Prune writes repacked files before it deletes old ones, so it needs some free room. When the bucket is completely full, restic documents prune --max-repack-size 0 as the option that uses the least scratch space. If even restic's small lock file cannot be written, delete a few objects outside the repository first, or move to a bigger plan. The restic page covers retention policies.

restic: keep 7 daily and 4 weekly snapshots, then prune
restic -r s3:https://s3.privates3.com/BUCKET forget --keep-daily 7 --keep-weekly 4 --prune
# if there is almost no free room left:
restic -r s3:https://s3.privates3.com/BUCKET prune --max-repack-size 0

Why is my bucket full when my files are smaller?

Usually because of old versions. S3 versioning can be turned on per bucket from any S3 client; old versions count toward the quota. Every overwrite or delete keeps the old copy until it is removed. A lifecycle rule can expire noncurrent versions after a set number of days, and abort multipart uploads left unfinished.

Lifecycle rules are part of the supported API, set with the AWS CLI. The block uses example values; the endpoint is shown with the keys in the client area. The versioning guide explains when versioning is worth its space.

lifecycle.json, then the AWS CLI command that applies it
# lifecycle.json
{
  "Rules": [
    {
      "ID": "expire-old-versions",
      "Status": "Enabled",
      "Filter": { "Prefix": "" },
      "NoncurrentVersionExpiration": { "NoncurrentDays": 30 },
      "AbortIncompleteMultipartUpload": { "DaysAfterInitiation": 7 }
    }
  ]
}

# apply it:
aws s3api put-bucket-lifecycle-configuration --bucket BUCKET --lifecycle-configuration file://lifecycle.json --endpoint-url https://s3.privates3.com

How do I move to a bigger plan?

Buy the bigger plan from the balance; the bucket keeps its data and keys. A bigger plan can be bought at any time; the bucket keeps its data and keys and the quota grows when the new plan starts. Monthly plans go from 1 to 100 TB; 12-month plans cover 1, 5 and 10 TB.

If the new plan starts later, clean up meanwhile so tonight's backup still runs. Keep an eye on the end date too: the plan end guide explains the read-only period.

Quota questions

Will PrivateS3 bill me for going over?

No. The plan size is a hard quota: an upload that would pass it is refused with a QuotaExceeded error, nothing is billed on top.

Do deletes work when the bucket is full?

Yes. Reads, listings and deletes are not limited by the quota.

Do old versions count toward the quota?

Yes. S3 versioning can be turned on per bucket from any S3 client; old versions count toward the quota.

Does forget alone free space?

No. forget removes snapshots; prune removes the data. Use forget --prune, or run prune after.

Can I get more room without a new plan?

No. Quotas follow the plan sizes on the price list, so more room means a bigger plan.

Verdict
  • A full bucket refuses uploads and bills nothing extra: clean up with forget --prune or a lifecycle rule.
  • If the data really grew, buy the next plan size; data and keys stay as they are.
Sources (2)
  1. restic: removing backup snapshots (forget and prune) — restic (read 2026-11-17)
  2. AWS CLI put-bucket-lifecycle-configuration docs.aws.amazon.com/cli/latest/reference/s3api/put-bucket-lifecycle-configuration.html — Amazon Web Services (read 2026-11-17)

Need more room? 5 TB for 12 months: $133.87

Or Bay 10 at $54 a month. Data and keys stay.

$5.40/TB-month · no KYC

Get storage