-
Notifications
You must be signed in to change notification settings - Fork 56
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
Maybe DestroySnapshot should not exist. #4
Comments
This consideration makes it seem more likely that CreateSnapshot should be a pool method, see #2. |
Request for removing DestroySnapshot: #3. |
Merged. |
mulkieran
referenced
this issue
in mulkieran/stratisd
May 18, 2017
It looks like our output parsing is working ok, since list_devices and list_versions both work, but how we're formatting the input buffer is still wrong because we're failing to set name correctly for table_status, see #4. Signed-off-by: Andy Grover <agrover@redhat.com>
mulkieran
referenced
this issue
in mulkieran/stratisd
May 18, 2017
We were getting panics because targ.next may be nonzero for the last target entry. target_count is what to go by. Don't use targ.next to get the next slice in the last loop iteration. Resolves #4 Signed-off-by: Andy Grover <agrover@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once the snapshot is created, it is a volume like any other. It should be destroyed using the method for removing any volume, DestroyVolumes.
The text was updated successfully, but these errors were encountered: