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

Invalid option 't' while resuming transfer #71

Open
adrianmarcu18 opened this issue Sep 25, 2020 · 3 comments
Open

Invalid option 't' while resuming transfer #71

adrianmarcu18 opened this issue Sep 25, 2020 · 3 comments

Comments

@adrianmarcu18
Copy link

adrianmarcu18 commented Sep 25, 2020

Hello. Trying to use the new functionalities of retry and resume, but having some issues while resuming. The output looks something like this (replaced the actual destination and dataset name):

Sep 25 09:33:34 INFO: Found resume token. Resuming last transfer of sshdestination:dataset (~0.0B)...
  invalid option 't'
usage:
        send [-DnPpRvLe] [-[iI] snapshot] <snapshot>
        send [-Le] [-i snapshot|bookmark] <filesystem|volume|snapshot>

For the property list, run: zfs set|get

For the delegated permission list, run: zfs allow|unallow
Sep 25 09:33:34 ERROR: Error while sending to sshdestination:dataset: cannot receive: failed to read from stream...

Later edit: Trying to remove the resume option from the config and run again the transfer will fail with the same error. So even though the resume config option is removed, it will still try to resume the last failed transfer and I am stuck in a loop.

@adrianmarcu18
Copy link
Author

Ok, so discovered that I was using different zfs versions on the source and destination. Source doesn't have the option of resume, but destination has. I think there should be implemented a way to check if the current zfs version supports resuming, and if not, to ignore the settings from the pyznap config.

@yboetz
Copy link
Owner

yboetz commented Sep 25, 2020

Yes, you need a more recent version of ZFS to use resumable send. I might put in a more meaningful error message at some point.

@adrianmarcu18
Copy link
Author

adrianmarcu18 commented Sep 25, 2020

I think it should be added to the requirements list which is the supported zfs version. Or add an additional check for zfs resume functionality. Because if you end up using resume feature on an older zfs version, there is no way to solve it, than to destroy the destination dataset to be able to send again. So a lot of things can break.

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