Rclone crashed with mounted union / GDrives

What is the problem you are having with rclone?

I have 2 google team drives, crypted and mounted via an Rclone union. The mount stopped being accessible and rclone seemed to have completely crashed. First time i have ever seen rclone crash (in 2+years usage). Have i hit a strange bug?

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

rclone v1.60.0

  • os/version: ubuntu 22.04 (64 bit)
  • os/kernel: 5.15.0-53-generic (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.19.2
  • go/linking: static
  • go/tags: none

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

Google Drive

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

/usr/bin/rclone mount rclone-union: /GSD --allow-other --dir-cache-time 1000h --log-level INFO --log-file /opt/rclone/logs/rclone.log --poll-interval 15s --umask 002 --user-agent robinrclone --rc --rc-addr :5572 --rc-no-auth --cache-dir=/rclone-cache --vfs-cache-mode full --vfs-cache-max-size 960G --vfs-cache-max-age 336h --bwlimit-file 350M

The rclone config contents with secrets removed.

type = drive
client_id = 
client_secret = 
scope = drive
service_account_file = /opt/rclone/sa_credentials/catwoman-gsd-mount.json
team_drive =

type = crypt
remote = GSD:files
password = 
password2 =

type = drive
client_id = 
client_secret = 
scope = drive
service_account_file = /opt/rclone/sa_credentials/catwoman-gsd2-mount.json
team_drive = 
root_folder_id = 

type = crypt
remote = GSD2:files
password = 
password2 =

type = union
upstreams = GSDcrypt::nc GSD2crypt::nc

A log from the command with the -vv flag

Log in pastebin as its over 700 lines.


That is a weird error.

It is an internal error from the Go runtime indicating something got messed up with its memory.

There are a couple of issues about this, but all closed with the report being memory corruption from elsewhere.

So I'd suspect that your computer might have bad RAM, or it might just be the result of an alpha particle flipping a bit in the RAM (which does happen, especially in consumer hardware with no ECC).

So if this was my machine I'd take it offline and run memtest86 on it for 24 hours. If that is OK then I'd assume it was a soft memory error and cross fingers it doesn't happen again!



Thanks for the advice. I'll find a suitable window to take it out of service and test the memory. Will keep an eye on it in the meantime.

Thanks for all your hard work on rclone, it's a brilliant bit of software.

1 Like