From bc29b6987a5656345597e87f350c6729fe7cbf2b Mon Sep 17 00:00:00 2001 From: Jan Musial Date: Thu, 1 Oct 2020 14:20:09 +0200 Subject: [PATCH] Update sample opencas.conf to include lazy_startup option Signed-off-by: Jan Musial --- utils/opencas.conf | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/utils/opencas.conf b/utils/opencas.conf index f1de783..161266a 100644 --- a/utils/opencas.conf +++ b/utils/opencas.conf @@ -20,10 +20,20 @@ version=19.3.0 ## Core devices configuration [cores] -## Cache ID Core ID Core device +## Cache ID Core ID Core device Extra fields (optional) ## Uncomment and edit the below line for core configuration #1 1 /dev/disk/by-id/wwn-0x123456789abcdef0 ## To specify use of the IO Classification file, place content of the following line in the ## Caches configuration section under Extra fields (optional) ## ioclass_file=/etc/opencas/ioclass-config.csv + +## If given cache/core pair is especially slow to start up, often doesn't come back +## up after reboot or you simply don't care if it does and don't want it to have +## an effect on your boot you can mark cores as lazy to prevent Open CAS from +## dropping boot to emergency shell because of this core failure. To do this +## put following line under in Extra fields (optional) section of core config: +## lazy_startup=true +## NOTE: This will cause open-cas.service to not wait for marked core while +## starting up - this option should be used with care to prevent races with +## other services for devices (e.g. mounts based on FS labels)