Creation

Volume creation happens on demand for ephemeral volumes. In contrast Persistent volumes need to be created explicitly via the CLI, web UI, or API prior to first use starting with V4.

Your cluster administrator configures storage provisioners that determine the storage backend and access policies for your organization. Your workflow creates and/or uses one or more storage volumes which are directories or resources managed by a provisioner.

A volume name must follow these rules:

• Length: Between 1 and 255 characters
• No path separators: Cannot contain / or \
• No path traversal: Cannot be . and cannot contain ..
• No null bytes: Cannot contain a null byte (\0)

Any other characters — letters in any case, digits, spaces, dots, underscores, hyphens, and other punctuation — are allowed.

Valid examples:

my-dataset
Research_Data-2024
project 1
results.v2

Invalid examples:

my/dataset          # Contains a path separator
data\set            # Contains a path separator
..                  # Path traversal
my..dataset         # Contains path traversal (..)

These rules prevent volume names from escaping the storage boundary. The same rules are enforced by the CLI, web UI, and API.

If you encounter a validation error when creating a volume, check that your volume name:

1. Is not empty and is no longer than 255 characters
2. Does not contain a path separator (/ or \)
3. Is not . and does not contain ..
4. Does not contain a null byte

A volume’s root directory has Unix-style permissions — a file mode — that control who can read, write, and traverse (enter) it. You choose the mode when you create the volume, and the mode cannot be changed afterward.

In the web UI, the New Volume dialog has a Permissions field listing modes in both octal and symbolic notation, for example 0750 (rwxr-x---). Every interface defaults to 0750: the volume owner has full access, group members can read and traverse, and other users have no access.

The web UI offers the eight modes listed above. The CLI accepts any POSIX mode up to 7777, including the setuid, setgid, and sticky bits.

The API field is a plain unsigned integer, not octal text, and the service does not enforce the CLI’s upper bound. Convert the mode before sending it: 0750 is 488, and sending 750 instead records mode 01356 – a sticky, world-writable volume.

The equivalent on the CLI is the --permissions flag, which also accepts symbolic notation:

$ fuzzball volume create nfs my-dataset --size 10GB --permissions 0750
$ fuzzball volume create nfs my-dataset --size 10GB --permissions u=rwx,g=rx

To see the mode on a volume created with an explicit mode, select it in the web UI volume list and read the Permissions row in the detail panel. Volumes created before Fuzzball recorded volume modes have no stored mode, so the detail panel omits the row for them entirely; the storage driver applies its own default when such a volume is mounted. The CLI reports the mode as a decimal number rather than octal, so fuzzball volume info PROVISIONER_NAME VOLUME_NAME prints permissions: 488 for a volume created with 0750.

Group ownership of the volume directory is derived from your account rather than chosen at creation time. Administrators can see Volume permissions for how the storage driver applies ownership and mode.