-
Notifications
You must be signed in to change notification settings - Fork 30
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
Is this bad? Compression signature was 4, expected 3.
#13
Comments
I have the same error but on a different file. It didn't finish. |
I pretty much gave up after I copied manually - and I guess the metadata didn't copy with it, and it didn't actually boot. I'd like to be able to copy to a subvolume / subvolume image to import though, which is what I was trying to do eventually in the first place. |
You should use btrfs send and receive instead of an image. There are ways to do it over a network if you have to. winbtrfs's readme says it supports send and receive. |
I couldn't even get to that point is my point. I'd have done something similar if I'd actually ended up with a btrfs volume. |
I have a similar issue, except mine says 2, expected 3. |
same, minen says 7 instead of 3 |
It seems the python implementation does not check the signature, and only writes the value 3 for when data was not compressed. Should there even be a check? |
|
Hey, is there any fix to this or a workaround? Tried compressing because there wasn't enough storage for metadata (thought maybe 10gb was enough, guess not), but it crashes a Sig 1 expected 3. |
I got:
\Windows\System32\MRT.exe: Compression signature was 4, expected 3.
with an exit code of 1. I'm not sure if it finished.Is that bad?
Ta
The text was updated successfully, but these errors were encountered: