flexblock wipe
Synopsis
Section titled “Synopsis”flexblock wipe [DEVICE] [flags]Description
Section titled “Description”wipe destroys a volume: every object under the prefix, the volume superblock, the ownership marker, and the local cache. The volume is always the one the grant names.
The device is optional. Omit it to destroy a volume no host is attached to, confirming with --allow-unverified. A device that holds no flexBlock cache is refused, never zeroed. wipe works on an unclean device deliberately, since a clean stop would mean uploading data about to be deleted.
wipe always prompts unless -y is given, and refuses with no terminal (exit code 2). It refuses while a daemon is serving, and when another host owns the volume. If any delete fails it exits non-zero; run it again to resume. It does not need a current grant.
After deleting, wipe may wait up to 290 seconds (the 285-second take-over fence plus a short margin) for uploads that could still land, and deletes whatever did, so a volume created at the same prefix later never inherits them.
| Flag | Default | Description |
|---|---|---|
--allow-foreign-ownership | — | Wipe although another host owns the volume. |
--allow-unverified | — | Wipe with no device to check ownership against. Required when no device is given; not allowed with one. |
--dry-run | — | Print what would be deleted and exit. |
-y, --yes | — | Skip the confirmation prompt. Does not override any safety refusal. |
Examples
Section titled “Examples”Preview, then wipe a volume through its cache device:
sudo flexblock wipe /dev/nvme1n1p1 --dry-runsudo flexblock wipe /dev/nvme1n1p1Wipe a volume that no host is attached to, without a prompt:
sudo flexblock wipe --allow-unverified -y