Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting sequential cut off policy/threshold returns 0 status even for non existing cores/caches #116

Closed
KamilLepek opened this issue Sep 25, 2019 · 0 comments · Fixed by #125
Assignees

Comments

@KamilLepek
Copy link
Contributor

KamilLepek commented Sep 25, 2019

For example for the following cache configuration:

type    id   disk             status    write policy   device
cache   1    /dev/nvme0n1p1   Running   wt             -

the following commands return exit code 0

casadm -X -n seq-cutoff -i 1 -j 50 -t 28
casadm -X -n seq-cutoff -i 1 -j 50 -p full
casadm -X -n seq-cutoff -i 5555 -j 50 -p full
casadm -X -n seq-cutoff -i 5555 -p full

When I add core this error still occurs (for different core ids than the one I added). As stated this behaviour occurs when setting per cache or per core.

@KamilLepek KamilLepek changed the title Setting sequential cut off policy/threshold returns 0 status even for non existing cores. Setting sequential cut off policy/threshold returns 0 status even for non existing cores/caches Sep 25, 2019
@robertbaldyga robertbaldyga self-assigned this Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants