flexblock update
Synopsis
Section titled “Synopsis”flexblock update <DEVICE> [flags]Description
Section titled “Description”update changes a setting recorded on the volume: the device size, the compression algorithm, or S3 server-side encryption. It writes the change to the volume superblock in object storage first, then locally.
The device must be cleanly stopped and not serving. --allow-unclean covers only an unclean stop, never a live daemon. The exception is a size change: with --device-size and a running daemon, update grows the live device through the daemon’s control socket, on Linux 6.16 or newer.
Growing is one-way and bounded by the grant’s licensed size; afterward grow the filesystem too (xfs_growfs or resize2fs). --device-size needs a current grant; other changes do not.
With no change, update repairs a volume superblock that object storage reports missing or stale, except one that records a larger size, which needs --device-size at that size.
| Flag | Default | Description |
|---|---|---|
--allow-unclean | — | Proceed on a device that was not cleanly stopped. |
--compression <none|lz4|zstd|snappy> | — | New algorithm for later writes; existing objects keep their own. |
--device-size <SIZE|+DELTA|max> | — | Grow to a size, by a delta, or to max (the licensed size). Needs a current grant, and Linux 6.16 while the daemon serves. |
--dry-run | — | Print the old and new values and exit. |
--s3-no-sse | — | S3 only: stop requesting server-side encryption for later writes. |
--s3-sse | — | S3 only: request server-side encryption for later writes. |
--s3-sse and --s3-no-sse cannot be combined.
Examples
Section titled “Examples”Grow a serving volume, then grow its filesystem:
sudo flexblock update /dev/nvme1n1p1 --device-size +1Tsudo xfs_growfs /mnt/analyticsGrow to the full licensed size:
sudo flexblock update /dev/nvme1n1p1 --device-size maxWith the daemon stopped, change compression for later writes:
sudo flexblock update /dev/nvme1n1p1 --compression lz4