[Google Drive] nfsmount on shared drive with service accounts can't delete files

Hello

I was this morning helping setting up rclone nfsmount in a Mac I’m not an owner of, hence why I won’t be able to provide all the required details now (I’m away from that Mac) but hopefully I can get some help/ideas of what could be wrong in the meantime.

What is the problem you are having with rclone?

Creating files and renaming works fine when using rclone nfsmount of a crypted shared Drive remote using a service account. Howerver, if I try to delete a file or a folder, I get an Input/output error (in zsh) or error 66 in Finder’s GUI.

When revising error logs, the error outputted is something like googleApi: 404 Not found file with Id XXXX. In the case of the folders (which logs the exact same message error, referring to the folder as a file), if I acess Drive’s WebUI with that specific ID (https://drive.google.com/drive/folders/XXXX), the folder exists, so I’m not sure why it could not be found and deleted.

At the time I was in front of the Mac I didn’t thought about issuing rclone rm or rclone rmdir commands, sorry.

Run the command 'rclone version' and share the full output of the command.

This is one of the fields I won’t be able to fill properly, sorry :sweat_smile:

Tested with rclone 1.73.2 and beta, both installed using the script in downloads page, in a iMac M1 with macOS 26.3.1 Tahoe (latest available for the device).

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

Google Drive Shared Drives (with a service account appointed as “content manager” of it).

The command you were trying to run (eg rclone copy /tmp remote:tmp)

/usr/local/bin/rclone nfsmount --config /Users/xx/.config/rclone/rclone.conf --vfs-cache-mode full --allow-other --drive-chunk-size=256M --track-renames --fix-case --links --vfs-links --vfs-cache-max-size 1G --volname RemoteTimeMachine Backup: /Users/xx/RemoteTimeMachine

I’m mounting it at boot like this with launchctl, in case it’s relevant:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.rclone.mount</string>
    <key>ProgramArguments</key>
    <array>
        <string>/usr/local/bin/rclone</string>
        <string>nfsmount</string>
	<string>--config</string>
	<string>/Users/xx/.config/rclone/rclone.conf</string>
        <string>--vfs-cache-mode</string>
        <string>full</string>
        <string>--allow-other</string>
	<string>--drive-chunk-size=256M</string>
	<string>--track-renames</string>
	<string>--fix-case</string>
	<string>--links</string>
	<string>--vfs-links</string>
	<string>--vfs-cache-max-size</string>
	<string>1G</string>
	<string>--volname</string>
	<string>RemoteTimeMachine</string>
	<string>Backup:</string>
	<string>/Users/xx/RemoteTimeMachine</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>KeepAlive</key>
    <true/>
    <key>StandardErrorPath</key>
    <string>/var/log/rclone.err</string>
    <key>StandardOutPath</key>
    <string>/var/log/rclone.out</string>
</dict>
</plist>

I tested without the –links and –vfs-links arguments, with no avail

The rclone config contents with secrets removed.

[BackupDrive]
type = drive
scope = drive
use_trash = false
skip_gdocs = true
server_side_across_configs = true
disable_http2 = false
acknowledge_abuse = true
stop_on_upload_limit = true
stop_on_download_limit = true
skip_shortcuts = true
skip_dangling_shortcuts = true
team_drive = REDACTED
root_folder_id = 
service_account_file = $RCLONE_CONFIG_DIR/sa_backup.json

[Backup]
type = crypt
remote = BackupDrive:REDACTED
password = REDACTED
password2 = REDACTED
strict_names = true
filename_encoding = base32768
suffix = none

A log from the command with the -vv flag

I didn’t ran it with the -vv flag, but as mentioned in the description, the source of the error (as seen in /var/log/rclone.err) is a 404 error from the API.

fwiw, no point in testing complex nfsmount, until simple command work


need to post a debug log.
and for a deeper look at the api calls, --dump=headers