--log-level <LEVEL>
: Set log level (trace, debug, info, warn, error) [default: info]--version
: Print version information--help
: Show help message<DISK_ID>
: Disk identifier (e.g., 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]--disable-xattrs
: Disable 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]--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]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.<MOUNTPOINT>
: Directory where the disk is mounted--force, -f
: Force unmount operation, skipping fsyncing outstanding writes and releasing any ownership claims [default: false]<PATH>
: Path to the file to check out--force, -f
: Force checkout, revoking an existing delegation from another client [default: false]<PATH>
: Path to the file to check in<MOUNTPOINT>
.
<MOUNTPOINT>
: Directory where the disk is mounted<MOUNTPOINT>
: Directory where the disk is mounted