-
Notifications
You must be signed in to change notification settings - Fork 245
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
btrfs initial full receive fails with "ERROR: failed to clone extents ..." #787
Comments
Further investigation indicates that the 2 source files share extents on both the original FS and the snap.
These extents overlap and different expected start values are reported. Is this a fault? ( Or a valid set of values that I dont understand?) Further investigation with all combinations of send options shows:
... or without --compressed-data.
Without --no-data, receive processes the sent stream correctly and shares the extents with --compressed-data ...
... and builds independant extents without.
This looks like a bug when receiving metadata of files with shared extents. It assumes it can clone the file when no data is present at the received end. |
With an empty receive directory ...
A send/receive runs ...
... and reports a failure.
A closer inspection shows that an attempt is made to clone the lib version of the target file from the lib64 version.
This is attempted even though the source files have distinct inodes and no parent subvols are involved.
My software versions ....
The text was updated successfully, but these errors were encountered: