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.

Sign up for GitHub

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

Jump to bottom

Enable some time estimate for --progress option (or a new --progress-total) option. #543

Open
kpoeppel opened this issue Jul 16, 2023 · 1 comment · May be fixed by #547
Open

Enable some time estimate for --progress option (or a new --progress-total) option. #543

kpoeppel opened this issue Jul 16, 2023 · 1 comment · May be fixed by #547

Comments

@kpoeppel
Copy link

As btrbk diff already delivers a super nice overview of the difference of a parent and child snapshot, one could also get a time estimate during a btrbk run. This could be done by extending the existing --progress option, or by introducing a --progress-total.
Choosing this option, for every newly created snapshot btrbk diff would be run before btrfs send/receive such that the pv command can get proper -s option for the progress update.

This way it is easier to estimate the total time left, especially in cases where the network bandwidth is the limiting factor.
@kpoeppel kpoeppel linked a pull request Aug 2, 2023 that will close this issue
Open
@zwimer
Copy link

zwimer commented Sep 10, 2024

Can't this also be done by not adding -q to mbuffer and echoing the total size beforehand? mbuffer has a progress bar that runs by default that looks like this:

in @ 24.0 MiB/s, out @ 24.0 MiB/s, 4352 MiB total, buffer 100% full

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Enable --progress-total option using pv. kpoeppel/btrbk
2 participants
@zwimer @kpoeppel