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.

Sign up for GitHub

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

Jump to bottom

Clean core in inactive state could not be removed #222

Closed
katlapinka opened this issue Dec 11, 2019 · 0 comments · Fixed by #228
Closed

Clean core in inactive state could not be removed #222

katlapinka opened this issue Dec 11, 2019 · 0 comments · Fixed by #228
Assignees
@jfckm

Comments

@katlapinka
Copy link
Contributor

Steps to reproduce:

  1. Start cache in WB mode and add core
  2. Write some data to CAS device.
  3. Flush cache.
  4. Stop cache.
  5. Unplug core device from OS.
  6. Load cache and check that core is in inactive state.
  7. Remove core without force option.

Actual status:
Inactive core without dirty data could not be removed without "force" option

Expected:
It should be possible to remove clean inactive core without "force" option
@jfckm jfckm self-assigned this Dec 11, 2019
@jfckm jfckm mentioned this issue Dec 11, 2019
Merged
vzhereb9 pushed a commit to vzhereb9/open-cas-linux that referenced this issue Jun 14, 2021
Merge pull request Open-CAS#222 from robertbaldyga/name-based-registr…
bc20845 
…ation

Name based cache/core management
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jfckm jfckm

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix removing clean inactive core jfckm/open-cas-linux
2 participants
@jfckm @katlapinka