What is the problem you are having with rclone?
I'm not sure what I'm doing wrong or perhaps overlooked in the documentation. I've also not found any existing forum posts searching here and elsewhere that address this particular issue. Here's what I'm running into:
- rclone works brilliantly when I sync a local directory to a Google Drive remote.
- When I attempt to use rclone to list, sync, or copy from a Google Drive remote to a local directory, it does not locate or "see" any existing Google Drive files or directories visible in the Web UI, except:
- When I try to list (
ls) the contents in a Google Drive remote, rclone does locate or "see" a directory or file I manually created/uploaded using the rclone remote (such as the 'test' directory which contains a 'test.txt' file in the screenshot below), but nothing else.
- When I try to list (
Run the command 'rclone version' and share the full output of the command.
rclone v1.53.3-DEV
- os/arch: linux/amd64
- go version: go1.18.1
I'm running rclone on a physical (non-VM) Linux host:
- Distributor ID: Ubuntu
- Description: Ubuntu 22.04.4 LTS
- Release: 22.04
- Codename: jammy
- Kernel: 5.15.0-113-generic
Which cloud storage system are you using? (eg Google Drive)
Google Drive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone ls -vv GoogleBackup:
Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
To my knowledge, there's not a more recent rclone package available in the release of Ubuntu Linux I'm using that supports the 'config redacted' option. As an alternative, I've attempted to manually redact my config file:
[GoogleSync]
type = drive
client_id = ***
client_secret = ***
scope = drive.file
root_folder_id = someNonRootFolderId
token = ***
[GoogleBackup]
type = drive
client_id = ***
client_secret = ***
scope = drive
root_folder_id = anotherNonRootFolderId
token = ***
I'm purposefully limiting these remotes to a specific folder that's not the root of my Google Drive.
My intent is to use the GoogleSync remote to make local files on my Linux machine available in Google Drive (this works great!).
As for the GoogleBackup remote, my intent is to keep a backup of content in that Google Drive directory on my local Linux machine. Ideally, I would like to use the '"drive.readonly" scope, but I tried setting this up with "drive" in the interim to see if it helped (it didn't).
A log from the command that you were trying to run with the -vv flag
Command output:
2024/07/18 12:47:47 DEBUG : rclone: Version "v1.53.3-DEV" starting with parameters
["rclone" "ls" "-vv" "GoogleBackup:"]
2024/07/18 12:47:47 DEBUG : Using config file from "/home/kevansizemore/.config/rclone/rclone.conf"
2024/07/18 12:47:47 DEBUG : Creating backend with remote "GoogleBackup:"
5 test/test.txt
2024/07/18 12:47:48 DEBUG : 4 go routines active
Log file content:
$ cat rcloneLog.txt
2024/07/18 13:00:20 DEBUG : rclone: Version "v1.53.3-DEV" starting with parameters ["rclone" "ls" "-vv" "GoogleBackup:" "--log-file=/home/kevansizemore/scripts/rcloneLog.txt"]
2024/07/18 13:00:20 DEBUG : Using config file from "/home/kevansizemore/.config/rclone/rclone.conf"
2024/07/18 13:00:20 DEBUG : Creating backend with remote "GoogleBackup:"
2024/07/18 13:00:20 DEBUG : 4 go routines active
I appreciate your time and consideration. Rclone has worked brilliantly for me for years, this is the first time I've encountered something I could not figure out from studying the (great!) documentation or searching the support forums.
Is there something about my approach that's causing the issue I'm experiencing?
Do I need to forego the rclone package available in this release of Ubuntu and try to manually install a more recent version?