Rclone move, write data

Help and Support
1

Why rclone write data to the source dir, when using rclone move command?

iotop —only

TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND 

20379 be/4 benba     715.78 K/s 1126.69 K/s  0.00 % 89.33 % rclone move ..

17338 be/4 benba       3.31 M/s    0.00 B/s  0.00 %  0.00 % rclone copy ...
2

Can you share what command you are running? What backend are you using?

3 
/bin/rclone move /directory/ GoogleDriveCrypt:directory/ --progress 
--checkers 1 --log-file ~/logs/upload.log -v --tpslimit 3 --transfers 3 
--drive-chunk-size 128M --create-empty-src-dirs --delete-empty-src-dirs

Backend: GoogleDrive + Crypt

4

And that's the process that was causing the IO? That seems strange I wouldn't expect that much IO at all with the move and it should be a lot of read and some minor activity for the log writing, but you are only doing INFO level logging which is not that much.

I tested some moves and I can't seem to recreate that.

Assuming you are the latest version of rclone as well?

5

not quite

rclone v1.47.0

  • os/arch: linux/amd64
  • go version: go1.12.4
6

That's pretty recent. Can you run the same thing and try to run lsof against the pid and see what it is doing?

lsof -p

and you can see what it's writing to.

7

With rclone move rclone will delete the files on the source - I guess that could show up as disk write - I'm not sure.

Also check your config, make sure that stuff is really going to google drive and you haven't accidentally pointed stuff to local disk by forgetting the : in the remote name.

8

Only previous copied (rclone copy) files are affected.
Any ideas, what happens in the background?

9

As I stated above, please see what's writing:

lsof -p

and you can see what it's writing to.

10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.