Skip to content

Releases: tarka/xcp

v0.7.3

02 Aug 04:15
Compare
Choose a tag to compare
  • Fix for progress-bar wrapping on smaller terminals; thanks to @ellishg for the report and fix.
  • Additional internal optimisations and cleanups from @lnicola.

v0.7.2

13 Apr 01:39
Compare
Choose a tag to compare

Minor testing and dependency fixes.

v0.7.1

14 Dec 00:41
Compare
Choose a tag to compare

Minor README updates

v0.7.0

14 Dec 00:39
Compare
Choose a tag to compare

Features:

  • The flag --no-perms has been added to skip permission copying; thanks to @lnicola for this feature.
  • Extended file attributes (xattrs) are now copied on systems that support them.
  • The parblock driver now preserves file sparse blocks.

Other improvments:

  • Some brute-force fuzz tests with randomly generated file-trees have been added, including random sparse files. These are slower so are not run with the default cargo test (unless you add the --ignored flag), but are run on CI.

v0.6.2

23 Nov 23:57
Compare
Choose a tag to compare

Fix for hanging single-file-overwrite case in parblock driver.

v0.6.1

23 Nov 23:24
Compare
Choose a tag to compare

Fixes and improvements for the parblock driver. Progress-bars now work, and performance should be more consistent.

xcp 0.6.0: Experimental block-level parallelism

18 Nov 22:33
Compare
Choose a tag to compare

The major changes in this version are:

  • The introduction of switchable 'drivers'. This has been added to facilitate experimenting with alternative strategies for copy optimisation. Currently 2 drivers are avalable:
    • 'parfile': the previous hard-coded xcp copy method, which parallelises tree-walking and per-file copying. This is the default.
    • 'parblock': An experimental driver that parallelises copying at the block level. This has the potential for performance improvements in some architectures, but increases complexity. It should be considered a work-in-progress; currently it does not support sparse files, does not play well with the progress bar, and will almost certainly eat your data. Testing is welcome.
  • A '--block-size' flag to configure size of copy operations.
  • The --no-target-directory (-T) flag from 'cp' is now supported (thanks to Walther Chen).