You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
For example for the following cache configuration:
the following commands return exit code 0
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.
The text was updated successfully, but these errors were encountered: