import/export-tar: --tar-format=BORG: roundtrip ALL item metadata#6523
Conversation
ThomasWaldmann
force-pushed
the
pax-borg-item-master
branch
from
f6aa885 to
bb640cb
Compare
Codecov Report
@@ Coverage Diff @@
## master #6523 +/- ##
=======================================
Coverage 82.99% 83.00%
=======================================
Files 39 39
Lines 10531 10543 +12
Branches 2061 2063 +2
=======================================
+ Hits 8740 8751 +11
- Misses 1292 1294 +2
+ Partials 499 498 -1
Continue to review full report at Codecov.
|
borgbackup#5830 export-tar: just msgpack and b64encode all item metadata and put that into a BORG specific PAX header. this is *additional* to the standard tar metadata. import-tar: when detecting the BORG specific PAX header, just get all metadata from there (and ignore the standard tar metadata).
ThomasWaldmann
force-pushed
the
pax-borg-item-master
branch
from
bb640cb to
e8069a8
Compare
|
if noone objects or has review feedback, will merge this soon. |
|
Thanks for this addition! I see that this item is in the docs for 1.3 alpha. Is it planned to land in the 1.2 series as well? |
|
Well, the idea is that this is the enabler for crossing even a breaking release. For that to work, it needs to be available on both old and new side. The code from this PR basically already solves that, but a remaining problem here is efficiency: just imagine you have 100 archives referencing 1TB data each. That would mean it would read 100TB from source repo and pump 100TB over the tar pipe and that would take quite a while. See my current PR which tries to optimize this. |
|
moved to #6643 |
3 participants
fixes #5830.
export-tar: just msgpack and b64encode all item metadata and put that into a BORG specific PAX header. this is additional to the standard tar metadata.
import-tar: when detecting the BORG specific PAX header, just get all metadata from there (and ignore the standard tar metadata).