Archil disks are currently in preview. The CLI is subject to change.
Global Options
--log-level <LEVEL>: Set log level (trace, debug, info, warn, error) [default: info]--version: Print version information--help: Show help message
mount
Mount a disk to a local directory.<DISK_NAME>: An owner-qualified disk name (organization/disk-name|employee@email.com/disk-name) or disk ID (dsk-0123456789abcdef)<MOUNTPOINT>: Local directory to mount the disk
--region <REGION>: Region where the disk is located (e.g.,aws-us-east-1,gcp-us-central1)--auth-token <TOKEN>: Authentication token, if using
--max-cache-mb <SIZE>: Maximum cache size in MB [default: 1/4 of available RAM or 2048 MiB, whichever is smaller]--target-cache-mb <SIZE>: Target cache size in MB [default: 75% of the maximum cache size]
--shared: Enable sharing the disk with multiple clients by skipping the checkout of the root directory [default: false]--enable-xattrs: Enable extended attributes [default: false]--statistics: Enable statistics collection [default: false]--force, -f: Force claim ownership of the root directory, immediately revoking the delegations of any other clients [default: false]
Force claiming ownership of the root directory will immediately revoke the delegations of any other clients.
This can result in data loss for any outstanding writes from other clients to the disk.
--no-fork: Launch without forking [default: false]--log-dir <DIR>: Log to directory instead of journald--max-log-size-mb <SIZE>: Maximum log file size in MB [default: 100]
Always use
archil unmount to unmount your Archil disks, not the builtin umount command. Unlike umount,
the archil unmount command does not exit until all pending data is flushed to the backing disk. This is particularly
important on system shutdown, in which the Linux kernel will, by default, call umount on all devices and shutdown
without waiting for pending Archil writes to be synced.unmount
Unmount a disk.<MOUNTPOINT>: Directory where the disk is mounted
--force, -f: Force unmount operation, skipping fsyncing outstanding writes and releasing any ownership claims [default: false]
Force unmounting a disk will skip fsyncing outstanding writes. This will result in data loss for any outstanding writes.
version
Display version information.checkout
Request an ownership claim on a file or directory.<PATH>: Path to the file to check out
--force, -f: Force checkout, revoking an existing delegation from another client [default: false]
Force checkout will revoke ownership that other clients have on parents of the affected file or children of the affected file.
For more details, see the Shared Disks page.
Force checkout will revoke any existing delegation from another client.
This can result in data loss for any outstanding writes from other clients to the affected file.
checkin
Check in a file, releasing ownership of a file or directory.<PATH>: Path to the file to check in
delegations
View the list of ownership claims that this client has on the disk mounted at<MOUNTPOINT>.
<MOUNTPOINT>: Directory where the disk is mounted
status
Display status information for a mounted disk, for example, whether or not the disk has failed and is not accepting writes from this client.<MOUNTPOINT>: Directory where the disk is mounted
set-cache-expiry
Set the duration of time for which directories are kept cached locally instead of forcing a read from the server. This command configures the readdir cache expiry time for a specific directory.<PATH>: Path to the directory where cache expiry should be set
--readdir-expiry <SECONDS>: Cache expiry duration in seconds
- This command only applies to directories, not files
- Setting expiry to 0 seconds disables caching for the specified directory
- Cache settings help balance performance and data freshness
- Longer expiry times improve performance but may show stale directory contents
- The path must be on an Archil-mounted filesystem