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

Very little progress output on prune #1322

Closed
darkskiez opened this issue Oct 4, 2017 · 3 comments
Closed

Very little progress output on prune #1322

darkskiez opened this issue Oct 4, 2017 · 3 comments

Comments

@darkskiez
Copy link

@darkskiez darkskiez commented Oct 4, 2017

Output of restic version

restic 0.7.2 (v0.7.2-0-g5b1e4df1)

How did you run restic exactly?

restic prune

What backend/server/service did you use?

sftp

Expected behavior

pruned repo

Actual behavior

12h so far of:

counting files in repo

Steps to reproduce the behavior

Have a large remote repo

Do you have any idea what may have caused this?

Do you have an idea how to solve the issue?

Some progress on the prune would be nice (if it cant be made faster.)

@fd0
Copy link
Member

@fd0 fd0 commented Oct 4, 2017

Huh, that's really odd. Between the line "counting files in repo" and the start of the progress output it really only lists the files in the backend. Is maybe the terminal output blocked? Can you try pressing ^Q (ctrl+Q)?

Or has the sftp connection stalled?

It really shouldn't take so much time.

@darkskiez
Copy link
Author

@darkskiez darkskiez commented Oct 12, 2017

So, I sadly think its a problem with restic over slow links.. I tried running prune locally but the RPI3 OOMed pretty quickly..

I've sadly had to give up on restic for now, trying borgbackup instead as it seems robust to over-the-internet backups.

@fd0
Copy link
Member

@fd0 fd0 commented Oct 12, 2017

But that's a different problem. We already know that restic needs a lot of memory right now (and we need to work on that), but what about the slow sftp connection?

I can understand if you don't have any interest to investigate further (and I'm happy you've found a backup solution that works for you), so feel free to close this issue.

@darkskiez darkskiez closed this Oct 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.