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

Issue with reusing same disk image with newer version #124

Closed
amarts opened this issue Jan 13, 2020 · 2 comments
Closed

Issue with reusing same disk image with newer version #124

amarts opened this issue Jan 13, 2020 · 2 comments

Comments

@amarts
Copy link
Member

amarts commented Jan 13, 2020

I have used a device which was used with a previous kadalu install (both used for testing), and when I try to use it again get below error:

[2020-01-13 09:36:06.149709] E [MSGID: 113063] [posix-common.c:663:posix_init] 0-storage-pool-1-posix: mismatching volume-id (1e67ddba-35e8-11ea-945f-0242ac110004) received. already is a part of volume 06be7d4a-31ec-11ea-9ed3-0242ac110004 
[2020-01-13 09:36:06.149789] E [MSGID: 101019] [xlator.c:626:xlator_init] 0-storage-pool-1-posix: Initialization of volume 'storage-pool-1-posix' failed, review your volfile again
[2020-01-13 09:36:06.149801] E [MSGID: 101066] [graph.c:361:glusterfs_graph_init] 0-storage-pool-1-posix: initializing translator failed

We should have an understanding how to use the data which has different glusterfs volume before. This may be expected behavior, but took some time for me to resolve. At least it would be great to add a check like these in kubectl_kadalu scripts so, users using that would get best experience.

@amarts
Copy link
Member Author

amarts commented Jan 22, 2020

Thinking more about it, this may not be a good idea. If it was used by a different volume, it may mean there may be a pod using it. This may cause problems.

Closing.

@amarts amarts closed this as completed Jan 22, 2020
@c-seeger
Copy link

for reference if others come accross this can be fixed see Recreation of storage-pool with existing Volume ID by adding volume_id from the error message to the creation yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants