I used the following script to mount my Google Drive Remote which was configured with my own client id and secret... But unfortunately since, Nov 17 2024, My Files and Folders slowly started to delete from my Google Drive and was in the Google Drive Bin.
Fortunately, I was able to recover all of them from the Google Drive Bin, I hope that all are recovered without any miss. I recovered them after stopping the mount service. I also deleted that remote from my System.
Run the command 'rclone version' and share the full output of the command.
Just now I noticed that I have defined a log file, but unfortunately, it does not exist in the /tmp directory...It must be because I restarted my computer. Is there anywhere else I can get the logs of rclone...
Or shall I recreate the rclone remote with the same client id and secret and mount a temporary subdirectory and check whether it repeats, if it does, will get the logs...
Something on your mount was deleting things as rclone is just a tool. If you think of a hammer breaking something, the hammer is just the tool that was used. Someone swung the hammer and hit something.
If rclone was mounted and files are removed, some other piece of software/human removed files.
Looks like you are running a mount as root which I personally would not do. If you are concerned about things, you'd lock down permissions and ensure what has the ability to delete and go from there.
And I'm like 99% sure I see the issue.
That fusermount won't work if things are hitting the mount point as it's also fusermount3 these days.
So it doesn't unmount and you are removing all the files..
I'd imagine if you to remove a folder, you'd use rmdir instead.
I'm not a huge fan of removing the mount point and re-adding it and I tend to keep things as simple as possible.
Stop a network mount means you have to stop all IO/processes hitting the mount and then you can unmount it.
Systemd will end up just killing it after 60 seconds and you end up in a funky state.
When I was using it, I would tie all my dependencies back and you can validate no processes are hitting the mount via fuser or something until you are sure you have everything quiet before unmounting it.