-
Notifications
You must be signed in to change notification settings - Fork 28
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
add new command to delete stale omap objects #251
Comments
Can you describe the scenario more? Will users commonly hit this issue, or not so common if they are following recommended practices? |
There can be cases where the subvolume was deleted but the omaps were not clean, which will result in having a stale omap. Currently, in the deletion of omap we are deleting the omap object and key only for the stale subvolumes to avoid these kinds of scenarios. |
Sounds good, so we don't expect it to be common, but it may be possible. |
@yati1998 this is done right? |
No, it is not done, it will be different from the subvolume cleanup. |
Add a new omap command to list all the stale omap objects and delete them.
Check this for more details:
#237 (comment)
The text was updated successfully, but these errors were encountered: