Google drive name corrupted with added '{P2dbo}' when mounting with '--drive-acknowledge-abuse' flag

Help and Support
1

I am using rclone to mount a Google Drive using the --drive-acknowledge-abuse flag to allow access to files that Google (mistakenly) thinks are spam or malware. This causes the string '{P2db0}' to be appended to the drive name returned by df --output=source in recent versions of rclone.

Specifically, in older versions -- e.g., version v1.45 (on a RPi4 running Debian Buster) and v1.50.2 (on Ubuntu 18.04) ---- when I type df --output=source, I get back the exact drive name that I used to mount my google drive -- both with and without the --drive acknowledge-abuse flag

# usr/bin/rclone mount --allow-other  --daemon my_drive_name: /home/me/gdrive
# df --output=source ~/gdrive
my_drive_name:

# usr/bin/rclone mount --allow-other --drive-acknowledge-abuse --daemon my_drive_name: /home/me/gdrive
# df --output=source ~/gdrive
my_drive_name:

But in v1.60.1-DEV (on Raspbery Pi5 and Pi0v2 running Bookworm), I get an extra {P2db0} appended to the drive name when I use the flag:

# usr/bin/rclone mount --allow-other  --daemon my_drive_name: /home/me/gdrive
# df --output=source ~/gdrive
my_drive_name:

# usr/bin/rclone mount --allow-other --drive-acknowledge-abuse --daemon my_drive_name: /home/me/gdrive
# df --output=source ~/gdrive
my_drive_name{P2db0}:

This causes several of my scripts to fail since they expect to see the drive name when they do a df --ouput=source

  • Is this the expected and desired behavior? (I don't see it documented)
  • Also is this the string that is always added or is it a random string that will differ from drive to drive?
  • Is there any way to avoid having the string appended?
2

welcome to the forum,

yes

  1. If you supply extra configuration to a backend by command line flag, environment variable or connection string then rclone will add a suffix based on the hash of the config to the name of the remote.
    This is so rclone can tell the modified remote apart from the unmodified remote when caching the backends
  2. Make sure backends with additional config have a different name for caching
  3. a debug log would show
    DEBUG : remote: detected overridden config - adding "{P2dbo}" suffix to name
  1. remove --drive-acknowledge-abuse from the command line.
  2. add acknowledge_abuse = true to the remote in the config file

that is a many years old, unofficial, custom compiled, development version of rclone.

  1. rclone selfupdate
    or
  2. uninstall that ancient version and https://rclone.org/install/#script-installation
1 Like
3

Thanks - worked perfectly. I wasn't aware that there was a difference between adding on command line vs. rclone.conf

Thanks. Someone should probably tell that to the Debian and Ubuntu maintainers as that is the latest version in Debian Bookworm (and hence also for RPi) and similarly in Ubuntu 24.04 & 25.04.

So probably millions of users are unawaringly using an "ancient version" :slight_smile:

5

Feel free since you are using their distro :slight_smile:

6

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