rustfs/rustfs · error · DiskError

volume is not empty

Error message

volume is not empty

What it means

Guard returned when deleting (or renaming away) a bucket directory that still contains entries. The S3 delete-bucket flow surfaces it as BucketNotEmpty: leftover objects, incomplete multipart uploads, or stray metadata files prevent removal. Callers must empty the bucket (including aborting in-progress multipart uploads) before retrying the delete.

Source

Thrown at crates/ecstore/src/disk/error.rs:98

    #[error("drive is part of root drive, will not be used")]
    DriveIsRoot,

    #[error("remote drive is faulty")]
    FaultyRemoteDisk,

    #[error("drive is faulty")]
    FaultyDisk,

    #[error("drive access denied")]
    DiskAccessDenied,

    #[error("file not found")]
    FileNotFound,

    #[error("file version not found")]
    FileVersionNotFound,

    #[error("too many open files, please increase 'ulimit -n'")]
    TooManyOpenFiles,

    #[error("file name too long")]
    FileNameTooLong,

    #[error("volume already exists")]
    VolumeExists,

    #[error("not of regular file type")]
    IsNotRegular,

    #[error("path not found")]
    PathNotFound,

    #[error("volume not found")]
    VolumeNotFound,

    #[error("volume is not empty")]

View on GitHub (pinned to 5dca076efe)

Solutions

1. Delete all objects and versions inside the volume before removing it
2. If the volume should be empty, inspect for orphaned files and clean them
3. Retry the delete after the contents are removed

When it happens

Trigger: Thrown at crates/ecstore/src/disk/error.rs:98 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of rustfs/rustfs@5dca076efe (2026-08-20). Data as JSON: /api/errors/55e4f91af50aca13. Report an issue: GitHub.