-
Notifications
You must be signed in to change notification settings - Fork 61
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
APPLY FAILED. #39
Comments
I'm not sure what's going on here -- my initial impression is that this output appears to be missing the remote-side output. Assuming you're using the latest released version of lvmsync (3.2.0) on the sender side, all output from the remote should be displayed prefixed by So, yeah, mystery. It may be that you've found a corner-case I hadn't considered, that's failing the receiver silently, or perhaps gnomes are eating your errors. A couple of things to try, to rule out fundamental problems:
That makes sure that |
Maybe is problem with path? lvmsync execute remote commands from bash? |
On the receiver side, lvmsync does very little -- it opens the destination file and writes chunks where its told. There's not a lot else that it does. I'll work on releasing a new version of lvmsync with improved debugging capabilities, which should show up what's going on. Look for it by the end of the weekend. |
OK, version 3.3.0 is out, and now supports |
|
Maybe this is problem?
|
Ok, i thinks i found error:
You must fix --verbose and --debug ;) |
If anyone else stumbles into this. Make sure the directory you want to store the snapback in exists on the server/remote. If it does not exist it will give a: |
The text was updated successfully, but these errors were encountered: