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

Display percentage in casync extract summary #184

Conversation

elboulangero
Copy link
Contributor

This commit adds percentage to the output of casync extract, to easily see the distribution of incoming chunks among local store, local seed and remote store.

The new output looks like that:

$ casync extract -v test.caibx yop.img
Zero bytes written as sparse files: 7.3G
Bytes cloned through reflinks: 0B
Chunk requests fulfilled from local store: 127661 (100%)
Bytes used from local store: 13.9G (100%)
Chunk requests fulfilled from local seed: 0 (0%)
Bytes used from local seed: 0B (0%)
Chunk requests fulfilled from remote store: 0 (0%)
Bytes used from remote store: 0B (0%)

(see #180 for original discussion)

This commit adds percentage to the output of `casync extract`, to easily
see the distribution of incoming chunks among local store, local seed
and remote store.

The new output looks like that:

  $ casync extract -v test.caibx yop.img
  Zero bytes written as sparse files: 7.3G
  Bytes cloned through reflinks: 0B
  Chunk requests fulfilled from local store: 127661 (100%)
  Bytes used from local store: 13.9G (100%)
  Chunk requests fulfilled from local seed: 0 (0%)
  Bytes used from local seed: 0B (0%)
  Chunk requests fulfilled from remote store: 0 (0%)
  Bytes used from remote store: 0B (0%)

Signed-off-by: Arnaud Rebillout <arnaud.rebillout@collabora.com>
@poettering poettering merged commit 3eb5fcd into systemd:master Feb 19, 2019
@elboulangero elboulangero deleted the display-percentage-in-casync-extract-summary branch March 19, 2019 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants