Getting this error everytime the command runs. Is there something that is needed to be done to this folder?
2020/07/19 07:48:20 NOTICE: Google drive root 'Encrypted/8nak3756llo68qkpg06nt70mg0': Disabling ListR to work around bug in drive as multi listing (3) returned no entries
2020/07/19 07:48:20 NOTICE: Google drive root 'Encrypted/8nak3756llo68qkpg06nt70mg0': Re-enabling ListR as previous detection was in error
What is your rclone version (output from rclone version)
1.52.2
Which OS you are using and how many bits (eg Windows 7, 64 bit)
It is a docker image (RHEL7)
Which cloud storage system are you using? (eg Google Drive)
GDrive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
[Gdrive]
type = drive
scope = drive
client_id =
client_secret =
token = {"access_token":"","token_type":"Bearer","refresh_token":"","expiry":""}
root_folder_id =
[Crypt]
type = crypt
remote = Gdrive:/Encrypted
filename_encryption = standard
password =
password2 =
A log from the command with the -vv flag
2020/07/19 07:48:20 NOTICE: Google drive root 'Encrypted/8nak3756llo68qkpg06nt70mg0': Disabling ListR to work around bug in drive as multi listing (3) returned no entries
2020/07/19 07:48:20 NOTICE: Google drive root 'Encrypted/8nak3756llo68qkpg06nt70mg0': Re-enabling ListR as previous detection was in error
Thanks for the quick response -- I am already running this with verbose logging as you can see below. The is the log entry that gets spammed when the rclone command is run in the docker instance.
That is essentially the command is my point. I can show you all the variables I pass to it, but since it's a docker it does not have a generic rclone command that is listed:
Depending if you just moved a bunch of stuff, Google Drive sometimes take some time to catch up. It doesn't seem to be a team drive though as that's normally where I see it.
fast-list does some magical indexing on the backside to speed things up and if it detects an error, it just does a regular listing so I don't think that should be an issue and should go away on its own over time.
Agreed that moving to NOTICE would be better -- Thanks for the information. I don't have a lot of empty directory but I do have a LOT of directories, I think over 1k in that folder. So maybe it's having a tough time getting them all.
As long as it's not effecting anything I don't mind but it would clean up the NOTICE logs which would be nice.