-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
panic during copy #8077
Comments
If I had to bet, OneDrive as the throttling there is real and running defaults, I'd imagine that was doing it. |
I didn't think we caught panics anywhere, but we must be... Or something is... |
Grepping the rclone source for Neither If it was run via the @buengese are you using a patched rclone? Struggling to understand what is going on here! |
Nope, this rclone version is neither patched nor was it running via A detail I forgot in the initial post ist that both the onedrive and ulozto backend very wrapped by a crypt backend. The exact command being run was: |
The only places we recover panics are here
For a plain So maybe in a dependency.... Unless you can reproduce it I don't think we'll track it down like this! |
I've seen the error yet again in a new transfer. Once again deep into a large transfer, always twice in a row and in very much seems to be related to the rate limiting. Still now clue where its coming from. I guess I'm going to retry that transfer with a debugger attached.
|
What is the problem you are having with rclone?
I've noticed some panic errors caught by pacer when looking at the log of an
rclone copy
from onedrive to ulozto. I'm not sure where the originate. I'll try to reproduce this.What is your rclone version (output from
rclone version
)Which OS you are using and how many bits (e.g. Windows 7, 64 bit)
Ubuntu 22.04 aarch64
Which cloud storage system are you using? (e.g. Google Drive)
OneDrive and uloz.to
The command you were trying to run (e.g.
rclone copy /tmp remote:tmp
)rclone copy onedrive:/path/to/dir/ uloz:/path/to/dir/ --progress -vv
How to use GitHub
The text was updated successfully, but these errors were encountered: