github/open-cas-linux
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #542 from imjfckm/update-conf-comments

Browse Source 
Update sample opencas.conf to include lazy_startup option
This commit is contained in:
Robert Baldyga 2020-10-05 17:25:07 +02:00 committed by GitHub
commit bc4450b478
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
utils/opencas.conf
View File

@ -20,10 +20,20 @@ version=19.3.0
## Core devices configuration ## Core devices configuration
[cores] [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 ## Uncomment and edit the below line for core configuration
#1 1 /dev/disk/by-id/wwn-0x123456789abcdef0 #1 1 /dev/disk/by-id/wwn-0x123456789abcdef0
## To specify use of the IO Classification file, place content of the following line in the ## To specify use of the IO Classification file, place content of the following line in the
## Caches configuration section under Extra fields (optional) ## Caches configuration section under Extra fields (optional)
## ioclass_file=/etc/opencas/ioclass-config.csv ## 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)