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

Invalid and duplicated info about detached caches #1622

Open
Kamoppl opened this issue Mar 13, 2025 · 0 comments · May be fixed by #1626
Open

Invalid and duplicated info about detached caches #1622

Kamoppl opened this issue Mar 13, 2025 · 0 comments · May be fixed by #1626
Assignees
Labels
bug Something isn't working v25.03

Comments

@Kamoppl
Copy link

Kamoppl commented Mar 13, 2025

Description

Running list caches cmd while cache is detached, prints mismatch info.
1 Warning is printed per each detached cache.
2 The warning may be misunderstood

Expected Behavior

Propare message is print

Actual Behavior

Warning: Cannot resolve path to cache. By-id path will be shown for that cache.
(Cache is in detached state so there is no path to disk)

Steps to Reproduce

  1. Start caches
  2. Detach caches (at least 2)
  3. List caches

Context

Possible Fix

Logs

Image

Configuration files

Your Environment

  • OpenCAS version (commit hash or tag): master - 2f827e2
  • Operating System:
  • Kernel version:
  • Cache device type (NAND/Optane/other):
  • Core device type (HDD/SSD/other):
  • Cache configuration:
    • Cache mode: (default: wt)
    • Cache line size: (default: 4)
    • Promotion policy: (default: always)
    • Cleaning policy: (default: alru)
    • Sequential cutoff policy: (default: full)
  • Other (e.g. lsblk, casadm -P, casadm -L)
@Kamoppl Kamoppl added the bug Something isn't working label Mar 13, 2025
@mmichal10 mmichal10 linked a pull request Mar 18, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v25.03
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants