STOP and READ USE THIS TEMPLATE NO EXCEPTIONS - By not using this, you waste your time, our time and really hate puppies. Please remove these two lines and that will confirm you have read them.
What is the problem you are having with rclone?
See below
Run the command 'rclone version' and share the full output of the command.
rclone v1.66.0
- os/version: Microsoft Windows 11 23H2 (64 bit)
- os/kernel: 10.0.22631.3527 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.22.1
- go/linking: static
- go/tags: cmount
Which cloud storage system are you using? (eg Google Drive)
Mega over WebDAV
The command you were trying to run (eg rclone copy /tmp remote:tmp)
.\rclone.exe check /SMB/over/LAN/ /Mega/remote/over/WebDAV -P -vv --dump bodies
Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
Just ordinary WebDAV endpoint behind crypt
A log from the command that you were trying to run with the -vv flag
2024/05/03 11:24:44 Failed to check: couldn't list files: read tcp 127.0.0.1:RANDOM_PORT->127.0.0.1:4443: i/o timeout
So I finished syncing ~50K files from local to remote (Mega over WebDAV), but when I tried to run rclone check afterwards, the program would get stuck at ~42K files with no progress being made, and just silently keep retrying. After ~50 mins (reaching 10 errors?) it quits. It seems all files got successfully uploaded to Mega as reported by the web portal (total size & no. of files seem to match) but at a certain point the list command fails.
Problem is even when running with -vv --dump bodies no useful info was generated. I was able to see response bodies and file paths being printed out subdir by subdir, but at the time the first ~42K files were listed, there's no more output, only:
// shown summarily after the last successful output
2024/05/03 11:24:44 NOTICE: Encrypted drive 'remote:/crypt': 1 differences found
2024/05/03 11:24:44 NOTICE: Encrypted drive 'remote:/crypt': 1 errors while checking
// then prints out ~42K files' hashes can't be checked etc, basically stopping here
// and then the last error msg in the title
2024/05/03 11:24:44 Failed to check: couldn't list files: read tcp 127.0.0.1:RANDOM_PORT->127.0.0.1:4443: i/o timeout
If I remove --dump bodies it actually shows the entire 10 retries, each time with a different random port, and how the pacer changes its sleep interval etc, but still no further info.
I am suspecting that it might have to do with non-ASCII characters in the filename / filepath, but there's no practical way to find out exactly which with the tools I have right now. Can anyone point me in the right direction? TIA.