aaedfb35dd
Current startup procedure works on an assumption that we will deal with asynchronously appearing devices in asynchronous way (udev rules) and synchronous events in the system (systemd units) won't interfere. If we would break anything (mounts) we would just take those units and restart them. This tactic was working as long as resetting systemd units took reasonable time. As hackish as it sounds it worked in all systems that the software has been validated on. Unfortunately it stopped working because of *.mount units taking MUCH longer time to restart even on mainstream OSes, so it's time to change. This change implements open-cas systemd service which will wait synchronously with systemd bootup process for all required Open CAS devices to start. If they don't we fail the boot process just as failing mounts would. We also make sure that this process takes place before any mounts (aside from root FS and other critical FS's) are even attempted. Now opencas-mount-utility can be discarded. To override this behaviour on per-core basis you can specify lazy_startup=true option in opencas.conf. Signed-off-by: Jan Musial <jan.musial@intel.com>
79 lines
1.3 KiB
Groff
79 lines
1.3 KiB
Groff
.TH casctl.8 __CAS_DATE__ v__CAS_VERSION__
|
|
.SH NAME
|
|
casctl \- whole-configuration-manager for Open CAS.
|
|
|
|
|
|
.SH SYNOPSIS
|
|
|
|
\fBcasctl\fR <command> [options...]
|
|
|
|
.SH COPYRIGHT
|
|
Copyright(c) 2012-2019 by the Intel Corporation.
|
|
|
|
.SH COMMANDS
|
|
.TP
|
|
.B start
|
|
Start all cache instances.
|
|
|
|
.TP
|
|
.B stop
|
|
Stop all cache instances.
|
|
|
|
.TP
|
|
.B init
|
|
Initial configuration of caches and core devices.
|
|
|
|
.TP
|
|
.B settle
|
|
Wait for all core devices to be added to respective caches.
|
|
|
|
.br
|
|
.B CAUTION
|
|
.br
|
|
May be used if there is no metadata on cache device or if metatata exists, then only if it's all clean.
|
|
|
|
.TP
|
|
.B -h, --help
|
|
|
|
|
|
.SH OPTIONS
|
|
|
|
.TP
|
|
.SH Command start does not accept any options.
|
|
|
|
.TP
|
|
.SH Options that are valid with stop are:
|
|
|
|
.TP
|
|
.B --flush
|
|
Flush data before stopping.
|
|
|
|
.TP
|
|
.SH Options that are valid with init are:
|
|
|
|
.TP
|
|
.B --force
|
|
Force cache start even if cache device contains partitions or metadata from previously running cache instances.
|
|
|
|
.TP
|
|
.SH Options that are valid with settle are:
|
|
|
|
.TP
|
|
.B --timeout
|
|
How long will command block waiting for devices to start before timing out [s].
|
|
|
|
.TP
|
|
.B --interval
|
|
How often will command poll for status change [s].
|
|
|
|
.TP
|
|
.SH Command --help (-h) does not accept any options.
|
|
|
|
.SH REPORTING BUGS
|
|
Patches and issues may be submitted to the official repository at
|
|
\fBhttps://open-cas.github.io\fR
|
|
|
|
.SH SEE ALSO
|
|
.TP
|
|
casadm(8), opencas.conf(5)
|