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

Migrating from a larger to a smaller pvc fails with a generic error message. #244

Open
danielr1996 opened this issue Sep 22, 2023 · 1 comment

Comments

@danielr1996
Copy link

Is your feature request related to a problem? Please describe.
When trying to copy from a larger pvc to a smaller pvc the migration fails with the following very generic error message

Migration failed with this strategy, will try with the remaining strategies
Error: migration failed: all strategies failed for this migration
❌  Error: migration failed: all strategies failed for this migration

Describe the solution you'd like
I would like pv-migrate to check the target and source size and don't even start the migration when there is less space in the target then the source. While I understand that comparing actual sizes could be difficult, it should at least be possible to compare the requested sizes and provide a flag --ignore-sizes if you know your data will fit because the pvcs are 100G and 50G each, but you know the actual size is just 10G.

Describe alternatives you've considered
It would be fine to display a more descriptive error after failing, maybe the one the underlying command (rsync) produced, instead of the generic one. This might be easier the implement, especially if you migrate e.g. 100G into a 99G pvc and find out that you dont't have enough space after copying for hours.

@utkuozdemir
Copy link
Owner

I like the idea of checking sizes and failing explicitly unless having --ignore-sizes set.
I also like the idea of showing the actual rsync error message on a failed migration.

I'll try to look into it some time.

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