RClone + GSuites Contribute permissions = lockup

What is the problem you are having with rclone?

I have service accounts with contribute access, they can add and read, but unfortunately at delete the mount just locks up.

What is your rclone version (output from rclone version)

1.51.0

Command

ExecStart=/usr/bin/rclone mount G*******: /GDrive/********
--allow-other
--dir-cache-time 160h
--fuse-flag sync_read
--tpslimit 10
--tpslimit-burst 10
--buffer-size=1G
--attr-timeout=1s
--vfs-read-chunk-size=256M
--vfs-cache-max-age=5m
--vfs-cache-mode=writes
--vfs-read-chunk-size-limit=off
--log-level DEBUG
--log-file /var/log/rclone-g*******.log
--timeout 1h
--umask 002
--rc

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Debian 10

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The rclone config contents with secrets removed.

[GMovies]
type = drive
client_id = 4******************************
client_secret = ********************
scope = drive
service_account_file = /home/s0n1cm0nk3y/.config/rclone/serviceaccounts/*******************.json
team_drive = 0A*****************

[G*******Crypt]
type = crypt
remote = G********s:
filename_encryption = standard
password = ******************************

Logs

2020/07/03 08:36:07 DEBUG : /: Attr:
2020/07/03 08:36:07 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwxr-x, err=
2020/07/03 08:36:07 DEBUG : /: ReadDirAll:
2020/07/03 08:36:07 DEBUG : /: >ReadDirAll: item=953, err=
2020/07/03 08:36:07 DEBUG : /: Attr:
2020/07/03 08:36:07 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwxr-x, err=
2020/07/03 08:36:07 DEBUG : /: Lookup: name="bob"
2020/07/03 08:36:07 DEBUG : /: >Lookup: node=bob, err=
2020/07/03 08:36:07 DEBUG : bob: Attr:
2020/07/03 08:36:07 DEBUG : bob: >Attr: a=valid=1s ino=0 size=0 mode=-rw-rw-r--, err=
2020/07/03 08:36:07 DEBUG : /: Lookup: name="bob"
2020/07/03 08:36:07 DEBUG : /: >Lookup: node=bob, err=
2020/07/03 08:36:07 DEBUG : bob: Attr:
2020/07/03 08:36:07 DEBUG : bob: >Attr: a=valid=1s ino=0 size=0 mode=-rw-rw-r--, err=
2020/07/03 08:36:07 DEBUG : Google drive root '': Checking for changes on remote
2020/07/03 08:36:09 DEBUG : /: Attr:
2020/07/03 08:36:09 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwxr-x, err=
2020/07/03 08:36:09 DEBUG : /: ReadDirAll:
2020/07/03 08:36:09 DEBUG : /: >ReadDirAll: item=953, err=
2020/07/03 08:36:09 DEBUG : /: Attr:
2020/07/03 08:36:09 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwxr-x, err=
2020/07/03 08:36:09 DEBUG : /: Lookup: name="bob"
2020/07/03 08:36:09 DEBUG : /: >Lookup: node=bob, err=
2020/07/03 08:36:09 DEBUG : bob: Attr:
2020/07/03 08:36:09 DEBUG : bob: >Attr: a=valid=1s ino=0 size=0 mode=-rw-rw-r--, err=
2020/07/03 08:36:09 DEBUG : /: Lookup: name="bob"
2020/07/03 08:36:09 DEBUG : /: >Lookup: node=bob, err=
2020/07/03 08:36:09 DEBUG : bob: Attr:
2020/07/03 08:36:09 DEBUG : bob: >Attr: a=valid=1s ino=0 size=0 mode=-rw-rw-r--, err=
2020/07/03 08:36:10 DEBUG : /: Remove: name="bob"
2020/07/03 08:37:07 DEBUG : Google drive root '': Checking for changes on remote
2020/07/03 08:38:07 DEBUG : Google drive root '': Checking for changes on remote
2020/07/03 08:39:07 DEBUG : Google drive root '': Checking for changes on remote
2020/07/03 08:40:07 DEBUG : Google drive root '': Checking for changes on remote
2020/07/03 08:41:07 DEBUG : Google drive root '': Checking for changes on remote
2020/07/03 08:42:07 DEBUG : Google drive root '': Checking for changes on remote
2020/07/03 08:43:07 DEBUG : Google drive root '': Checking for changes on remote
2020/07/03 08:44:07 DEBUG : Google drive root '': Checking for changes on remote

I don't see any deletes in the log?

Try the latest stable version 1.52.2 and see if that helps? If not try the latest beta. If that doesn't help then I'll tell you how to debug further!

Latest update seems to be helping though I had a question. User in contribute does indeed get I/O errors at delete. But after another user with full control deletes it, the contribute user is now able to delete it. Is this normal operation?

Give your SA manager access and you won't have issues

within the email group? If your talking content manager vs contributor I want the SA to have contribute access for a reason. Its just the locking up part that was the issue.

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