The log is too big, as it contains one entry per file. The rclone config contents with secrets removed. Experimentally it will continue to grow without limit, and ends up stalling when all the time is spent swapping.
I stopped the command once it started using 10% of my memory. rclone-ignore -links -v -v -memprofile=/tmp/rclone-profile3 /home idrive-e2-encrypted:backup-marelle-home IDrive e2 The command you were trying to run (eg rclone copy /tmp remote:tmp) sudo rclone -log-file=/tmp/rclone.log -config /root/.config/rclone/nf -retries 1 -ignore-errors sync -exclude-if-present. Which cloud storage system are you using? (eg Google Drive) Rclone sync is using all my memory with the iDrive+crypt backend Run the command 'rclone version' and share the full output of the command. The scripts only deal with the high level things like authentication, configuring, etc (all using the REST API) while the uploads and downloads are deferred to the command line program (the scripts can do upload/download with the REST API as well if hey can't find the binary).What is the problem you are having with rclone? Besides the perl scripts, there is a pre-compiled binary command line utility to deal with high-efficiency data transfers. Their code is a complete mess and I started making a Python replacement before finding rclone for all my other data-movement needs. I have somewhat studied their perl scripts for idrive-backup (which may also be used for idrive-sync). I am curious if either the idrive-backup or idrive-sync support S3 as well.
0 kommentar(er)
