-
Notifications
You must be signed in to change notification settings - Fork 3
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
Cachebackend ASD removal failed #539
Comments
@matthiasdeblock do I get it correct that the use case was the following. We wanted to remove all ASD from a (cache) backend. This means no namespace should be on the backend otherwise you will hit the error as above as the policy can't be met.
@JeffreyDevloo Would openvstorage/framework#1656 not solve this issue. First re-configure the backend to not use that cache backend (which removes the namespaces) and next you should be able to remove all ASDs. |
No, this is to be resolved within the alba plugin. The plugin should determine whether or not the backend is storage or caching. If the backend is only used for caching, allow an unsafe safety |
Instead of the plugin checking allow a force remove (checkbox) of an ASD. The issue with the plugin checking is that in case this is an external backend, you don't have the context if it is use for cache or storage backend. |
@matthiasdeblock is there a workaround for this? |
As I had to remove all disks on the entire VM, the only possibility here was to stop the VM and then remove the disks. |
It might be a problem if you have to remove a single disk on a node for replacement. |
Just had the chance to retry this one and had the same issue while removing an SSD from a VM on Nuvolat. (@wimpers , it's not removing the entire backend but just an SSD). Strange thing I had now was that I first had these error messages: Logs:
After this, the disk got into failed state: While trying to remove it again, I've received the message again that there is potential data loss: Logs:
As this is a removal of the entire VM from the SSD storage, we can use the previous mentioned 'workaround'. As in shut down the VM and then remove the ASD's. |
The problem is, like @wimpers mentioned is that there is no way to detect in what context these ASDs are used... |
The removal of an ASD in the cachebackend failed with the current safety is not as expected.
As this is an ASD in the cachebackend we should be able to remove the disk without any issues.
The text was updated successfully, but these errors were encountered: