Rclone mounts stopped working on archlinux rclone 1.68.0 - complete system failure

Help and Support
1

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)

[Unit]
After = network.target

[Service]
Type=notify
RestartSec=5
ExecStart = rclone mount gdrive: /home/<USER>/gdrive-rclone \
# --allow-other \
# --umask 002 \
--umask 077 \
--rc --rc-addr :<PORT> --rc-user <USER> --rc-pass <PASSWORD> \
--cache-dir /home/<USER>/.cache/rclone/gdrive \
--vfs-cache-mode full \
--vfs-cache-poll-interval 5m \
--vfs-cache-max-age 8760h \
--vfs-cache-max-size 10G \
--attr-timeout 8700h \
--dir-cache-time 8760h \
--poll-interval 10s \
--multi-thread-streams 0
# --log-file /home/<USER>/.config/rclone/gdrive.log

ExecStop = fusermount -uz /home/<USER>/gdrive-rclone
ExecStartPost = rclone rc vfs/refresh recursive=true --fast-list --drive-pacer-min-sleep 10ms _async=true --rc-addr :<PORT> --rc-user <USER> --rc-pass <PASSWORD> --timeout 0
Restart = on-failure

[Install]
WantedBy = default.target

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[aws-glacier-deep]
type = s3
provider = AWS
access_key_id = XXX
secret_access_key = XXX
region = eu-west-1
location_constraint = eu-west-1
acl = private
storage_class = DEEP_ARCHIVE

[aws-glacier-deep-crypt]
type = crypt
remote = aws-glacier-deep:tjspbukwhiocn/crypt
password = XXX
password2 = XXX

[backup-android-pixel6]
type = crypt
remote = gdrive:vutwHxZMnzyMn
password = XXX
password2 = XXX

[bm3-share]
type = crypt
remote = gdrive:tUUYKzZWvBOzvPqxn
password = XXX
password2 = XXX

[gdrive]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
token = XXX
root_folder_id = XXX
team_drive =

[gdrive-crypt]
type = crypt
remote = gdrive:crypt
password = XXX
password2 = XXX

[music-host3]
type = crypt
remote = gdrive:6qrOwjFxihbydswHn
password = XXX
password2 = XXX

[notes]
type = crypt
remote = gdrive:JyEsdYawaFTmn
password = XXX
password2 = XXX
### Double check the config for sensitive info before posting publicly

A log from the command that you were trying to run with the -vv flag

Oct 06 12:27:33 host3 systemd[1436]: mount-rclone-gdrive.service: Scheduled restart job, restart counter is at 1.
Oct 06 12:27:33 host3 systemd[1436]: Starting mount-rclone-gdrive.service...
Oct 06 12:27:33 host3 rclone[16124]: NOTICE: Serving remote control on http://[::]:5573/
Oct 06 12:27:33 host3 rclone[16124]: CRITICAL: Fatal error: failed to mount FUSE fs: directory already mounted, use --allow-non-empty to mount anyway: /home/user1/gdrive-rclone
Oct 06 12:27:33 host3 systemd[1436]: mount-rclone-gdrive.service: Main process exited, code=exited, status=1/FAILURE
Oct 06 12:27:33 host3 systemd[1436]: mount-rclone-gdrive.service: Failed with result 'exit-code'.
Oct 06 12:27:33 host3 systemd[1436]: Failed to start mount-rclone-gdrive.service.

Oct 06 12:34:28 host3 systemd[1431]: mount-rclone-gdrive.service: Scheduled restart job, restart counter is at 36.
Oct 06 12:34:28 host3 systemd[1431]: Starting mount-rclone-gdrive.service...
Oct 06 12:34:28 host3 rclone[11853]: NOTICE: Serving remote control on http://[::]:5573/
Oct 06 12:34:29 host3 rclone[11890]: {
Oct 06 12:34:29 host3 rclone[11890]:         "error": "connection failed: Post \"http://[\\\":5573\\\"]/vfs/refresh\">
Oct 06 12:34:29 host3 rclone[11890]:         "path": "vfs/refresh",
Oct 06 12:34:29 host3 rclone[11890]:         "status": 503
Oct 06 12:34:29 host3 rclone[11890]: }
Oct 06 12:34:29 host3 rclone[11890]: NOTICE: Failed to rc: connection failed: Post "http://[\":5573\"]/vfs/refresh": >
Oct 06 12:34:29 host3 systemd[1431]: mount-rclone-gdrive.service: Control process exited, code=exited, status=1/FAILU>
Oct 06 12:34:29 host3 rclone[11853]: ERROR : /home/user1/gdrive-rclone: Unmounted rclone mount
Oct 06 12:34:29 host3 systemd[1431]: mount-rclone-gdrive.service: Main process exited, code=exited, status=143/n/a
Oct 06 12:34:29 host3 systemd[1431]: mount-rclone-gdrive.service: Failed with result 'exit-code'.
Oct 06 12:34:29 host3 systemd[1431]: Failed to start mount-rclone-gdrive.service.
2

I might have solved it, but there is another issue. Just remembered that it was already a reported bug in 1.67, but I forgot that the temporary fix was --url instead of --rc-addr, while I kept trying --rc-url...

on top of that there was another issue (as faith often has it) that before rebooting I started a large transfer of files, which seems to have continued after reboot - this seems to be a bug where I can't mount this one remote now, although other remotes mount fine, presumably until that transfer of files finishes - trying to mount it now only times out:

Oct 06 13:02:31 host3 systemd[1496]: mount-rclone-gdrive-crypt.service: Consumed 1.479s CPU time, 86.3M memory peak.
Oct 06 13:02:31 host3 systemd[1496]: Starting mount-rclone-gdrive-crypt.service...
Oct 06 13:02:31 host3 rclone[9520]: NOTICE: Serving remote control on http://[::]:5574/
Oct 06 13:04:01 host3 systemd[1496]: mount-rclone-gdrive-crypt.service: start operation timed out. Terminating.
Oct 06 13:04:01 host3 systemd[1496]: mount-rclone-gdrive-crypt.service: Main process exited, code=exited, status=143/n/a
Oct 06 13:04:01 host3 systemd[1496]: mount-rclone-gdrive-crypt.service: Failed with result 'timeout'.
Oct 06 13:04:01 host3 systemd[1496]: Failed to start mount-rclone-gdrive-crypt.service.

I will be able to confirm that only after transfer finishes of course...

3

issue appears to be primarily with a gdrive-crypt remote (the one that transferred large amounts of files before reboot)

I am able to mount it fine with just:

rclone mount gdrive-crypt: /home/user/gdrive-rclone-crypt

but it fails with options:

rclone mount gdrive-crypt: /home/user/gdrive-rclone-crypt --umask 077 --rc --rc-addr :<PORT> --rc-user user1 --rc-pass <PASSWORD> --cache-dir /home/user1/.cache/rclone/gdrive-encrypted --vfs-cache-mode full --vfs-cache-poll-interval 5m --vfs-cache-max-age 8760h --vfs-cache-max-size 10G --attr-timeout 8700h --dir-cache-time 8760h --poll-interval 10s --multi-thread-streams 0
2024/10/06 13:25:46 NOTICE: Serving remote control on http://[::]:5574/

~ ❯ ls gdrive-rclone-crypt/                                                                                   
"gdrive-rclone-crypt/": Transport endpoint is not connected (os error 107)

I've tried swapping --rc-addr in mount command with --url, but this didn't work.

4

adding -vvvv debug options seems to have explained the issue - as mentioned before that large transfer of many small files must have caused, what seems to be "transfers excceeded" limit in google drive api - truncated log below:

~ 3m 35s ❯ rclone mount gdrive-crypt: /home/<USER>/gdrive-rclone-crypt --umask 077 --rc --rc-addr :<PORT> --rc-user <USER> --rc-pass <PASSWORD> --cache-dir /home/<USER>/.cache/rclone/gdrive-encrypted --vfs-cache-mode full --vfs-cache-poll-int
erval 5m --vfs-cache-max-age 8760h --vfs-cache-max-size 10G --attr-timeout 8700h --dir-cache-time 8760h --poll-interval 10s --multi-thread-streams 0 -vvvv
2024/10/06 13:29:26 DEBUG : rclone: Version "v1.68.0" starting with parameters ["rclone" "mount" "gdrive-crypt:" "/home/<USER>/gdrive-rclone-crypt" "--umask" "077" "--rc" "--rc-addr" ":<PORT>" "--rc-user" "<USER>" "--rc-pass" "<PASSWORD>" "-
-cache-dir" "/home/<USER>/.cache/rclone/gdrive-encrypted" "--vfs-cache-mode" "full" "--vfs-cache-poll-interval" "5m" "--vfs-cache-max-age" "8760h" "--vfs-cache-max-size" "10G" "--attr-timeout" "8700h" "--dir-cache-time" "8760h" "--poll-inter
val" "10s" "--multi-thread-streams" "0" "-vvvv"]
2024/10/06 13:29:26 INFO  : Using --user <USER> --pass XXXX as authenticated user
2024/10/06 13:29:26 NOTICE: Serving remote control on http://[::]:<PORT>/
2024/10/06 13:29:26 DEBUG : Creating backend with remote "gdrive-crypt:"
2024/10/06 13:29:26 DEBUG : Using config file from "/home/<USER>/.config/rclone/rclone.conf"
2024/10/06 13:29:26 DEBUG : Creating backend with remote "gdrive:crypt"
2024/10/06 13:29:26 DEBUG : vfs cache: root is "/home/<USER>/.cache/rclone/gdrive-encrypted"
2024/10/06 13:29:26 DEBUG : vfs cache: data root is "/home/<USER>/.cache/rclone/gdrive-encrypted/vfs/gdrive-crypt"
2024/10/06 13:29:26 DEBUG : vfs cache: metadata root is "/home/<USER>/.cache/rclone/gdrive-encrypted/vfsMeta/gdrive-crypt"
2024/10/06 13:29:26 DEBUG : Creating backend with remote ":local,encoding='Slash,Dot':/home/<USER>/.cache/rclone/gdrive-encrypted/vfs/gdrive-crypt/"
2024/10/06 13:29:26 DEBUG : :local: detected overridden config - adding "{bxYPm}" suffix to name
2024/10/06 13:29:26 DEBUG : fs cache: renaming cache item ":local,encoding='Slash,Dot':/home/<USER>/.cache/rclone/gdrive-encrypted/vfs/gdrive-crypt/" to be canonical ":local{bxYPm}:/home/<USER>/.cache/rclone/gdrive-encrypted/vfs/gdrive-crypt"
2024/10/06 13:29:26 DEBUG : Creating backend with remote ":local,encoding='Slash,Dot':/home/<USER>/.cache/rclone/gdrive-encrypted/vfsMeta/gdrive-crypt/"
2024/10/06 13:29:26 DEBUG : :local: detected overridden config - adding "{bxYPm}" suffix to name
2024/10/06 13:29:26 DEBUG : fs cache: renaming cache item ":local,encoding='Slash,Dot':/home/<USER>/.cache/rclone/gdrive-encrypted/vfsMeta/gdrive-crypt/" to be canonical ":local{bxYPm}:/home/<USER>/.cache/rclone/gdrive-encrypted/vfsMeta/gdriv
e-crypt"
2024/10/06 13:29:28 DEBUG : mailing list archive 2/1432252252.MgzgVltJxlylX_0551.tachyon,S=7680:2,S: vfs cache: checking remote fingerprint "7680,2016-08-21 00:43:29 +0000 UTC" against cached fingerprint ""
2024/10/06 13:29:28 DEBUG : mailing list archive 2/1432252252.MgzgVltJxlylX_0551.tachyon,S=7680:2,S: vfs cache: truncate to size=7680 (not needed as size correct)
2024/10/06 13:29:28 DEBUG : vfs cache: looking for range={Pos:0 Size:7680} in [{Pos:0 Size:7680}] - present true
2024/10/06 13:29:28 DEBUG : mailing list archive 2/1432252252.MgzgVltJxlylX_0551.tachyon,S=7680:2,S: vfs cache: setting modification time to 2016-08-21 01:43:29 +0100 BST
2024/10/06 13:29:28 INFO  : mailing list archive 2/1432252252.MgzgVltJxlylX_0551.tachyon,S=7680:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:29:28 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252252.MgzgVltJxlylX_0551.tachyon,S=7680:2,S"
2024/10/06 13:29:28 DEBUG : mailing list archive 2/1432252252.MhabBzjWs4sKX_0241.tachyon,S=5953:2,S: vfs cache: checking remote fingerprint "5953,2016-08-21 00:44:04 +0000 UTC" against cached fingerprint ""
2024/10/06 13:29:28 DEBUG : mailing list archive 2/1432252252.MhabBzjWs4sKX_0241.tachyon,S=5953:2,S: vfs cache: truncate to size=5953 (not needed as size correct)
2024/10/06 13:29:28 DEBUG : vfs cache: looking for range={Pos:0 Size:5953} in [{Pos:0 Size:5953}] - present true
2024/10/06 13:29:28 DEBUG : mailing list archive 2/1432252252.MhabBzjWs4sKX_0241.tachyon,S=5953:2,S: vfs cache: setting modification time to 2016-08-21 01:44:04 +0100 BST
2024/10/06 13:29:28 INFO  : mailing list archive 2/1432252252.MhabBzjWs4sKX_0241.tachyon,S=5953:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:29:28 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252252.MhabBzjWs4sKX_0241.tachyon,S=5953:2,S"
2024/10/06 13:29:28 DEBUG : mailing list archive 2/1432252252.Mhhhof5pu1W4h_0590.tachyon,S=1298:2,S: vfs cache: truncate to size=1298 (not needed as size correct)
2024/10/06 13:29:28 DEBUG : mailing list archive 2/1432252252.Mhhhof5pu1W4h_0590.tachyon,S=1298:2,S: vfs cache: setting modification time to 2016-08-21 01:43:39 +0100 BST
2024/10/06 13:29:28 INFO  : mailing list archive 2/1432252252.Mhhhof5pu1W4h_0590.tachyon,S=1298:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:29:28 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252252.Mhhhof5pu1W4h_0590.tachyon,S=1298:2,S"
2024/10/06 13:29:29 DEBUG : mailing list archive 2/1432252252.MiK08UYiidir6_0786.tachyon,S=8087:2,S: vfs cache: truncate to size=8087 (not needed as size correct)
2024/10/06 13:29:29 DEBUG : mailing list archive 2/1432252252.MiK08UYiidir6_0786.tachyon,S=8087:2,S: vfs cache: setting modification time to 2016-08-21 01:44:10 +0100 BST
2024/10/06 13:29:29 INFO  : mailing list archive 2/1432252252.MiK08UYiidir6_0786.tachyon,S=8087:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:29:29 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252252.MiK08UYiidir6_0786.tachyon,S=8087:2,S"
2024/10/06 13:29:29 DEBUG : mailing list archive 2/1432252252.MiNyV9R82Gkf9_0086.tachyon,S=1750:2,S: vfs cache: truncate to size=1750 (not needed as size correct)
2024/10/06 13:29:29 DEBUG : mailing list archive 2/1432252252.MiNyV9R82Gkf9_0086.tachyon,S=1750:2,S: vfs cache: setting modification time to 2016-08-21 01:47:28 +0100 BST
2024/10/06 13:29:29 INFO  : mailing list archive 2/1432252252.MiNyV9R82Gkf9_0086.tachyon,S=1750:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:29:29 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252252.MiNyV9R82Gkf9_0086.tachyon,S=1750:2,S"
2024/10/06 13:29:29 DEBUG : mailing list archive 2/1432252252.Mie9jxfU3GAax_0326.tachyon,S=1956:2,S: vfs cache: truncate to size=1956 (not needed as size correct)
2024/10/06 13:29:29 DEBUG : mailing list archive 2/1432252252.Mie9jxfU3GAax_0326.tachyon,S=1956:2,S: vfs cache: setting modification time to 2016-08-21 01:44:53 +0100 BST
2024/10/06 13:29:29 INFO  : mailing list archive 2/1432252252.Mie9jxfU3GAax_0326.tachyon,S=1956:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:29:29 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252252.Mie9jxfU3GAax_0326.tachyon,S=1956:2,S"
...
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MYxp7V1tzTE0V_0230.tachyon,S=5883:2,S: md5 = 6c408ae57aacb585b647442e68fbbb0d OK
2024/10/06 13:31:54 INFO  : mailing list archive 2/1432252253.MYxp7V1tzTE0V_0230.tachyon,S=5883:2,S: Copied (new)
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MYxp7V1tzTE0V_0230.tachyon,S=5883:2,S: vfs cache: fingerprint now "5883,2016-08-21 00:49:17 +0000 UTC"
2024/10/06 13:31:54 INFO  : mailing list archive 2/1432252253.MYxp7V1tzTE0V_0230.tachyon,S=5883:2,S: vfs cache: upload succeeded try #1
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MaDgkYJyd4nL2_0873.tachyon,S=1503:2,S: vfs cache: delaying writeback as --transfers exceeded
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MZrBtRTBRYBVB_0442.tachyon,S=2212:2,S: vfs cache: starting upload
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MzWRAGwvj2lDL_0292.tachyon,S=2560:2,S: vfs cache: truncate to size=2560 (not needed as size correct)
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MzWRAGwvj2lDL_0292.tachyon,S=2560:2,S: vfs cache: setting modification time to 2016-08-21 01:52:19 +0100 BST
2024/10/06 13:31:54 INFO  : mailing list archive 2/1432252253.MzWRAGwvj2lDL_0292.tachyon,S=2560:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:31:54 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252253.MzWRAGwvj2lDL_0292.tachyon,S=2560:2,S"
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MaDgkYJyd4nL2_0873.tachyon,S=1503:2,S: vfs cache: delaying writeback as --transfers exceeded
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MzWRGlkehSXSj_1012.tachyon,S=2291:2,S: vfs cache: truncate to size=2291 (not needed as size correct)
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MzWRGlkehSXSj_1012.tachyon,S=2291:2,S: vfs cache: setting modification time to 2016-08-21 01:53:47 +0100 BST
2024/10/06 13:31:54 INFO  : mailing list archive 2/1432252253.MzWRGlkehSXSj_1012.tachyon,S=2291:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:31:54 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252253.MzWRGlkehSXSj_1012.tachyon,S=2291:2,S"
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MaDgkYJyd4nL2_0873.tachyon,S=1503:2,S: vfs cache: delaying writeback as --transfers exceeded
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MZ4xrzKLqI139_0565.tachyon,S=1063:2,S: md5 = 689377d2126509af04c2ac3af9e67c08 OK
2024/10/06 13:31:54 INFO  : mailing list archive 2/1432252253.MZ4xrzKLqI139_0565.tachyon,S=1063:2,S: Copied (new)
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MZ4xrzKLqI139_0565.tachyon,S=1063:2,S: vfs cache: fingerprint now "1063,2016-08-21 00:43:40 +0000 UTC"
2024/10/06 13:31:54 INFO  : mailing list archive 2/1432252253.MZ4xrzKLqI139_0565.tachyon,S=1063:2,S: vfs cache: upload succeeded try #1
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MaITIdGtLrc14_0019.tachyon,S=1217:2,S: vfs cache: delaying writeback as --transfers exceeded
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MaDgkYJyd4nL2_0873.tachyon,S=1503:2,S: vfs cache: starting upload
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MzWVLFuEZrefB_0136.tachyon,S=3605:2,S: vfs cache: truncate to size=3605 (not needed as size correct)
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MzWVLFuEZrefB_0136.tachyon,S=3605:2,S: vfs cache: setting modification time to 2016-08-21 01:52:15 +0100 BST
2024/10/06 13:31:54 INFO  : mailing list archive 2/1432252253.MzWVLFuEZrefB_0136.tachyon,S=3605:2,S: vfs cache: queuing for upload in 5s
2024/10/06 13:31:54 DEBUG : mailing list archive 2: Added virtual directory entry vAddFile: "1432252253.MzWVLFuEZrefB_0136.tachyon,S=3605:2,S"
2024/10/06 13:31:54 DEBUG : mailing list archive 2/1432252253.MaITIdGtLrc14_0019.tachyon,S=1217:2,S: vfs cache: delaying writeback as --transfers exceeded

I'm hoping that this will sort itself on its own after a while...

5

Update to 1.68.1.

That just means you have more files in the cache than in the transfer. If you have a lot of small files, it has to compare cache to the remote to make sure things are consistent.

6

Thanks for looking into this.

Update to 1.68.1.

I've already swapped --rc-addr to --url in all .service files rclone rc command, so unless --url is going to be deprecated, I'm okay with waiting for 1.68.1 to arrive in the official repository?

That just means you have more files in the cache than in the transfer

oh okay, that's good to know. I don't understand then, what's causing:

~ 1m 57s ❯ ll gdrive-rclone-crypt/
"gdrive-rclone-crypt/": Transport endpoint is not connected (os error 107)

should my command mount despite these large transfers going in the background (assuming that mount will start working again once they finish)? Is this a bug in rclone?

I can see them slowly going through:

~ 17s ❯ rclone ls "gdrive-crypt:mailing list archive 2" | wc -l  13:39:59
39829
~ 1m 54s ❯ rclone ls "gdrive-crypt:mailing list archive 2" | wc -l   13:45:33
40320
7

I'm not sure what you mean by official repository. The only official is Install (rclone.org) and everything is an unofficial repository in some OS's repo.

That means you drive was killed by something and was not unmounted cleanly. To unmount a fuse releated mount point, you have to stop all processes from accessing it and then unmount it. Dangling stuff leads to things like systemd killing the mount and leaving it in a bad state.

8

everything is an unofficial repository in some OS's repo.

true, I meant archlinux distro repository, that's easiest for me

That means you drive was killed by something and was not unmounted cleanly.

that explains why I couldn't suspend it last night and had to reboot it. Interesting, I thought that rclone will be able to stop transfers and resume them after reboot even if it was killed forcefully I imagine that it will just recover normally.

Would you recommend rm -rf .cache/rclone and starting from fresh after transfers finish, if these mount errors continue?

9

Those are not recommended to use. rclone is a stand alone binary and offers a self update so you can be sure of version changes.

It's not the cached transfers that cause that as it's other processes holding the mount open.

You'd run something like fuser to see what is holding your mount.

10

Those are not recommended to use. rclone is a stand alone binary and offers a self update so you can be sure of version changes.

oh sorry, I've had no idea. That's great, and it looks like rclone selfupdate was available since v 1.55 (in 2021), which is before I started using it, so no excuses. My only mild concern would be that it requires running as root, which might open some new attack vector...

You'd run something like fuser to see what is holding your mount.

Thanks, but running fuser -m gdrive-rclone-crypt doesn't seem to provide much useful information:

fuser -mv gdrive-rclone-crypt                                                14:31:45
                     USER        PID ACCESS COMMAND
/home/user/gdrive-rclone-crypt:
                     root     kernel mount /home/user/gdrive-rclone-crypt

I've tried lsof, but:

lsof +D /home/user/gdrive-rclone-crypt                                   14:36:55
lsof: WARNING: can't stat(/home/user1/gdrive-rclone-crypt): Transport endpoint is not connected
11

It's not the cached transfers that cause that as it's other processes holding the mount open.

That makes sense, I'm suspecting that might be caused by mergerfs which also was set by systemd unit to require this rclone gdrive mount:

       │ File: mount-mergerfs-gdrive-aws-union-crypt.service
──────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ [Unit]
   2   │ After = network.target
   3   │ Requires = mount-rclone-gdrive-crypt.service
   4   │ After = mount-rclone-gdrive-crypt.service
   5   │ Requires = mount-aws-glacier-deep-crypt.service
   6   │ After = mount-aws-glacier-deep-crypt.service

I may try to remove Requires lines and just leave After hoping that would release such locks?

12

Sorry not following what you mean as when you install or update, you have to run as root if you want it installed for everyone in the system. You don't have to run as root, you can run as a user and just install it somewhere else.

It's really up to you on how you want to install it.

I always run fuser -cu as root to see.

That really has nothing to do with it.

If you run a mount and something is mounted.

Say you have Plex/Jellyfin/whatever, something hitting the mount and using it.

Systemd doesn't know what is using the mount nor does it care, it will kill it after a period of time since it cannot unmount it being used.

That being said, I always tie all my services that use the mount to it.

Ideally, you want to stop all services that are using it and depending on how paranoid you are, you can fuser it and validate all is done and then stop it.

13

my bad, I was running rclone selfupdate on an rclone installed from archlinux repo package. Obviously I should have downloaded the binary, save it to user home and then selfupdate would work.

Say you have Plex/Jellyfin/whatever, something hitting the mount and using it.

I see, makes sense, but still I'm not sure how to find out what processes are using it, neither fuser -mv ./gdrive-rclone-crypt nor fuser -cu ./gdrive-rclone-crypt output any information.

I've run out of ideas, so I just rm -rf .cache/rclone/gdrive-rclone-crypt and run mount again and that seemed to be doing something else than just being stuck on the previous debug messages

2024/10/06 23:42:02 DEBUG : Google drive root 'crypt': Checking for changes on remote
2024/10/06 23:42:12 DEBUG : Google drive root 'crypt': Checking for changes on remote
2024/10/06 23:42:22 DEBUG : Google drive root 'crypt': Checking for changes on remote
...

now it's being stuck on these messages. I will give it a few more minutes and hopefully it will work again. I wouldn't be surprised though if it turned out that google is just throttling this account now.

14

okay, all works now, it finally has snapped out of it, started populating .cache/rclone/gdrive-rclone-crypt and let's me list directories without much lag.

I'm still waiting for a mergerfs mount that combines this and another remote to start working again (currently stuck trying to list root directory), but if it won't work soon I guess that I can remove it's cache folder again hoping for the same effect.

I guess that means that your suggestion about corrupted .cache directory after systemd forecefully killing it before it finished all the transfers was right.

[2024-10-07 Mon 00:05] UPDATE after reboot all works fine including mergerfs and rclone-crypt
it is really really slow now (presumably throttled account)

15

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