-
-
Notifications
You must be signed in to change notification settings - Fork 754
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
Borg extract hangs after about an hour. (strace: Timeout) #3866
Comments
Looks like your network or ssh connection broke down. I also use rsync.net and ubuntu 18.04 now, so I'll try to reproduce this. If you need the extraction result urgently, I can propose 2 ways that might work for you right now until we find a better solution or the root cause of the problem:
|
As you said @ThomasWaldmann the ssh connection broke down. This fixed it for me:
Is this something we could fix in borg? |
borg just uses ssh, it does not configure ssh (assuming that the user already has a working ssh configuration). if that is not the case, maybe there should be rather a bug been filed against the ssh default configuration of the ssh package. restarting a broken connection: borg does not do that, please check, iirc we might have a ticket for this already. borg extract resume: iirc we already have a ticket for that, but it is non-trivial. |
add @rvanlaar's fix to the docs / faq? |
I will add this to the FAQ / make a PR. |
Backport from master. fixes borgbackup#3866
borgbackup#4782) Add FAQ for preventing SSH timeout in extract, fixes borgbackup#3866
Have you checked borgbackup docs, FAQ, and open Github issues?
yes
Is this a BUG / ISSUE report or a QUESTION?
ISSUE
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.1.5
Operating system (distribution) and version.
Ubuntu 18.04
Hardware / network configuration, and filesystems used.
Hardware: UX501VW laptop,
network config: 250Mbit network connection
filesystems used: ext4
How much data is handled by borg?
90 GB
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg -v -p --remote-path=borg1 extract [email protected]:REPONAME::2018-05-28
Describe the problem you're observing.
After a while all activity stops, no cpu usage, no downloads
Strace shows:
select(8, [5 7], [], [4 5 7], {tv_sec=1, tv_usec=0}) = 0 (Timeout)
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
I can reproduce the issue. The issues shows up after about an hour.
I tried restarting the export. This gave the same problem.
I would like two things for borg to support.
A better retry after the timeout and borg export to be able to resume after a failure.
Restoring an 80 GB repo isn't fun this way.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: