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

Jump to bottom

xdelta3 fails to decode on block device #149

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 4 comments
Closed

xdelta3 fails to decode on block device #149

GoogleCodeExporter opened this issue Mar 24, 2015 · 4 comments
Labels
auto-migrated

Comments

@GoogleCodeExporter
Copy link 

I'm trying to use xdelta3 to bring a remote block device into sync with a local 
one. I'm able to easily generate a xdelta3 patch file using the command:

xdelta3 -e -B 33554432 -v -9 -I 0 -s /dev/loop5p2 /dev/loop4p2 patch.xd3

However, when I try to decode on the remote system using the following command:

xdelta3 -v -d -B 33554432 -s /dev/sda2 patch.xd3 /dev/sda3

I get the following error:

xdelta3: non-seekable source in decode: XD3_INTERNAL

As I understand it, this is caused by not having a large enough buffer. 
However, my -B argument is equal to the creator of the patch. In fact, I can 
double that size and it still won't work.

Original issue reported on code.google.com by da...@fivepmtechnology.com on 17 Oct 2012 at 3:09
@GoogleCodeExporter
Copy link
Author 

This happens to me, too, when decoding to a plain file but using a fifo as 
source. It stops with the same error after outputting 9395240960 bytes. When 
replacing the fifo source by a plain file source the same vcdiff decodes 
properly (approx. 40 GB).

Original comment by Arno1...@gmail.com on 19 Oct 2012 at 4:35

@GoogleCodeExporter
Copy link
Author 

Thanks.  Someone sent me a script that alleges to reproduce this for me, so I 
should be able to figure it out.

Original comment by josh.mac...@gmail.com on 5 Nov 2012 at 7:13

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author 

I believe this is fixed in SVN 375.
Thanks.

Original comment by josh.mac...@gmail.com on 12 Nov 2012 at 8:39

@GoogleCodeExporter
Copy link
Author 

I'm marking this closed with the release of 3.0.5. Let me know if anything 
doesn't work as expected. Thanks. Josh

Original comment by josh.mac...@gmail.com on 13 Nov 2012 at 6:20

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter