Mount not detecting changes

I recently switched to mounts of team drives mounted with service accounts and now my mounts are no longer automatically detecting changes. if I use rc to refresh them then the new files will show up

I can see from the log:
Google drive root '': Checking for changes on remote
that rclone is checking for changes, but should the Google drive root be empty?

(I am not using vfs-cache-mode full)

Is there something obvious I am missing or need to remove?

Using rclone v1.53.1
running on ubuntu 18.04
Storage system: Google Drive

rclone mount teamDrive: /home/mounts/teamDrive \
--allow-other \
--drive-server-side-across-configs \
--dir-cache-time 1000h \
--log-level DEBUG \
--log-file /home/logs/teamDrive \
--poll-interval 15s \
--umask 002 \
--user-agent fubar \
--vfs-cache-mode writes \
--cache-dir=/home/_rcloneData/_cache \
--vfs-cache-max-size 75G \
--vfs-cache-max-age 336h \
--rc \
--rc-addr=localhost:5304 \
--use-mmap &

The rclone config contents with secrets removed.

[teamDrive]
type = drive
scope = drive
server_side_across_configs = true
service_account_file = /home/service/teamDrive.json
root_folder_id = 0AFXG4t3LJJmkFEfrR

(I just added team_drive = 0AFXG4t3LJJmkFEfrR to my config, but as I had to remount it will have found any new files now so will need to wait until I add more to see if it made any difference, the log still shows Google drive root as empty)
Snippet of log files

2020/10/12 15:31:19 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:19 DEBUG : Google drive root '': Checking for changes on remote
2020/10/12 15:31:20 DEBUG : : Statfs:
2020/10/12 15:31:20 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:21 DEBUG : : Statfs:
2020/10/12 15:31:21 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:22 DEBUG : : Statfs:
2020/10/12 15:31:22 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:23 DEBUG : : Statfs:
2020/10/12 15:31:23 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:24 DEBUG : : Statfs:
2020/10/12 15:31:24 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:25 DEBUG : : Statfs:
2020/10/12 15:31:25 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:26 DEBUG : : Statfs:
2020/10/12 15:31:26 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:27 DEBUG : : Statfs:
2020/10/12 15:31:27 DEBUG : : >Statfs: stat={Blocks:3932160 Bfree:3932160 Bavail:3932160 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2020/10/12 15:31:28 DEBUG : : Statfs:

Thanks

What does

rclone ls teamDrive:

show?

Just upload a new file, and that shows when I do an rclone lsl on the directory using the teamDrive: remote

542467055 2020-10-12 14:17:21.105000000 A TV Show - s03e14 - Episode 14.mkv

Have waited a few minutes and on the mount that episode is still not showing up

ok, so it has now showed up in the mount at 16:49, so not sure why it took so long to show up when the mount settings should poll every 15s

Will need to do some more accurate timings to see if I can determine if there is a specific time it takes between showing up via a direct call to the remote vs when it appears in the mount.

I guess it could be some sort of api limit. I am currently moving thousands of tiny files back from another team drive that I moved to in error.

I can never quite figure out how google allocate api request quotas between various api keys and service accounts. Possibly they are shared across all of them

If you are moving a lot of files, team drives take longer to reflect changes in what I thought as it does some indexing on the backside.

Never saw a problem with my regular google drive.

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